---
name: 411data
description: Agent-native lead and business-data enrichment (email, company, phone, websearch, lead search). Billing waterfall — virtual USD balance first (~$0.20 starting credit on wallet mint at /connect), then 402 + x402 v2 (EIP-3009 USDC on Base mainnet). Bazaar discovery at /discovery/resources.
version: 0.1.0
origin: https://411data.io
mcp_endpoint: https://411data.io/mcp
mcp_descriptor: https://411data.io/mcp.json
openapi: https://411data.io/openapi.json
openapi_free: https://411data.io/openapi-free.json
well_known_x402: https://411data.io/.well-known/x402
bazaar_discovery: https://411data.io/discovery/resources
tags: [leads, enrichment, b2b, email, company, phone, agent, x402, mcp, bazaar]
---

# 411data skill

This file teaches an LLM agent how to use the 411data service end-to-end.

## 0. Scope discipline — READ THIS FIRST

411data enriches **emails, companies, phones, and B2B leads** through
vendor waterfalls. Every input and output is stored for audit.

- **Answer using only the data returned by 411data tools.**
- If a tool returns no match, an error, or a 402 the user has not paid,
  **say so plainly**. Offer to broaden filters, register an agent token,
  settle x402, **prepay USDC** ([`/cookbook/prepay_deposits`](https://411data.io/cookbook/prepay_deposits)),
  or earn **free virtual credits** via session-summary
  ([`/cookbook/session_feedback`](https://411data.io/cookbook/session_feedback)).
  **Do not invent contact records to fill gaps.**
- **Bill-on-match:** enrichment and lead-search routes charge up front,
  then **auto-refund** when no usable match is found (`matched: false` or
  zero rows). See [`/cookbook/bill_on_match`](https://411data.io/cookbook/bill_on_match).
- **Before tackling a new question shape, scan the cookbook** at
  https://411data.io/cookbook — free worked examples for email waterfall,
  company-by-domain, lead-search filters, and websearch vs waterfall.
- **Refuse to invent data.** If enrichment returns no match, do not
  guess emails or phone numbers from the web. See
  https://411data.io/cookbook/anti_invent.

## 1. Mint an agent token

Wallet-bound mint (recommended): https://411data.io/connect

- Requires ≥ $1 USDC on Base at mint time (eligibility check only).
- Grants **$0.20 virtual USD** starting balance (~4 email enrichments at default pricing).
- Optional MPP allowance signature for hands-free x402 after balance hits zero.

Bearer format: `411_…` (admin) or scoped usage key `411k_…` (data routes only).

## 2. MCP tools

Connect to `https://411data.io/mcp` with `Authorization: Bearer 411_…`.

| Tool | Price | Purpose |
|------|-------|---------|
| `agents_me` | Free | Profile, balance, wallets |
| `agents_balance` | Free | Virtual USD balance |
| `enrich_email` | $0.050 | Single email enrichment |
| `enrich_company` | $0.050 | Company by name and/or domain |
| `enrich_phone` | $0.050 | Phone reverse lookup |
| `enrich_websearch` | $0.150 | LLM web-search business contacts |
| `leads_search` | $0.100 | Filtered B2B lead list |

Full descriptor: https://411data.io/mcp.json

## 3. REST equivalents

```bash
# Email enrichment
curl -X POST https://411data.io/api/v1/enrich/email \
  -H 'Authorization: Bearer 411_…' \
  -H 'Content-Type: application/json' \
  -d '{"email":"jane@acme.com"}'

# Company enrichment
curl -X POST https://411data.io/api/v1/enrich/company \
  -H 'Authorization: Bearer 411_…' \
  -H 'Content-Type: application/json' \
  -d '{"domain":"acme.com"}'

# Lead search
curl -X POST https://411data.io/api/v1/leads/search \
  -H 'Authorization: Bearer 411_…' \
  -H 'Content-Type: application/json' \
  -d '{"industry":"software","state":"FL","limit":25}'
```

## 4. Billing waterfall

1. **Virtual USD balance first** — every paid call debits `virtual_balance_usd`.
2. **402 + x402 only when balance is exhausted** — wallet MPP allowance or fresh USDC settlement on Base.

402 bodies include `billing_reason`, `virtual_balance_usd`, `connect_url`, `topup_url`, and `llm_user_message`.

## 5. Usage keys (admin → desktop LLMs)

Admin bearer (`411_…`) can create scoped keys at `/connect?action=usage-keys` or `POST /api/v1/keys`. Keys (`411k_…`) are limited to enrichment + lead routes and enforce per-key spend caps.

## 6. Further reading

- Developer guide: https://411data.io/developers
- Cookbook: https://411data.io/cookbook
- Pricing: https://411data.io/pricing
- x402 manifest: https://411data.io/.well-known/x402