Set up OP for AI agents
OP gives agents a phone number they can actually use. Start with the guide for your agent runtime, then add inbound webhooks when the workflow becomes two-way.
Choose your agent
What OP gives an agent
OP gives an agent a real phone number it can use for SMS, OTPs, replies, and account recovery workflows. Instead of treating texting as a throwaway side channel, OP turns the phone number into a durable identity attached to the agent's delegated work.
That matters because many web workflows still use phone numbers as a trust and recovery primitive. A browser agent, CLI agent, or local automation stack can be technically capable and still get stuck the first time it needs a code, a reply, or a stable number for future sign-ins.
Choose plugin setup or plain API setup
Hermes and OpenClaw have OP plugin flows, so the best setup path is to install the plugin, configure the delegated phone number, and pass a webhook URL where OP can deliver inbound events.
Codex and Claude Code should start with https://www.op.inc/skills.md. That skill file is the agent-readable entrance point: it explains when to skip setup, when to run OTP signup, how to mint an API key, and how to use the stable /v1 runtime API.
Why skills.md matters for CLI agents
A CLI agent is not always starting with credentials. The OP skill gives it the full decision tree: existing OP_API_KEY, new human signup, or returning human login. That keeps Codex and Claude Code from confusing setup sessions with runtime API keys.
After setup, the flow becomes simple: store OP_API_KEY safely, send SMS with POST /v1/messages, and read replies with GET /v1/messages or webhooks.
Webhooks make the workflow agent-native
Outbound texting is only half of the useful loop. The moment your agent needs OTPs, replies, delivery status, or recovery codes, OP should send events back to the app or agent runtime through a webhook.
For local development, a tunnel URL is enough. For production, use a stable HTTPS endpoint and keep the OP number attached to the same account or workflow over time.
Start small, keep the identity stable
The fastest path is to pick the guide for your agent, send one test message, then add inbound handling once the workflow needs it. For more on why the number itself matters, read VoIP numbers vs carrier numbers for agents.
Once a workflow relies on a phone number for verification or recovery, avoid swapping numbers between tools. The value is continuity: the same number sends, receives, verifies, and remains reachable later.
Final step: ask the agent what OP unlocks
After the first message works, give the agent one more instruction. This turns setup into a useful handoff instead of stopping at a successful test SMS.
Read https://www.op.inc/skills.md and https://api.op.inc/docs.
Now tell me what you can do with OP from here.
Include:
- the OP number you are using
- how you can send texts
- how you can receive replies or OTP codes
- whether webhooks or polling make more sense for this project
- whether I should use the shared free number or lease a dedicated number
- any voice-call capabilities that are relevant
- 3 useful next workflows you can handle for me
Before sending real messages to anyone else, ask for my approval.