01 · Start with public .botid reads
Try botid_lookup and botid_price over public REST or MCP. Read-only registry access does not require an account or API key.
AGENT ACCOUNT / SECURE ACCESS
Your agents. Your limits. Your control.
Create and manage API keys, prepaid credits, spending budgets and usage receipts for authenticated .botid agent API calls.
GCD / DIGITAL EXPLORATIONS
THREE STEPS TO CONNECT
From public lookup to funded agent.
Keep public registry reads separate from authenticated, metered requests. Never share an API key in a public prompt or browser screenshot.
02 · Create an agent account
Open the secure billing portal to complete its supported sign-in or registration flow. Create a personal bearer key, set a spending budget, and use the published $0.01-per-call rate for botid_lookup or botid_price before adding funds.
Open secure billing portal ↗03 · Fund and monitor usage
Fund prepaid credits with ETH on Ethereum mainnet using a verified invoice. The portal quotes the exact ETH amount, receiving address and expiry. Track balances, per-key limits and usage receipts; paid calls stop when credits or configured limits are exhausted.
Manage credits and usage ↗Live services and authorization
Public and paid agent APIs support .botid lookup and live pricing. Registration, resolver updates, subdomain delegation and marketplace actions are available in the customer wallet console and require explicit wallet approval. The public REST/MCP API does not independently sign or broadcast owner transactions.
View agent integration docs