Quick start — Enrich Agent

Step-by-step for humans using the hosted 411data enrich agent. For scripts and automation, see the developer guide (REST API).

Part 1 — Mint your bearer

  1. Go to 411data.io/connect.

  2. Connect a wallet on Base — recommended: Sign in with Base (passkey, no extension). Advanced: MetaMask, Rabby, or another browser extension.

  3. Fund the wallet with at least $1 USDC on Base — on Base (chain ID 8453), hold ≥ $1 USDC. This is a one-time eligibility check; 411data never withdraws it. On /connect, use Buy USDC on Base with Coinbase if your balance is low, or transfer USDC from another wallet.

  4. Mint your bearer key — connect → confirm Base + USDC balance → sign the sign-in message(s) → mint your key.

  5. Save your bearer key immediately — you'll get a token like 411_….

Copy it now (password manager, notes app, etc.).

Part 2 — Open the enrich agent

  1. Open /enrich_agent in the same browser where you minted (or restore your bearer via /connectRestore saved bearer).

  2. Pick a model tier (if prompted) and start chatting — ask enrichment questions such as "Enrich [email protected] and summarize what the API returns."

  3. Stress-test your setup — paste prompts from the example question bank to verify the agent calls enrich routes and handles no-match refunds correctly.

Quick reference

Step Where What
Wallet + mint /connect Get your 411_… bearer
Hosted agent /enrich_agent Chat-based enrichment
REST / scripts /developers curl + x402 walkthrough

Billing: wallet mints start with $0.20 virtual credit. Paid enrichment calls spend that balance first; when it hits zero, your wallet's pre-signed MPP allowance covers x402 charges automatically. See pricing and the developer guide for details.

Lost your bearer? If you still have it on another device, go to /connect and use Rotate bearer. If it's gone everywhere, mint a new agent from a different wallet — the old wallet stays permanently bound to the lost key.

Automation

For headless scripts, CI, or custom apps, use the REST API documented at /developers and /openapi.json. No external LLM client setup is required.