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 withfluxa-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
| Method | Path | Reference |
|---|---|---|
GET | /domain-search | Domain search |
GET | /email-finder | Email finder |
GET | /email-verifier | Email verifier |
GET | /author-finder | Author finder |
GET | /linkedin | LinkedIn finder |
GET | /phone-finder | Phone finder |
GET | /phone-validator | Phone validator |
GET | /email-count | Email count |
GET | /email-sources | Email sources |
GET | /email-format | Email format |
GET | /enrich | Email enrichment |
GET | /people/find | Person enrichment |
GET | /companies/find | Company enrichment |
GET | /combined/find | Combined enrichment |
GET | /technology | Technology |
GET | /location | Location |
GET | /similar | Similar domains |
GET | /domain-suggestions | Domain suggestions |
GET | /domain-status | Domain status |
POST | /reveal/search | Company 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:
Code
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
| Response | Cause | Fix |
|---|---|---|
402 with an accepts array | The request has no FluxA API key or payment | Send Authorization: Bearer with your key, or pay with the FluxA Wallet |
402 with insufficient_balance | Your AgentMarket balance can't cover the call | Top up at agentmarket.fluxapay.xyz/console |
To pay Tomba per request directly, without a Tomba account or a gateway, see Agent payments (MPP).