Skip to main content
An agent can set up Locus Pro without a dashboard login or workspace invitation. It verifies its identity through AgentID, asks a person to fund its balance through Stripe Checkout, and connects to tools through MCP. The account starts at $0. The agent can manage its own tools, balance, and credentials. The payer’s card stays in Checkout.

​
Let the agent handle setup

Give your agent the Locus skill and this prompt:
Send to your agent
The agent starts by reading the current onboarding instructions:
Read onboarding instructions
This public endpoint returns the flow and URLs the agent needs.

​
How setup works

1

Register and verify identity

The agent generates a recovery token and begins registration. It follows the returned AgentID authorization URL to verify its identity and inbox.
2

Activate the account

The agent repeats the original registration request after approval. It stores the returned account credential and recovery token securely.
3

Connect through MCP

The agent adds the hosted MCP server and completes OAuth using the same AgentID identity.
4

Choose tools and request funding

The agent enables the tools it needs and creates a Stripe Checkout link for a specific amount. You review and pay through that link.
5

Start work

The agent waits for funding status to become ready, then uses its MCP connection to discover and call tools.

​
What the payer approves

Share only the funding link. Never paste card details into chat.

​
Building your own onboarding flow

The API reference defines the requests and responses. The AgentID authentication reference covers browserless identity verification.

​
Registration and recovery

Generate 24 random bytes encoded as unpadded base64url:
Generate a recovery token
Send it with an account name to POST /api/credits/agent/register. A 202 response includes account.registration.authorizationUrl. Complete that authorization, then replay the exact name and token before the pending registration expires. Save account.connection.credential from the activation response. This lcac_… credential authorizes the agent-account REST routes; tool access uses MCP OAuth.

​
MCP connection

MCP server URL
Choose AgentID during authorization and use the identity that registered the account. On a headless host, keep the client’s login process and callback listener running throughout the handoff.

​
Tool access and funding

Use a stable Idempotency-Key when retrying a funding request. Poll the returned statusUrl at the suggested interval and continue only when its state is ready.

​
Rotate the credential

Use POST /api/credits/agent/credential/rotate with the current credential and a newly generated recovery token. Save the new credential and token together; rotation replaces both immediately. Keep both secrets out of funding messages, prompts, and source repositories.