FREE INFRASTRUCTURE FOR AGENTS AT SCALE

Give one agent or a whole fleet real email accounts and phone access.
Still $0 at 1,000 accounts.

KeyID gives agents real inboxes, phone and SMS access, verification handling, and saved state so they can run pure email operations or full website workflows without paid mailbox-seat economics. The real break is that the cost still stays at $0 when the account count gets large.

Get started See the cost breakdown
No human setup No API keys Email fleets + website flows 
https://keyid.ai/mcp

Add as remote MCP endpoint in Claude, Cursor, or any MCP client

ext install keyid.keyid-agent-inbox

Or search "KeyID Agent Inbox" in the VS Code Marketplace

npm install @keyid/sdk

Then: const agent = new KeyID(); await agent.provision();

pip install keyid

Then: agent = KeyID(); identity = agent.provision()

POST https://keyid.ai/api/v1/provision

No API key needed — use from any language or runtime

Works with Claude Cursor VS Code Windsurf OpenAI CrewAI AutoGen LangChain OpenClaw Lovable Replit Devin n8n Playwright

Why it stays free

Shared infrastructure. Separate identities.

Inboxes and phone access are allocated from shared pools. Each agent gets its own identity, but no one pays for a private mailbox stack behind every account. Domains are warmed up before entering the pool and rotated automatically when reputation degrades. Rotation only affects outbound sending — agents keep receiving all incoming messages to the same address regardless.

Provisioning is rate-limited per IP and per identity. Agents that abuse sending or trigger spam complaints lose reputation and get throttled automatically. Repeat offenders are suspended. This keeps the shared pool healthy for everyone without charging for access.

Use cases at scale

Use KeyID when many agents need separate identities.

The common pattern is not one blocked registration. It is repeated account creation, outbound email, replies, support, and recovery across a fleet where each agent needs its own inbox identity.

Outreach automation Virtual assistants Research agents Web automation Lead generation Account management QA & testing Customer support bots Data collection Price monitoring Competitive intelligence Onboarding flows Marketplace sellers Social media agents Recruiting pipelines Compliance checks

Outbound fleets

Send thousands of emails from distinct agent identities.

Give campaign agents, account managers, or follow-up workers their own inboxes so sending, reply handling, and recovery do not collapse into one shared mailbox.

Each agent keeps its own send, receive, and recovery identity.

Registration waves

Register on websites at scale.

When agents need accounts on marketplaces, tools, forums, or partner systems, the same identity layer can catch email links, SMS codes, and login checks without a human loop.

One path covers inboxes, phone access, links, codes, and saved state.

Support and reply teams

Give your virtual team their own inboxes.

Customer-facing fleets need separate identities for replies, follow-up, and recovery, otherwise every message thread piles into a human-owned shared mailbox.

Replies stay attached to the right agent identity.

FAQ

Answers teams ask before they move one agent or a whole fleet onto real inboxes, SMS, and website verification work.

Is KeyID really free at 1,000 accounts?

Yes. The homepage claim is about 1,000 separate accounts, not 1,000 messages. KeyID is currently $0 at that scale, which is why teams paying mailbox-fleet pricing elsewhere switch.

Is this for one agent, or for teams running fleets?

Both. One builder can use KeyID for a single headless agent, and teams can use the same system for hundreds or thousands of agents that need separate inboxes for registration, sending, reply, and recovery.

Can agents actually use this on real websites that send email or SMS verification?

Yes. KeyID is built for the real website path: inboxes, phone and SMS, magic links, email codes, and TOTP so agents can keep moving through third-party registration and recovery flows.

Why not use Gmail, Google Workspace, AgentMail, or outreach tools?

Those paths either assume human-owned accounts, paid mailbox seats, API-key setup, or pricing that gets painful once you need a real fleet. KeyID is aimed at agent-native infrastructure instead. The full breakdown is on the compare page.

Do I need a human setup, dashboard, or API key before an agent can use it?

No. The goal is zero human setup in the critical path. Agents can get real communication identity without first making your team provision and manage a human mailbox stack.

Where do I find MCP, Claude, Cursor, Lovable, Replit, OpenClaw, or Playwright setup?

See the For agents section below. The setup and runtime references live there and on the linked docs pages.

Can agents send or reply from these accounts too?

Yes. The same infrastructure that handles registration and verification also supports real inbound and outbound communication, which is why it works for support agents, outreach fleets, and business-facing automation too.

For agents

Implementation details live here. Expand for hosted MCP, local stdio, and runtime guides for Claude, Cursor, Lovable, Replit, OpenClaw, and Playwright.
Open setup guide Open MCP Hub Claude setup Cursor setup
Hosted MCP Local stdio Lovable Replit OpenClaw Playwright

Remote

Hosted MCP endpoint

https://keyid.ai/mcp

Local

Local stdio package

npx -y @keyid/agent-kit

Claude + Cursor

Use KeyID inside your agent client.

Connect the hosted endpoint or the local package, then give the agent inbox, SMS, and website verification access.

Open Claude guide Open Cursor guide

Lovable + Replit

Keep app logic in your runtime and hand identity work to KeyID.

Use SDK or API calls in app code, then keep website registration and verification loops on real inboxes and real phone/SMS channels.

Open Lovable guide Open Replit guide

OpenClaw

Add email identity to every OpenClaw agent and skill.

Connect KeyID as a remote MCP skill so OpenClaw agents can provision inboxes, receive verification codes, and handle OTP flows across a multi-agent fleet.

Open OpenClaw guide

Playwright

Keep the browser in Playwright and the identity layer in KeyID.

Let Playwright drive the site while KeyID handles inboxes, SMS, codes, and persistent website state for long third-party flows.

Open setup guide

Real agent infrastructure at fleet scale

Stop paying human-mailbox prices for agent fleets.

Give one agent or ten thousand real email accounts, phone and SMS access, and the website identity layer it needs to register, reply, and recover on its own.

Get started Compare the economics