Domain discovery in one HTTP call

How It Works

• 1
  Install the SDK

  npm install @x402/fetch @x402/evm viem

• 2
  Set your wallet key

  One environment variable: PRIVATE_KEY. That’s the only config.

• 3
  Call fetch()

  Payment happens automatically. You get JSON back with domain suggestions or availability status.

Scout beta

One payment buys the outcome: send a naming brief, get back a ranked shortlist with per-entry evidence — availability verified against the registry, trademark and web diligence with sources.

POST /scout · $0.15 quick (brainstorm → expand → screen → rank) · $0.50 deep (adds registry-precise verification + diligence) · the amount you pay selects the tier.

# Start a job (x402 payment selects the tier; unpaid call returns the price menu)
curl -X POST https://finddomain.io/scout?tier=deep \
  -H "payment-signature: <x402 payload>" \
  -d '{"brief": "tea subscription startup, playful, .com or .io"}'
# => {"job_id": "…", "status_url": "/scout/…", "tier": "deep"}

# Poll for free until done
curl https://finddomain.io/scout/JOB_ID

Any stage that falls back is named in the response’s degraded list — a thinner answer is visibly thinner. Also available as MCP tools scout_start / scout_status.

Pricing

Prices in USDC on Base mainnet (ERC-20, eip155:8453). $0.005 = 5,000 atomic units.

Parameters

* Required

{
  "results": [
    { "domain": "tea.com", "subdomain": "tea.", "zone": "com" },
    { "domain": "tea.house", "subdomain": "tea.", "zone": "house" },
    { "domain": "tea.cafe", "subdomain": "tea.", "zone": "cafe" }
  ]
}

{
  "domain": "tea.com",
  "zone": "com",
  "status": "active",
  "tags": "generic"
}

Suggestions don’t include availability — use /status to check a specific domain.

Quickstart

import { x402Client, wrapFetchWithPayment } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

const client = new x402Client();
registerExactEvmScheme(client, {
  signer: privateKeyToAccount(process.env.PRIVATE_KEY),
});
const fetch = wrapFetchWithPayment(globalThis.fetch, client);

// Domain suggestions
const suggestions = await fetch("https://finddomain.io/suggest?query=tea");
console.log(await suggestions.json());

// Precise availability
const status = await fetch("https://finddomain.io/status?domain=tea.com");
console.log(await status.json());

import os
from x402.client import Client
from eth_account import Account

account = Account.from_key(os.environ["PRIVATE_KEY"])
client = Client(account)

# Domain suggestions
suggestions = client.get("https://finddomain.io/suggest", params={"query": "tea"})
print(suggestions.json())

# Precise availability
status = client.get("https://finddomain.io/status", params={"domain": "tea.com"})
print(status.json())

Agent Integration

finddomain.io is built for AI agents. Any agent with an x402-compatible wallet and USDC on Base can call the API autonomously — no user interaction required, no API key to manage.

curl https://finddomain.io/skill.md

The skill file documents all endpoints, the x402 payment flow, example responses, and error handling.

What is x402?

x402 is an open HTTP payment protocol built on the 402 Payment Required status code. When a client calls a protected endpoint, the server responds with a machine-readable PAYMENT-REQUIRED header describing the price and payment address. The client signs a USDC authorization (EIP-3009, gasless) and retries. The server verifies and settles on-chain, then serves the resource. No accounts, no API keys — payment is the authentication.

Learn more at x402.org