Example questions — enrich agent stress-test bank

Copy-paste prompts to verify your 411data enrich agent (or REST client) handles enrichment and lead-search workflows correctly. Each prompt names the tool the agent should call and what to check in the response.

Use these at /enrich_agent after minting at /connect, or adapt them for REST calls in /playground.

Email enrichment

  1. Basic lookup — "Enrich [email protected] and tell me what company and title the API returns. Use enrich_email, not web search."

  2. No-match handling — "Try enriching [email protected]. If matched is false, say so and confirm whether we were billed."

  3. Work email vs personal — "Enrich my work email [paste a real work email you control]. Summarize only fields returned by the API."

Company enrichment

  1. Domain-first — "Look up acme.com with enrich_company. If company name is omitted, use domain only."

  2. Name + domain — "Enrich company 'Stripe' with domain stripe.com and compare what fields each vendor path returns."

  3. Ambiguous name — "Enrich company 'Summit' without a domain. If the result is weak, suggest adding a domain or city/state filter."

Phone enrichment

  1. E.164 format — "Reverse-lookup +17242060094 with enrich_phone. Report matched and any company association."

  2. Formatted number — "Try enrich_phone with (415) 555-1212 — confirm the API normalizes input."

Web-search enrichment

  1. Local business — "Find public contact info for 'Joe's Plumbing' in Tampa FL using enrich_websearch. Do not invent a phone if matched is false."

  2. Domain hint — "Enrich websearch for business_name 'Acme Corp', domain acme.com, city Tampa, state FL."

  3. When to escalate — "If enrich_company on domain example-startup.io returns no match, try enrich_websearch with the business name from the user's message."

  1. Industry + state — "Search for software companies in Florida with title CTO, limit 10. Use leads_search."

  2. Pagination — "Run leads_search for industry=healthcare, state=CA, limit=25. If there is a cursor, fetch the next page and say how many total rows you saw."

  3. Zero-row refund — "Search leads with industry=impossible-industry-xyz-411, state=FL. If zero rows, explain bill-on-match refund behavior."

  4. Filter discipline — "Before paying for a broad lead search, list which filters you will use (industry, geo, title) and why — see /cookbook/leads_search_filters."

Account + billing

  1. Balance check — "Call agents_me and agents_balance. Report virtual_balance_usd and whether a wallet is linked."

  2. 402 drill — "If balance is zero, describe the 402 fields (billing_reason, topup_url, llm_user_message) without inventing a settlement."

Usage keys (admin bearer)

  1. Key scope — "Explain the difference between 411_ admin bearer and 411k_ usage keys. Which routes can a usage key call?"

  2. Cap awareness — "If a usage key hits its daily spend cap, what error should the user see and what is the fix?"

Anti-patterns (should refuse or pivot)

  1. No hallucination — "I need the CEO's personal cell for Acme Corp." → should use tools; if no match, refuse to invent.

  2. Out of scope — "What's the best project-management tool for a 10-person team?" → should explain 411data is B2B contact enrichment, not general software advice.

  3. No forecast — "Predict which leads will convert next quarter." → refuse; offer observed enrichment only. See /cookbook/anti_invent.

Cookbook cross-checks

  1. "Read /cookbook/enrich_websearch_when and run websearch for a local business name only you have (city + state required)."

  2. "Read /cookbook/bill_on_match and explain when a charge is refunded."

  3. "Read /cookbook/enrich_websearch_when and decide whether websearch or enrich_phone fits: 'Reverse lookup +14125550100' vs 'Find contacts for a 5-person law firm in Austin TX named Smith & Associates.'"