A B2B enrichment API for Clay and Claude Code

Fyonta is a flat-rate B2B contact database and enrichment API. This post covers the two most common ways teams actually plug it in: as an HTTP enrichment column inside Clay, and as an MCP server for Claude Code. Same API key works for both — there's no separate Clay pricing tier or agent-specific plan.

What you need first

An API key. Sign up free and subscribe from the dashboard, or use an existing key — both integrations below use it exactly as-is.

Using Fyonta as an enrichment API in Clay

Clay's HTTP API column is a general-purpose way to call any REST API from a table and map the response into columns. Fyonta's endpoints are a standard REST API with header-based auth, so they drop in directly.

Step by step

1. In your Clay table, click + to add a column, search for HTTP API, and select it.
2. Switch to the Configure tab for manual setup (or describe what you want in the Generate tab and let Clay's AI assistant draft the config).
3. Set the method to GET and the endpoint to a Fyonta URL, for example:

   https://api.fyonta.com/v1/enrich/email-search

4. Add query parameters, referencing existing table columns where useful:

   company_url: /Company Domain
   first_name: /First Name
   last_name: /Last Name

5. Add your API key as a header. Rather than pasting it into every column, save it once in Clay's header account manager (Select header account → + Add account) so it's encrypted and reusable across columns:

   X-API-Key: YOUR_FYONTA_KEY

6. Set the response field path so Clay extracts just the email instead of the whole payload:

   data.email

7. Click Test against a single row, confirm the result, then run it across the table.

The same pattern works for any Fyonta endpoint — swap the URL and parameters for Phone Finder, Reverse Email Lookup, Domain Search, or Lead Search against our owned database. Full parameter reference is in the docs.

One setting worth getting right

Clay's HTTP API column has its own rate-limiting field (requests per timeframe). Set it at or under your Fyonta plan's limit — 200/min on Basic, 1,000/min on Pro — so Clay doesn't fire faster than Fyonta will accept and start returning 429s partway through a large table run.

Using Fyonta as an MCP server in Claude Code

Fyonta ships a remote MCP server at api.fyonta.com/mcp using Streamable HTTP transport — the transport Claude Code's own docs recommend for cloud-based MCP services. Connecting it is one command.

Add the server

claude mcp add --transport http fyonta https://api.fyonta.com/mcp \
  --header "X-API-Key: YOUR_FYONTA_KEY"

Verify it connected:

/mcp

You should see fyonta listed as ✔ Connected with 7 tools available. If you'd rather have it available across every project instead of just the current one, add --scope user to the command above.

What you get

Seven tools: search_leads against Fyonta's owned database, plus enrich_email_search, enrich_phone_search, enrich_reverse_email_lookup, enrich_domain_search, enrich_contact_finder, and enrich_company_finder — the same six enrichment endpoints available over REST. Full tool reference is on the MCP page.

Try it

Once connected, plain-language requests work directly:

Find the work email for the VP of Sales at acme.com

Who does jane.doe@acme.com belong to?

List Director-level contacts at companies in the IT Services industry in California

One key, two surfaces, one flat rate

Neither integration changes the pricing. Whether a lookup comes from a Clay table, a Claude Code MCP tool call, or a raw curl request, it's the same account, the same rate limit, and the same $99 or $499 monthly fee — not a separate credit pool for automations versus interactive use, which is how most enrichment vendors price it.

FAQ