Introduction
This article walks you through setting up an Anthropic account for ARVO Studio and finding the two values you need to enter in ARVO Studio Setup: the API key and the model identifier. This is specifically written for somebody who has not used or done this before. The deployment is the end users’ responsibility, not Bluefort’s and is billed directly by the provider.
Before you start you will need
- A company email address to register with, ideally a shared one rather than an individual’s, so the account does not become tied to one person who may later leave the company.
- A company payment card. Anthropic bills this directly and the charges will not appear on your Bluefort invoice.
- Somewhere safe to store a key, such as your organisation’s password manager. Do not plan to email it or save it in a document.
- Agreement internally on who owns this account and who is responsible for the costs related to it.
Step 1: Create your Anthropic account
Go to the Anthropic Console at console.anthropic.com and create an account using your company email address. Register it as an organisation rather than a personal account where you are offered the choice, so that colleagues can be added later.
Step 2: Add billing
Open the billing area of the console and add your company payment card. Until billing is set up, API calls are refused, so this step cannot be skipped. If your organisation prefers to control this, set a monthly spend limit at the same time for transparency purposes. That limit is yours to set and change; Bluefort has no visibility of it and no ability to raise it.
Step 3: Create an API key
Open the API keys area of the console and create a new key. Give it a name that says what it is for, such as ARVO Studio followed by the environment name, so that if you later hold several keys you can tell which is which and revoke the right one.
Important: The key is displayed once, at the moment you create it. Copy it into your password manager so its not lost. If you lose it you cannot recover it; you have to revoke that key and create another.
Treat the key exactly as a password. Anyone holding it can use your account so ideally this is not emailed, not pasted into any chat message and not stored in a shared document.
Step 4: Note the model identifier
ARVO Studio needs to know which model to use, provided as a model ID rather than a friendly name. So this must be one of the models ARVO Studio supports, so choose it must be chosen carefully.
Step 5: Check your rate limits
New accounts start on an entry usage level with standard / default rate limits. That is usually fine for a first project, but a busy build can reach the limit, and when it does the work is slowed or refused. Check the limits shown against your account so you know where you stand before you start a project.
Note: Rate limits, throughput and availability are set by Anthropic, not by Bluefort. If a request is refused because a limit has been reached, it is resolved in your own Anthropic account.
Step 6: Enter the values in ARVO Studio
Go back to Business Central, open ARVO Studio Setup and find the Your Anthropic API (BYO) group. Turn Claude Direct Connection Enabled on, and make sure the Foundry connection is off, because only one connection should be active at a time.
- Claude API URL is the standard API endpoint and should be left as it is.
- Claude Model takes the model identifier from step 4.
- Claude API Key takes the key you copied in step 3. The field is write-only, so once you save it the value is never shown again and the Configured toggle button confirms it is stored.
- Claude Max Tokens should be left at its default unless you have a reason to lower it, because a value set too low can truncate output and cause validations to fail.
Step 7: Check that everything works
Save the Setup page, then run Test Connection. A clean result confirms that the entitlement can be reached, that the AI connection responds and that the required identities can authenticate. If the AI connection is the part that fails, the usual causes are a model identifier that does not match a supported model, a key that was revoked or regenerated and not re-entered, or billing that has not been completed on the Anthropic account.