Interzoid
DATA · DATA & ANALYTICS
Similarity keys and standardisation for company, name, and address data on their key.
Connect Interzoid with Fabriq Developer
Your user pastes their Interzoid credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting Interzoid in practice
Interzoid passes its credential as a license query parameter on every call — api.interzoid.com/<endpoint>?license=… — so the key is captured by proxy logs, CDNs and referrer headers rather than living in a header. That one key covers the REST APIs, the wizards, the database connectors and the MCP server, all drawing on a single shared credit balance.
Scopes that draw scrutiny
license (query parameter)The single credential for everything Interzoid offers, tied to one credit balance. There are no scopes and no per-surface keys, so an agent’s key is also the key the wizards and database tools use.
Worth knowing
- Each API call consumes a set number of credits that depends on the endpoint, while the wizards and database tools deduct credits per record processed — so cost scales with data volume, not with call count.
- Usage from every surface lands in the same central balance, so an interactive wizard run and an automated batch job compete for the same credits with no way to ring-fence either.
- Registration is free and issues a working key plus starting credits automatically, which means a production-capable credential exists with no review step between signup and first call.
- Interzoid’s own guidance is to treat the license key like a password and rotate it if exposed — which is awkward advice for a value that has to appear in a URL.
Checked against API license keys (2026-09-29), Interzoid APIs (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Interzoid behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.