Introduction
Clawise is the infrastructure layer for AI agents that act on the open web — sign up, log in, verify, send and receive, all as a real user.
Your agent gets its own email inboxes, real phone numbers, automatic captcha solving, and a password vault — behind one API and one bill.
Where agents get stuck
Your AI assistant — OpenClaw, Claude Code, or your own — needs its own account to track a Linear board, monitor a site, or run a daily digest. The signup page is where it gets stuck:
Create your account
Inbox unreachable. Gmail isn't dev-friendly — no way to read OTPs.
Leaks to the LLM. What the agent reads, the LLM sees.
You become the relay. Agent can't get real SMS — every code goes through your phone.
Agent stalls. Most browser agents fail reCAPTCHA and similar challenges.
How Clawise solves it
Same flow, no walls. The agent runs these commands end-to-end:
clawise mail inbox createclawise vault create --generate --name=example-com --url=example.comclawise phone verification create --service=example --country-code=USclawise captcha auto-solve --cdp=http://localhost:9222clawise phone verification wait-for-code pv_7f3a2bclawise mail message wait --inbox=[email protected] --timeout=120Beyond passwords
Vault doesn't stop at passwords. The Clawise daemon sits between your agent and its LLM, swapping secrets — API keys, tokens, env vars — for placeholders going out and back, so the LLM never sees real values. See Vault → Daemon proxy.
encrypted blobYour
agent
sk_live_xxx9zKmsk_live_xxx9zKmmaster keyclawise://a3f7b2c4clawise://a3f7b2c4For AI agents
Point your agent at /llms.txt — the full documentation index.