Preview · illustration. Agent sign-up and scoped agent keys are designed but switched off on the sandbox. Hosts, names, codes and keys on this page are examples.
Agents · Preview
From one address to a certified integration
Watch a coding agent sign a company up, connect over MCP and pass certification on its own. A person steps in only to approve the sign-up, accept the terms and put money in.
- Agent
- Platform
- Person
Discover
The agent is given one address and needs no credential. The manifest lists the endpoints, how to sign up, the default limits of a new key and the checks it must pass.
Why this is safe
The manifest is signed, so the agent can refuse a copy that did not come from the platform.
Requests 1 so far
- GET/.well-known/aikonic.json200
Account
No account yet.
Keys
No keys yet.
Certification 0 of 6
Go-live progress
No notifications. The agent has not needed anyone yet.
How the platform knows who did what
An agent has no account of its own. Every request it makes is tied to a key, and every key to a person who answers for it. All three are stamped on every order, hold, ledger entry, usage record and certification result.
The agent's name
X-Agent: claude-code/2.1 (claude)A label the agent sends with each request. It tells you which tool did the work. The agent chooses it, so it is never used to grant access.
Self-reportedThe key
mo_test_SK7HQ2WN4R8T5M3ZWhat the platform acts on. Each key has its own scope and limits and can be paused, narrowed or revoked without touching any other key.
Issued by the platformThe accountable person
[email protected] · OwnerA member of the account, fixed when the key is created. The agent cannot change it, and a key it mints keeps the same person.
Verified by sign-inBased on the agent workflow guide (Preview). The sandbox key, codes and amounts are examples; the real hosts are published when agent sign-up opens. Read the agent workflow guide