Start as an agent

Choose a way in

• Just trying it, no key: POST /api/public/compute/demo, or MCP at /api/mcp/rpc without a key. A demo tenant, rate limited per IP.
• A free API key right now, no human: POST /api/agents/register. A sandbox workspace with 25 compute calls a day and a key valid for 30 days, plus a claim link for a person.
• An OAuth client for a client-credentials framework: POST /api/oauth/register (dynamic client registration), then the client_credentials grant at POST /api/oauth/token. There is no authorization code flow. The same sandbox as the call above; an additional option, not a replacement.
• No account, pay per call: Where pay-per-call is on, POST /api/compute/price with no credential answers 402 with x402 payment requirements. agents.json lists it under payments.x402 only while it is on.
• A workspace of your own, as an agent: Sign in with AgentID and an inbox you control, then create an API key in Settings.
• A person owns the account: A person signs up and creates an API key, or an agent-bound key, for the agent.

Register with one call

No account, inbox or person is needed. Send your name and you get a sandbox workspace and an API key straight away.

curl -X POST https://api.last-price.ai/api/agents/register \
  -H 'content-type: application/json' \
  -d '{"name":"your-system/role-name"}'

The response shows the key once in api_key.key. Send it as the x-api-key header. It can compute prices with built-in functions and read functions and routing policies, up to 25 compute calls a day, and it expires after 30 days. It can rotate itself at /api/api-keys/rotate, and it also works as OAuth client credentials at /api/oauth/token. If your OAuth client-credentials framework expects to register its own client, POST /api/oauth/register gives the same sandbox as a client_id and client_secret instead.

The response also carries a claim link. Give it to a person: when they sign in and claim the workspace, it joins their account and the sandbox limits lift.

Or sign in with AgentID

1. Bring an inbox you control

   Create an inbox through your AgentMail account and keep its API key private. AgentID sign-in requires provider_connect permission on that key.

   AgentMail sign-in instructions

2. Sign in to Last Price

   Open signup and choose Sign in with AgentID when the option is available. On auth.agentid.com, verify the application is Last Price Project and review the requested agent name and email. Authorize the pending sign-in with your own inbox through api.agentmail.to. Never send your AgentMail key to Last Price.

   Verified accounts can start without manual waitlist approval on the public production app. Suspended and rejected accounts remain restricted.

3. Use your workspace

   Continue to onboarding after the sign-in callback. Your browser session grants access to your workspace, not staff administration. Choose a workflow or open the dashboard.

4. Create an API credential

   Open Settings, API keys, and create a key with only the scopes your task needs. Send it as the x-api-key header. Call GET /api/me to discover the workspace it resolves to; consult the API contract before making pricing calls. A browser sign-in session is not an API key.