Claim a workspace an agent made

An AI agent can create an AgentStack workspace on its own. It calls one public endpoint, gives your email address, and receives an API key. It then builds an agent, trains it on content, and chats with it — all before you know the workspace exists. This page explains what that workspace is, what it can and cannot do, and what to do with the email you received.

If you did not expect this email, you do not have to do anything. Ignore it and the workspace deletes itself in seven days.

The sandbox plan

A workspace made this way runs on the sandbox plan. The plan exists to let software try the product without a card, without a human, and without much risk. It is deliberately small:

• 25 credits, granted once. They never refresh. One chat message costs one credit.
• One-credit models only. More expensive models are refused.
• One agent, and up to 25 crawled pages per website source.
• Eight API areas: agents, sources, ingest, chat, conversations, messages, activity, and analytics.

Everything else is closed. A sandbox key cannot send email, connect a channel, call an external URL through a custom action, publish a help page or help center, add a custom domain, read contacts, or touch billing. It cannot spend money, and it cannot create more keys. New parts of the API stay closed to it until somebody opens them on purpose.

The workspace also has no owner. Nobody is a member of it, so nobody can sign in to it, until you claim it.

Why you were emailed

The agent named your address. Nobody verified it, and AgentStack does not treat it as yours until you prove that you read it. The 6-digit code in that email is that proof. It is valid for 24 hours, and five wrong entries lock it out. A correct code never costs you an attempt.

The workspace itself lives for seven days, so the code can expire while the workspace is still there. The claim page has a Send a new code button for that. It mails a fresh code to the same address — the one on the workspace, which nobody can change. The code you already have keeps working until the new one is actually sent, and stops the moment it is.

The code never travels in the claim link, so holding the link is not enough to take, or delete, the workspace. Only somebody who read the mailbox can.

Claim it

Open the claim link. The page shows you what the agent built before you decide anything: the agent's name, the instructions it was given, what it was trained on, and any endpoints its actions can reach. The API key is never shown there.

You then have two choices.

Claim it. Sign in — or create an account, if you do not have one — using the address the code was sent to, and enter the code. The workspace becomes yours, you become its owner, and it stops being on a timer. If that address already has an AgentStack account, the workspace joins that account. An account under any other address is refused, even with the right code.

That second rule is what protects you. You may well have given the code to the agent, and the agent already has the claim link, so neither of those identifies you. Being signed in as the mailbox does. The agent can confirm the code through its own endpoint, which tells it that you received the email, but it cannot take ownership on your behalf, and it cannot delete the workspace either.

The same rule applies to Send a new code: only somebody signed in as that address can ask for one, so nobody else can invalidate the code in your inbox or use up the day's sends.

Delete it. Enter the code and confirm. The workspace and everything in it is removed at once. This cannot be undone.

What a claim changes

A claim moves the workspace from the sandbox plan to the free plan. The free plan does not include REST API access. The agent's key keeps working as a credential and stops expiring, but every API call it makes returns PLAN_UPGRADE_REQUIRED until you upgrade the workspace to a paid plan.

This matters if you want the agent to keep working. Upgrade the workspace, or expect the agent to stop the moment you claim it. Your 25 sandbox credits stay as they are: the free plan's monthly credits are not added retroactively.

If you do nothing

An unclaimed workspace is deleted seven days after it was created, with everything in it. A daily job does this. There is no second email and no recovery, because the address was never verified and AgentStack will not send unrequested mail to it.

The API key the agent holds expires on the same schedule, and both dates are fixed when the workspace is created, so a key can never outlive the workspace it belongs to.

For developers

The endpoints behind this flow, their request and response shapes, error codes and rate limits are documented in REST API: agent sign-up. Agents that want the short version can read /agent.md.