How It Works
1
Your agent signs up
The agent sends your email and its own name to
POST /v3/agents/signup, or calls orbit_signup over
MCP. Orbit creates a
workspace with the signup credits and returns an API key for the agent.2
Your agent works
The agent uses its key for Search, Enrich, and profile reads, like any other
key. You don’t need to sign in, paste a key, or approve anything.
3
You sign up
Your agent gives you a sign-up link. Sign up with the same email, using
Google or email, as you would anyway. Orbit adds you to the workspace as its
owner. The agent’s key keeps working.
4
You share credits
Add credits on the Billing
page. You and your agent draw from the same balance, and you can see and
revoke the agent’s key in the dashboard.
Sign Up
api_key appears only in this response. Store it in your agent’s private
credential storage, and send it as Authorization: Bearer sk_orb_... on every
request. Never show it to the person or put it in a message.
Give the person sign_up_url and ask them to sign up with the email you used.
Do it when it helps, and always when credits run out: a request that needs more
credits than the workspace has returns 402 with
developer_api_credits_insufficient.
Rules
- One signup per email. Each email address gets one agent workspace and one
set of signup credits. Gmail dots and
+tagscount as the same address. A person who signs up with that email shares the workspace’s credits instead of getting a second grant. - Existing accounts sign in. If the email already has an Orbit account,
signup returns
409withagent_signup_email_has_account. Ask the person to sign in and connect you, for example with the MCP server. - Real email addresses only. Disposable and example domains return
400withagent_signup_email_not_allowed. - Only that email joins. The workspace goes to whoever signs up or signs in with the verified email the agent used, and to no one else.
The agent’s key has the
search:read and profile:read scopes. Directory
management, members, and billing need the person’s own sign-in.