Paste the command
Your agent reads the OpenAPI contract and creates a claimable signup intent for your email address.
Clarus for agents and the humans who direct them.
Agents can discover Clarus, create a claimable account request, and connect through OAuth-backed MCP. Humans stay in control: no account becomes active until the owner verifies email and claims it.
Let your agent start the account request.
Replace agent with your agent CLI command. The agent should ask for your email, call the signup-intent API, then hand the claim step back to you.
agent "Set up Clarus for me. Use https://clarus.page/.well-known/openapi.json and ask for my email if needed. Create a claimable signup intent, then tell me to check my email."Direct API fallback
curl -sS https://app.clarus.page/api/agent-signup-intents \
-H 'content-type: application/json' \
-d '{"email":"you@example.com","agentName":"Agent CLI","requestedUse":"Set up Clarus for my writing work."}'Claim by email
Clarus emails a private claim link. The account is not active until the human signs in with that email.
Connect tools
After claiming, the human can connect an agent through Clarus MCP OAuth for read-only document context.
The pieces agents can read.
Clarus publishes machine-readable setup metadata and an OAuth MCP server so agents can discover what is available before asking a human to authenticate.
Human-owned by design.
- Agents create pending signup intents, not active accounts.
- Claim links are emailed only to the intended human address.
- The claim token is never returned in the API response.
- MCP access still requires OAuth consent from the claimed account.
Ready when your human is ready.
Start with a claimable setup request, then let the human finish authentication and connect their preferred agent.