Give your agent real-world accounts

CitizenAI holds the identity, the credentials and the approvals. Your agent gets scoped access to the accounts you decide it should have — nothing more.

Connect your agent from Claude Code, Codex, OpenCode, Hermes, OpenClaw, ChatGPT, or Claude. Provision the email addresses, phone numbers, wallets and social accounts your agent needs, and keep every approval on your side of the line.

Quickstart

In the dashboard, open Connect an agent and copy the prompt. Send it to your agent:

Set up CitizenAI — https://citizenagent.ai/llms.txt

The agent sends you one approval link. Open it and approve the connection.

Step	What it does
Install	The agent reads the setup link and runs the installer from the CitizenAI site. No repository checkout and no package-registry credential is necessary.
Pair	The agent starts a device authorization. You approve one link, and the short code is already in it.
Verify	The agent installs the account skill, adds the `citizen-ai` MCP server, and calls one CitizenAI tool.

Pairing buys nothing. Paid provisioning is approved separately, every time.

Connect your agent walks the same path with the failure cases attached.

Everything in these docs

Section	What it covers
Start here	What the product is, what it deliberately does not do, and one account end to end.
Connect a runtime	The setup link, OAuth sign-in for ChatGPT and Claude, and keeping a runtime connected.
Marketplace	Twelve categories, and the three ways an agent gets into a service.
Accounts	Email, phone, crypto wallets, social accounts, cloud sign-in, identity, credentials.
Payments	Fund in USD or USDC, and read the record of every purchase.
Agent access	The `/mcp` endpoint and the tools your agent is given.
Reference	Troubleshooting, health, supported versions, terms.

All pages lists every page on this site, and names what is deliberately not here.

What your agent can be given

Capability	What your agent gets	How it arrives
Email addresses	A mailbox it can read verification codes from	Paid
Phone numbers	A rented number for SMS codes, one service at a time	Paid
Crypto wallets	A server-custodied wallet, with balances and transfers	Provisioned
Social accounts	A sign-in through the cloud browser	Billed per session
Provider connections	Reviewed third-party tools, connected without sharing keys	Reviewed

How it fits together

Your runtime                      CitizenAI                     The real world
Your agent             ──MCP──▶   identity, credentials,   ──▶   email, phone, wallet,
                       ──cloud──▶ approvals, payments            social, provider tools
                          browser

Every connection is outbound, from your machine to CitizenAI. CitizenAI never opens a connection into your runtime, and it does not store a gateway URL.

How it fits together covers each path, and what travels over it.

When something breaks

Symptom	Start here
The agent shows as offline	Reconnect or repair
A verification code never arrived	Email addresses
`Provider unavailable.` at checkout	Service purchases
A cloud sign-in does not start	Cloud sign-in
A second agent replaced the first one	Connect more than one agent

On this page

Give your agent real-world accounts#

Quickstart#

Everything in these docs#

What your agent can be given#