Name.ai developer portal / Sandbox
Two ways to test against name.ai, and neither touches real money, real domains or production data.
Every public endpoint is a read. Domain search and availability, WHOIS, TLD pricing and registry requirements, marketplace listings, /api/batch and /ask need no account and no key, and nothing they do can register, charge for or transfer a domain. You can call them from a test suite as often as the rate limit allows.
curl -s "https://name.ai/api/pricing/tld?tld=ai&op=register"
curl -s -X POST https://name.ai/api/batch \
-H 'Content-Type: application/json' \
-d '{"operations":[{"op":"tld_requirements","params":{"tld":"ai"}}]}'Integrations that search partner inventory, create orders or send buyers to checkout test in a fully isolated sandbox. It runs the real API logic and real HMAC request signing against a fixed set of pre-seeded test listings.
| Sandbox | Live | |
|---|---|---|
| Credentials | pk_sandbox_ / sk_sandbox_ | pk_live_ / sk_live_ |
| Inventory | Pre-seeded test listings | Real listings from opted-in sellers |
| Payments | Stripe test mode — no card is charged | Real payments |
| Domain transfers | None | Real transfers via registrar push |
| Webhooks | Real signed events with test payloads | Real signed events |
| Getting credentials | Issued immediately on partner approval | Issued by name.ai on request |
There is no separate sandbox hostname. Sandbox and live are served from the same origin on the same https://name.ai/api/partner/v1 paths, and the credential you sign a request with selects which inventory answers it. Going live is a credential swap — the paths and signing logic do not change.
For hosted checkout in the sandbox, use Stripe's test card numbers (for example 4242 4242 4242 4242) with any future expiry date and any CVC.