Verify a Free workspace
A workspace on the Free plan has to verify a mobile number and add a payment card before it can place a call. The card is not charged. Paid and Beta workspaces are not asked for either.
What you need
| Step | What happens |
|---|---|
| 1. A mobile number | Enter the number in international format (for example +447700900123). We text it a one-time code and you type the code back. Mobiles from the UK, Guernsey, Jersey, the Isle of Man and the US can be verified. One number verifies one workspace. |
| 2. A payment card | Add a card through the secure card form. It is saved with our payment provider and is not charged; you pay only if you later buy credit or a plan. A card the workspace already has on file counts. |
Both steps are on the Verify page of the web app, at /verify. A new sign-up lands there. An owner or admin of the workspace has to do them; other members see the page and cannot complete it. The steps can be done in either order and the workspace is verified as soon as both are done.
Until the workspace is verified
Everything that does not place a call works as normal: creating and editing mapping jobs, tests, personas and datasets, reading results, and managing the team and API keys. Starting a run of any kind is refused, in the web app and through the API, the SDKs and the MCP server. The web app shows a message with a link to the Verify page. The API answers:
HTTP/1.1 402 Payment Required
Content-Type: application/json
{
"error": "This workspace is on the free plan and is not verified. An owner or admin must verify a mobile number and add a card (the card is not charged) on the Verify page of the console before calls can be placed.",
"errorCode": "VERIFICATION_REQUIRED"
}Nothing is started and nothing is used from the workspace's allowance. The API key stays valid: retry the same request with the same key once the workspace is verified. See Errors for how this differs from the other 402 responses.
If the card is removed
The workspace stays verified only while it has a card on file. Removing its last card makes it unverified again, and runs are refused until a card is added on the Verify page. The mobile number stays verified, so no new code is needed. Removing one of several cards changes nothing.
Workspaces created by an AI agent
An agent that registered its own workspace (see Agent onboarding) can verify the mobile number with a person's help: it calls requestAnchorCode, the person reads back the code from the text message, and the agent calls verifyAnchorCode. That alone does not make the workspace able to place calls. An owner or admin still has to open the Verify page in a browser: the page picks up the number the agent verified, with no second text message, and takes the card.
For a workspace nobody has claimed yet, the agent calls getClaimLink and gives the person the link; they set a sign-in, which makes them the owner, and then complete the Verify page. For a workspace that already has an owner, that person signs in to the web app and completes the Verify page. Until they have, the agent's runs get the VERIFICATION_REQUIRED refusal above.
Common problems
| What you see | What to do |
|---|---|
| The number has already verified another workspace | Use a different mobile. A number can stand behind one workspace only. |
| It is not a mobile number | Landlines and virtual numbers cannot receive the code. Use a mobile. |
| The country is not supported | Only UK, Guernsey, Jersey, Isle of Man and US mobiles can be verified for now. |
| Too many codes have been requested | Wait an hour, then ask for a new code. |
| You cannot verify a mobile for this workspace | You are not an owner or admin. Ask one of them to open the Verify page. |
| The card was saved but the step is not ticked | Refresh the page after a minute; the confirmation from the payment provider can lag. |