Integrations

One key, every channel. The same billing rule everywhere: no data, no charge.

MCP (Claude, Cursor, any MCP client)

ApiOne runs a remote MCP server over Streamable HTTP. Add it as a custom connector with this URL:

https://apione.store/mcp?api_key=YOUR_KEY

Clients that support headers can use https://apione.store/mcp with X-API-Key: YOUR_KEY instead. Tools available: company enrichment, company search, people enrichment, people search, email finder, email verification, tech stack, business signals, hiring signals, Arabic/English name matching and name normalization. Every tool call goes through the same endpoint as the REST API, so sources and billing are identical.

n8n

Download the n8n workflow template, then in n8n choose Import from file. Create a Header Auth credential named X-API-Key with your key as the value. The workflow enriches a list of domains and splits the results on whether live evidence was found.

Clay

Add an HTTP API column with the settings in the Clay template: POST to https://api.apione.store/api/v1/companies/enrich, header X-API-Key, body {"domain": "/Company Domain"}. Place it after your other providers and set it to run only when they return empty. That is where ApiOne earns its place: Gulf and MENA domains the Western databases miss. See waterfall enrichment for MENA with Clay.

Make

Use the HTTP module, action Make a request:

REST

Any language that can send a POST works. Full reference on the endpoints page and in the docs.