> ## Documentation Index
> Fetch the complete documentation index at: https://docs.robase.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> For chatbots and coding agents, start at /guides/ai-agents.
> Hosted MCP: POST https://api.robase.dev/mcp (Streamable HTTP). Auth: Authorization: Bearer robe_… or robe_agent_….
> Phase 1 tools: get_pricing, send_otp, verify_otp, get_otp, send_sms, get_sms. No payment or top-up tools.
> Call get_pricing; treat listed:true as marketed markets (NG, GH, KE, ZA, GB, BJ, CI, US). Do not invent countries or delivery percentages.
> Prefer OTP-shaped tests such as "Your Robase test OTP is 123456". Do not send Hello or Good morning as tests. Match errors on error.type.

# Routing and failover

> Per-country routes with a fallback on NG/KE/GH/ZA. GB/US/CA are single-route.

Robase routes each message through an upstream SMS gateway picked for the destination country. Which gateways we use is not part of the API contract and may change without notice. Default seed routes:

| Country | Fallback route |
| - | - |
| Nigeria | Yes |
| Kenya | Yes |
| Ghana | Yes |
| South Africa | Yes |
| United Kingdom | — |
| United States | — |
| Canada | — |

If the primary route rejects or times out, the send is retried on the fallback **in the same dispatch**. Credits are refunded if every configured route fails.

Operators can pin one customer to specific routes for a country; credit cost still comes from the global route.

We do not publish a delivery-rate percentage and we do not claim direct MNO contracts on the public site. Routing is through aggregators.

Your application never sees the upstream. You get status via GET endpoints and [webhooks](/sms/webhooks).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.