Developers & AI agents

betadomain for AI agents & developers

Connect betadomain to Claude or ChatGPT, or call our public API directly. Check domain availability and prices, look up non-personal WHOIS data, and — with a token — manage your own domains. Everything is honest: buying still needs a human checkout.

MCP endpoint (Streamable HTTP · JSON-RPC 2.0)https://betadomain.de/api/mcp

Add betadomain in Claude →Available as a connector in the Claude directory.

Step by step

Connect betadomain to Claude

Claude can talk to betadomain through a custom connector. Read tools work right away; purchase and account tools need a token (see below).

Open Claude and go to Settings → Connectors.
“Add custom connector” (sometimes called “Add MCP server”).
Enter the URL https://betadomain.de/api/mcp and save.
For read tools you are done — ask e.g. “Is mycompany.com available at betadomain?”.
For write tools (manage domains, start an order): create a token in the portal and store it as a Bearer-Token on the connector (header Authorization: Bearer <token>).

Step by step

Connect betadomain to ChatGPT

Works the same way via a custom connector — provided your ChatGPT plan supports custom connectors / MCP (e.g. developer mode or apps for business/enterprise plans). If you don’t see the option, your plan doesn’t offer it yet.

In ChatGPT open Settings → Connectors / Developer mode.
Add a new connector / MCP server.
Enter the URL https://betadomain.de/api/mcp.
For write tools, paste a personal access token as the bearer token (same as for Claude).

Reference

Available MCP tools

Read tools are open and rate-limited per IP. Write tools require a bearer token and only ever act on your own data.

Tool	What it does	Example input	Token?
`domain_check`	Checks a full domain (incl. extension) for availability and returns the annual prices (registration/transfer/renewal).	`{ "domain": "mycompany.com" }`	no
`domain_search`	Searches a name. With an extension exactly that one is checked; without one the popular extensions (.de, .com, .eu, .net, .org, .shop, .io, .dev) in parallel.	`{ "query": "mycompany" }`	no
`whois_lookup`	WHOIS/RDAP lookup. Returns only non-personal registry fields: status, dates, nameservers, registrar — no owner data (GDPR).	`{ "domain": "example.com" }`	no
`list_tlds`	Lists the supported extensions with annual prices. Optional category="popular", search="shop", limit/offset.	`{ "category": "popular" }`	no
`tld_price`	Annual prices of a single extension (registration, transfer, renewal).	`{ "tld": ".io" }`	no
`list_my_domains`	Lists the signed-in customer’s domains (name, extension, status, expiry, auto-renewal) — own only.	`{ }`	required
`start_order`	Starts an order (registration/transfer). Checks availability and prices server-side and returns a Stripe checkout link. No headless purchase.	`{ "items": [{ "domain": "mycompany.com", "type": "register" }] }`	required
`get_order_status`	Queries the status of your own order (status, amount, line items, date).	`{ "orderId": "…" }`	required

Authentication

Create a token

Write tools use a personal access token (PAT). Create one in the portal, use it as a bearer token, revoke it any time.

Sign in and open betadomain.de/account/profile → section “MCP / API access”.
Click “Create token”. The token (prefix bdk_live_) is shown exactly once — copy it now. We only store a SHA-256 hash.
Send it as header Authorization: Bearer <token>.
Revoke a token any time in the same screen — clients using it stop working immediately.

Up to 20 active tokens per account. A login is required to issue a token.

Direct access

Public REST API

Two read-only POST endpoints — no API key, no auth. Fair use: 30 requests/minute and 300/6 hours per IP.

POST /api/domain/check

curl -X POST https://betadomain.de/api/domain/check \
  -H "Content-Type: application/json" \
  -d '{"domain":"mycompany.com"}'

POST /api/domain/search

curl -X POST https://betadomain.de/api/domain/search \
  -H "Content-Type: application/json" \
  -d '{"query":"mycompany"}'

Machine-readable description: /openapi.json (OpenAPI 3.1).

Machine-readable

Discovery

Everything an AI system needs to find and understand our interfaces is published under well-known URLs.

/.well-known/mcp.jsonMCP server card — all capabilities & tools for agents
/.well-known/agent.jsonA2A agent card (agent-to-agent)
/.well-known/oauth-protected-resourceOAuth protected-resource metadata (bearer token)
/.well-known/oauth-authorization-serverOAuth authorization server (planned, not yet active)
/.well-known/api-catalogAPI catalog (RFC 9727 linkset)
/.well-known/auth.mdNotes for agents: what is public, where a human is needed
/openapi.jsonOpenAPI 3.1 of the public REST API
/llms.txtShort overview for AI systems (llms.txt)
/llms-full.txtFull text for AI systems

Honest limits

What agents cannot do

No headless purchase. start_order prepares everything server-side and returns a Stripe checkout link — payment and, if needed, identity verification (KYC) are completed by a human. Nothing is charged automatically.
WHOIS returns non-personal registry fields only (status, dates, nameservers, registrar) — no owner, admin or tech contacts (GDPR). For .de, DENIC provides limited data anyway.
Prices and availability are always resolved server-side against our live data — never trusted from client input.

Create a token View MCP server card