Authyo for AI agents
Authyo handles passwordless login, OTP verification, and session management for other apps, giving support and engineering teams a way to verify users and manage active sessions. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Authyo.
Verify a one-time passcode
Verify an OTP a customer submitted during login before letting a support agent confirm their identity.
Send a transactional OTP
Send a one-time passcode to a customer's phone or email as part of a login or checkout flow.
Revoke a suspicious session
Revoke an active user session flagged as suspicious only after a support lead approves it, since it signs the user out immediately.
5 Authyo actions, graded by risk.
Every Authyo action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
2Look things up. Allowed by default.
- authyo.verify_otpVerify OTP
- authyo.verify_tokenVerify Token
write
2Create and change things. Allow, or ask the user first.
- authyo.send_otpSend OTP
- authyo.send_order_notificationSend Order Notification
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- authyo.revoke_sessionRevoke Session
Authyo in three steps.
- 01Your users connect AuthyoThey add their Authyo api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “send OTP” can wait for the user, and “revoke Session” can be denied outright.
- 03Any agent can actYour agent calls Authyo through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('authyo', { read: 'allow', write: 'ask', // send_otp destructive: 'deny', // revoke_session }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Authyo connects.
Users add their Authyo api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Authyo connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Authyo from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraphMore security and identity apps.
Authyo and Arc0, answered.
Can I use Authyo with Claude, ChatGPT or Cursor?
Yes. Connect Authyo to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Authyo actions you allow.
How do users connect Authyo?
Users add their Authyo api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Authyo actions can my agent take?
5 in total: 2 read, 2 write and 1 destructive, such as “send OTP”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Authyo?
Yes. Actions like “revoke Session” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Authyo too?
Yes. The same Authyo connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Authyo into your agent.
Your users connect Authyo once, under your brand. Your agent gets 5 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan