For developers and agents
This developer portal is free and public — no signup required to start building against the Name.ai API docs, the Name.ai MCP server, or the OpenAPI spec. Signing in via OAuth additionally unlocks real marketplace pricing on domain search.
Domain search/availability, WHOIS lookup, and TLD pricing/requirements as MCP tools. Works with any MCP client — Claude, Cursor, and others.
The same endpoints as plain REST, documented as an OpenAPI 3.1 spec, for anything that isn’t speaking MCP.
OAuth 2.1 with PKCE. Optional — every endpoint works without it. Signing in additionally unlocks real marketplace prices.
A curated, machine-readable overview of intermediatebrokers.com — what it is, and where to start.
The MCP server is remote — no install, no API key. Add it to any MCP client (Claude Code, Claude Desktop, Cursor, and others) with this config:
{
"mcpServers": {
"name-ai": {
"type": "http",
"url": "https://mcp.intermediatebrokers.com/mcp"
}
}
}Or with the Claude Code CLI:
claude mcp add --transport http name-ai https://mcp.intermediatebrokers.com/mcpTools available: domain search/availability, WHOIS lookup, TLD registration pricing, and TLD registration requirements. To see real marketplace prices on domain searches, authenticate per auth.md. The server is open source — source, AGENTS.md, and agent plugin manifest at github.com/namekart/nameai_mcp. Pricing for agents: /pricing (HTML) or /pricing.md (markdown).
Two agents integrating against intermediatebrokers.com reported the same friction — the picture had to be assembled from several pages. This is the whole surface in one table.
| Resource | Where |
|---|---|
| API referenceEndpoints, conventions, curl examples | /developers/api |
| OpenAPI 3.1 specThe machine-readable contract | /openapi.json |
| MCP serverSetup and tool reference | /developers/mcp |
| MCP manifestAlso extensionless at /.well-known/mcp | /.well-known/mcp.json |
| MCP server card | /.well-known/mcp/server-card.json |
| AuthenticationOAuth 2.1 + PKCE, optional | /developers/auth |
| auth.mdThe canonical agent_auth document | /auth.md |
| Protected-resource metadataRFC 9728 | /.well-known/oauth-protected-resource |
| Authorization-server metadataRFC 8414 | /.well-known/oauth-authorization-server |
| Batch endpointGET it for the catalogue; POST up to 20 reads | /api/batch |
| Natural-language searchNLWeb; JSON or SSE | /ask |
| Schema mapIndexes the structured-data feeds | /schemamap.xml |
| Marketplace feedOne schema.org Product per line | /feeds/listings.jsonl |
| Pricing, agent-readablePer-TLD table, commissions, limits | /pricing.md |
| Site map for agentsScoped: /developers/llms.txt, /api/llms.txt | /llms.txt |
| AI catalogEvery agentic resource here | /.well-known/ai-catalog.json |
| A2A agent card | /.well-known/agent-card.json |
| Agent skills indexArtifacts with digests | /.well-known/agent-skills/index.json |
| SandboxTest without real money or transfers | /sandbox |
| Sandbox step-by-step guidePartner API; environment is set per credential | /syndicate-partners/sandbox |
| JavaScript SDKnpm install nameai-sdk | https://www.npmjs.com/package/nameai-sdk |
| Python SDKpip install nameai | https://pypi.org/project/nameai/ |
| Source, AGENTS.md, plugin.jsonAgent configs and the plugin manifest | https://github.com/namekart/nameai_mcp |
The public read endpoints need no sandbox — they are free, unauthenticated and safe to call as often as the rate limit allows. The Partner API has one: sandbox and live are selected by the environment on your credential, not by a separate hostname, so the same /api/partner/v1 paths serve both. Sandbox credentials are issued on approval with no manual review, and sandbox orders fire real signed webhooks. Sandbox testing guide.
The files themselves, for a client that already knows what it wants: /openapi.json, /.well-known/mcp.json, /auth.md, /llms.txt, and the section-scoped /developers/llms.txt · /api/llms.txt.