TombaTomba
Start free
  • Documentation
  • API reference
  • SDKs & CLI
  • AI & MCP
  • Integrations
  • Enterprise
  • Migration guides

Find, verify and enrich B2B contacts from public sources, in the app, your spreadsheet or through the API.

GDPR & CCPA

// docs

  • API changelog
  • Support options
  • Security

// platform

  • Dashboard
  • Pricing
  • API status

// resources

  • Help center
  • Product updates
  • TombaBot crawler

// company

  • Website
  • Contact us
  • Edit or remove your data

© 2021–2026 Tomba.io

  • Terms of service
  • Privacy policy
  • Cookie policy
  • Security policy
  • GDPR
  • CCPA
Integrations overview
Automation
Apify
Tools
OrthogonalFluxA AgentMarket
Integrations

FluxA AgentMarket

FluxA AgentMarket is a marketplace of paid APIs for AI agents. It lists Tomba and forwards requests to 20 Tomba endpoints through its router. FluxA builds, prices, and supports this integration: you authenticate with a FluxA API key or the FluxA Wallet and pay FluxA, and the requests don't use your Tomba credits. The listing is agentmarket.fluxapay.xyz/marketplace/apis/tomba.

Prerequisites

  • A FluxA API key, created at agentmarket.fluxapay.xyz/keys. Calls made with the key are paid from your AgentMarket balance.
  • Or, to pay per call in USDC on Base instead: the FluxA Wallet CLI (npm install -g @fluxa-pay/fluxa-wallet), connected to your FluxA wallet with fluxa-wallet connect --client "My agent".

You don't need a Tomba account. Setup, billing, and support questions go to FluxA.

Connect an agent

The listing publishes a skill file with every endpoint, its parameters and price, and the payment steps: agentmarket.fluxapay.xyz/marketplace/apis/tomba/skills.md. Give that URL to Claude Code, Codex, or another agent that can make HTTP requests, then ask it to find or verify an email. Without the FluxA Wallet, the agent asks you for a FluxA API key before its first call.

Call Tomba with a FluxA API key

Send requests to https://router.fluxapay.xyz/api/tomba followed by the Tomba path without /v1, with the key as a bearer token. The parameters are Tomba's, so the API reference applies.

The X-Balance-Charge response header gives what the call cost and the balance left. GET https://router.fluxapay.xyz/api/tomba lists the endpoints with FluxA's current price for each.

A FluxA API key spends your AgentMarket balance. Load it from an environment variable or a secrets manager, never from source code.

Endpoints

MethodPathReference
GET/domain-searchDomain search
GET/email-finderEmail finder
GET/email-verifierEmail verifier
GET/author-finderAuthor finder
GET/linkedinLinkedIn finder
GET/phone-finderPhone finder
GET/phone-validatorPhone validator
GET/email-countEmail count
GET/email-sourcesEmail sources
GET/email-formatEmail format
GET/enrichEmail enrichment
GET/people/findPerson enrichment
GET/companies/findCompany enrichment
GET/combined/findCombined enrichment
GET/technologyTechnology
GET/locationLocation
GET/similarSimilar domains
GET/domain-suggestionsDomain suggestions
GET/domain-statusDomain status
POST/reveal/searchCompany search

Pay per call with x402

Without a key, the router answers a paid endpoint with 402 Payment Required and an x402 accepts array priced in USDC on Base. The FluxA Wallet pays it within a spending mandate you approve once. With the CLI connected (see Prerequisites) and jq installed:

TerminalCode
URL="https://router.fluxapay.xyz/api/tomba/email-verifier?email=jane.doe@stripe.com" # A budget of 1 USDC (amounts are in USDC atomic units), valid for 7 days. # Open the printed link and approve the budget before the wait ends. MANDATE=$(fluxa-wallet mandate-create --desc "Tomba lookups" --amount 1000000 --seconds 604800 --currency USDC) echo "$MANDATE" | jq -r .data.authorizationUrl MANDATE_ID=$(echo "$MANDATE" | jq -r .data.mandateId) fluxa-wallet mandate-status --id "$MANDATE_ID" --wait 300 # Pay the 402 response, then repeat the request with the payment. PAYMENT=$(fluxa-wallet x402-v3 --mandate "$MANDATE_ID" --payload "$(curl -s "$URL")" | jq -r .data.xPaymentB64) curl "$URL" -H "X-Payment: $PAYMENT"

Reuse the mandate for later calls until its budget or time runs out. FluxA's x402 payment guide covers mandates, agent IDs, and payment errors.

Troubleshooting

ResponseCauseFix
402 with an accepts arrayThe request has no FluxA API key or paymentSend Authorization: Bearer with your key, or pay with the FluxA Wallet
402 with insufficient_balanceYour AgentMarket balance can't cover the callTop up at agentmarket.fluxapay.xyz/console

To pay Tomba per request directly, without a Tomba account or a gateway, see Agent payments (MPP).

Last modified on November 19, 2026
Orthogonal
On this page
  • Prerequisites
  • Connect an agent
  • Call Tomba with a FluxA API key
  • Endpoints
  • Pay per call with x402
  • Troubleshooting
curl "https://router.fluxapay.xyz/api/tomba/email-finder?domain=stripe.com&first_name=Jane&last_name=Doe" \ -H "Authorization: Bearer $FLUXA_API_KEY"