Lead enrichment, one API, one waterfall per job

superagnt Lead APIs sit on top of multiple upstream lead-data providers and expose a single unified surface per use case (email finder, email verifier, person/company enrich, person/company search, company discovery, domain emails, mobile finder, company intelligence). For each call you can pass an optional `fields[]` selector and an optional `max_cost_cents` budget. superagnt then runs its sources cheapest first, skips any source that would push spend past your budget, stops as soon as your fields are filled, and merges results into a normalized response shape. Provider names are never returned in the response. Pricing is hybrid: simple endpoints (e.g. intelligence signals, company discovery, people search) are flat-priced; waterfalls (email finder, email verifier, enrich, find-mobile, company search) are billed in the published `min – max` cents range based on what was actually spent upstream, plus a small markup. Bring one API key, get one bill, and let superagnt handle vendor selection, key rotation, and result merging.

Which upstream providers are used?

superagnt abstracts upstream providers entirely. Provider names are never returned in the response and we routinely add or rotate providers as we improve coverage and price. You only ever talk to one API.

How is pricing calculated for waterfall endpoints?

Each waterfall endpoint publishes a `min – max` cents range. superagnt runs its sources cheapest first until your `fields[]` are filled, skipping any source that would push spend past your `max_cost_cents` budget, then bills you the actual upstream cost plus a small markup. Flat-priced endpoints (intelligence signals, company discovery, people search, etc.) are always charged at the published rate.

What does `max_cost_cents` do?

It caps the maximum amount superagnt will spend upstream on a single call. Any source that would push spend past the cap is skipped, so some requested fields may stay missing. Lower values trade completeness for cost predictability.

How does field-based selection work?

Pass `fields[]` (e.g. `["email", "job_title"]`) and the waterfall stops as soon as every requested field has a value, which saves you money compared to always running the full enrichment.

Are bulk endpoints faster than calling enrich repeatedly?

Yes — bulk endpoints fan out requests in parallel and aggregate billing into a single deduction. You also get per-record budget control via `max_cost_cents_per_record`.

Can I use these APIs from AI agents?

Yes — that's the primary use case. All endpoints return structured JSON optimized for function calling in GPT-4, Claude, Gemini, and similar models. You can also wire superagnt into MCP-based agent runtimes.