instadomain

buy_domain_crypto

Start the purchase flow for a domain using USDC crypto payment (x402 protocol).

Autonomous two-step payment flow — no browser required:

Step 1: Call this tool to reserve the domain and get a pay_url. Step 2: Pay the pay_url using your x402 wallet:

If you have Coinbase Payments MCP: call its x402 payment tool with the pay_url.
Otherwise: run curl -L <pay_url> — your x402-enabled HTTP client will handle the 402 handshake and USDC payment on Base automatically.

After payment succeeds, call get_domain_status(order_id) to poll until registration is complete (usually under 60 seconds).

The registrant contact details are required because the domain will be registered in the buyer's name (they become the legal owner). WHOIS privacy is enabled by default, so these details are not publicly visible.

IMPORTANT: Before calling this tool, you MUST first call check_domain to get the price and confirm it with the user.

Args: domain: The domain to purchase (e.g. "coolstartup.com"). first_name: Registrant's first name. last_name: Registrant's last name. email: Registrant's email address. address1: Registrant's street address. city: Registrant's city. state: Registrant's state or province. postal_code: Registrant's postal/zip code. country: 2-letter ISO country code (e.g. "US", "GB", "DE"). phone: Phone number in format +1.5551234567. org_name: Organization name (optional, leave empty for individuals).

Returns: Dict with order_id, pay_url (full URL to pay via x402), price_usdc, price_cents, network, and USDC contract address.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	Yes
`email`	Yes
`phone`	Yes
`state`	Yes
`domain`	Yes
`country`	Yes
`address1`	Yes
`org_name`	No
`last_name`	Yes
`first_name`	Yes
`postal_code`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A5/5.0

Behavior5/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that this tool only reserves and returns a pay_url, that payment happens externally via x402/curl, that no browser is required, that registrant details become public WHOIS (though privacy is enabled), and that polling is needed for completion. This is comprehensive for a financial mutation tool.

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

Conciseness5/5

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

The description is organized with numbered steps, an IMPORTANT note, and labeled Args/Returns sections. Every sentence adds operational value, and the length is justified by the tool's complexity. There is no redundancy or filler.

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?

The description covers the entire lifecycle: prerequisite price check, reservation step, payment execution options, post-payment polling, legal ownership context, input parameter formats, and return fields. For a multi-step purchase flow with no annotations, this is nearly complete and leaves the agent well-equipped to invoke and follow through.

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

Parameters5/5

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

Schema description coverage is 0%, but the Args section thoroughly documents all 11 parameters with meaningful semantics: formats for phone and country, optional org_name, example for domain, and clear labels for registrant fields. This fully compensates for the bare schema, making parameter usage unambiguous.

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?

The description opens with a specific action: 'Start the purchase flow for a domain using USDC crypto payment (x402 protocol).' It names the resource, the verb, and the payment method, clearly distinguishing it from sibling tools like buy_domain and buy_domain_mpp by emphasizing crypto/x402 and the two-step flow.

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?

The description gives explicit when-to-use guidance: 'Before calling this tool, you MUST first call check_domain to get the price and confirm it with the user.' It also details the post-payment step (poll get_domain_status) and provides alternative payment methods (Coinbase MCP or curl), giving the agent a complete operational sequence.

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

All instadomain tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool targets a distinct action or payment method. The three buy tools are clearly differentiated by payment flow (Stripe checkout, crypto x402, Stripe MPP) with explicit guidance on when to use each. All other tools have unique purposes (check, status, renew, transfer).

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using lowercase snake_case (e.g., check_domain, suggest_domains, verify_transfer_code). There are no mixed conventions or ambiguous prefixes.

Tool Count5/5

With 12 tools, the set is well-scoped for a domain purchase and management service. Each tool covers a necessary step in the workflow (check, buy via 3 methods, status, renew, transfer), without unnecessary bloat.

Completeness4/5

The tool surface covers the core domain lifecycle: check availability, purchase (with multiple payment options), renew, and transfer (code request, verify, unlock). Minor gaps like listing owned domains or managing DNS are absent, but the primary use case is well-supported.

Resources

Need Help?