Atom.com — Premium Domains

Get domain registration Coinbase (USDC) pay link

get_domain_register_coinbase_pay_link

Read-only

Get a Coinbase checkout link, paid in USDC, to register a FRESH domain (an available domain that is NOT a curated Atom marketplace listing — for a listing use get_domain_purchase_coinbase_pay_link). Returns two URLs for the same payment: x402_url — an agent with an x402-capable crypto wallet (e.g. a Coinbase agentic wallet) pays it directly (POST, 402 Payment Required, signed retry); and checkout_url — the hosted page a human opens in a browser to pay with their own wallet. Use this when the user wants to pay with crypto/USDC, or when an x402-capable wallet is available in this session. term_years is derived server-side from the TLD.

Always present the exact server-computed price returned here (includes VAT where applicable) — never estimate or recompute it yourself. This tool charges nothing by itself.

RIGHT AFTER handing over the link (or paying x402_url), start polling get_coinbase_payment_status with the returned payment_code — keep calling it while status is 'pending' and stop_polling is false (each call waits ~10s server-side). If stop_polling turns true, stop and show its user_message exactly as given; check again when the user says they have paid. The domain is only registered once that reports status 'completed' (poll again while 'pending'). If the registry rejects the registration after payment it reports 'refunded' (credited to the Atom account balance).

If this reports error 'registrant_contact_required', ask the user for their name, phone, address, city, zip, and country, call create_registrant_contact with those, then retry. If it reports 'billing_country_required', the user must save a billing country on their Atom account first.

Input Schema

Name	Required	Description	Default
`domain`	Yes	The domain to register, including extension.

Output Schema

Name	Required	Description
`url`	Yes
`price`	No	Exact total the checkout charges.
`domain`	Yes
`success`	Yes
`currency`	No
`x402_url`	No	x402 payment endpoint for agent wallets: POST it, get 402 Payment Required, sign and retry. Prefer this over checkout_url when an x402 wallet is connected.
`term_years`	No
`vat_amount`	No
`checkout_url`	Yes	Hosted Coinbase checkout page — give this to a human to pay in a browser.
`payment_code`	Yes	Pass to get_coinbase_payment_status after paying.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 1, 2026

changedOutput schema / properties / checkout_url / description

Previous value: -"Coinbase checkout URL (x402-payable). Hand to an x402 wallet or the user."New value: +"Hosted Coinbase checkout page — give this to a human to pay in a browser."

addedOutput schema / properties / x402_url

Added value: +{
+  "description": "x402 payment endpoint for agent wallets: POST it, get 402 Payment Required, sign and retry. Prefer this over checkout_url when an x402 wallet is connected.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

AddedSep 30, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations cover safety (readOnlyHint=true, destructiveHint=false), and the description reinforces rather than contradicts them by stating 'This tool charges nothing by itself' and explaining the two returned URLs and the 402/POST signed-retry flow. It goes well beyond annotations by disclosing side-effect timing (domain only registered after status 'completed'), refund behavior, and polling semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the sibling disambiguation are front-loaded in the first sentence, and every subsequent sentence carries operational information (pricing rule, polling, error recovery). It is long, but the length is justified by the multi-step payment workflow rather than padding; a slightly tighter error-handling section would push this to a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a single-param tool with full schema coverage, an output schema, and annotations, this is complete: it covers what the tool returns (two URLs), what it does not do (no charge), how to complete the flow, and how to recover from the two documented error states. Nothing essential to correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter with 100% schema coverage, so the schema already does the work (baseline 3). The description adds value by constraining the domain to a fresh, available, non-listing domain and noting term_years is derived server-side from the TLD — meaning the agent needn't supply it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (get a Coinbase checkout link paid in USDC to register a fresh domain) and immediately disambiguates from the closest sibling by naming get_domain_purchase_coinbase_pay_link for curated listings. The 'FRESH domain, not a marketplace listing' distinction is exactly the kind of boundary an agent needs before choosing a tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use it ('when the user wants to pay with crypto/USDC, or when an x402-capable wallet is available') and names the alternative for the other case. It also provides conditional branches for error codes (registrant_contact_required, billing_country_required) and points to the required follow-up tool (get_coinbase_payment_status).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Atom.com — Premium Domains tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.