Build with Bavlio

Two APIs serve the same B2B data. Pick by integration style.

SaaS API

Traditional API with API keys

For server-to-server workflows on a Bavlio plan. Authenticate with an API key, consume credits from your subscription, get dashboards and audit logs. Best when the integration lives inside your team's own stack.

• API-key auth against your workspace
• Usage counts against your SaaS plan credits
• Organization-level billing + audit logs
• Standard REST semantics

SaaS API docs See plans

x402 API

Pay-per-call in USDC on Base

For AI agents with their own CDP wallet. No Bavlio account, no API key — each request carries a signed USDC authorization that settles per call on Base mainnet via the x402 protocol.

• No account, signup, or credit card
• 0.003–0.012 USDC per call, settled on-chain
• 5 endpoints: email verify, validate, find, LinkedIn URL, prospect search
• Listed on AgentCash, x402scan, x402.direct, x402 Bazaar

x402 API docs Swagger UI

Which one should I use?

SaaS API if you are a Bavlio customer automating workflows inside your own systems, want spend capped by your monthly plan, and prefer dashboards over on-chain settlement.

x402 API if you are an AI agent (or build one) that needs to pay for B2B data on demand without a human-in-the-loop signup — one signed request, one paid answer, no subscription.

Same data under the hood. Different auth + billing shape. Full OpenAPI spec at api.bavlio.com/openapi.json (Swagger UI at /docs, ReDoc at /redoc).