API playground
Browse every OtoCo capability by category. Each tool shows whether it is public or requires an API key, plus copyable curl / Node.js snippets.
Base URL follows NEXT_PUBLIC_MCP_API_URL / NEXT_PUBLIC_API_URL, otherwise staging https://api-staging.otoco.io.
Public tools need no Authorization header. API key tools need Authorization: Bearer otoco_sk_… — follow How to get an API key (create it in DashPanel → Developer).
REST + MCP
API playground
Browse every OtoCo capability by category. Copy ready-to-run curl or Node.js requests. Public tools need no key; private tools need an API key from How to get an API key.
https://api-staging.otoco.io/v1https://api-staging.otoco.io/mcp/v1/public/name-checkPublicpublic_name_check
Check entity name availability on production networks (`main`, `polygon`, `base`); testnet-only collisions (`sepolia`, `basesepolia`) are ignored. Without jurisdiction checks all supported (DELAWARE, WYOMING, SWISSASSOCIATION, UNADUNA — Marshall Islands excluded).
Parameters
| Name | Type | Required | Example |
|---|---|---|---|
name | string | Yes | Acme LLC |
jurisdiction | string | No | DELAWARE |
curl -s -X POST \
-H "Content-Type: application/json" \
-d '{
"name": "Acme LLC"
}' \
"https://api-staging.otoco.io/v1/public/name-check"Related
- How to get an API key
- OtoCo MCP Overview
- Connect your AI agent
- Machine-readable reference: https://otoco.io/mcp.md