Interzoid batch data enrichment
Interzoid batch data enrichment. No file needed, JSON in and JSON out: POST up to 100 records as a JSON array (objects such as {"company":"IBM","id":7}, plain values, or row arrays) and get JSON back, with each record's enriched fields appended. Multilingual: add the optional language parameter (for example language=German, language=fr, or language=Japanese) to get enriched results from the premium intelligence functions in any of 16 supported languages (French, German, Italian, Spanish, Japanese, Portuguese, Mandarin, Arabic, Dutch, Greek, Turkish, Korean, Swedish, Vietnamese, Thai, Indonesian), at the same per-record price. Priced per record by function and billed by exact record count, up to 100 records per job (total = per-record price x number of records). Price tiers: $0.01/record, $1.00 for 100 records (standardization, translation, parsing, and classification); $0.05/record, $5.00 for 100 records (X handle lookup); $0.10/record, $10.00 for 100 records (business name and domain lookup); $0.25/record, $25.00 for 100 records (business, contact, property, and financial intelligence, plus custom data); $0.35/record, $35.00 for 100 records (customs duty rates). Call with your records (POSTed JSON, or a CSV/TSV file URL in the connection parameter) and a function to receive an exact quote. Unsupported languages return English. Every function with its inputs, outputs, price, and a ready-to-run example: GET https://enrich-api.interzoid.com/functions (free); full guide: https://enrich-api.interzoid.com/llms-full.txt.
Paid test badge: not yet. The checks above are free: we call the tool without paying and read the payment request it sends back. The Verified badge needs paid calls whose answers match the promised output, and nobody can buy a badge.
Endpoint
GET https://enrich-api.interzoid.com/enrich
| Category | Company and compliance |
|---|---|
| Provider host | enrich-api.interzoid.com |
| Networks | eip155:8453 |
| Payment schemes | exact |
| Self-reported calls, 30 days | 2 from 1 payers (the provider's figure, not ours) |
Our checks, last 30 days
| Day | Result | HTTP | Asked | Time |
|---|---|---|---|---|
| 2026-09-30 | valid payment request | 402 | $23.00 | 1147 ms |
Example input (from the provider)
{
"method": "GET",
"queryParams": {
"connection": "https://dl.interzoid.com/csv/companies.csv",
"filetype": "csv",
"function": "business-info",
"lookup_column": "1"
},
"type": "http"
}
Promised output schema (from the provider)
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"input": {
"additionalProperties": false,
"properties": {
"method": {
"enum": [
"GET"
],
"type": "string"
},
"queryParams": {
"properties": {
"connection": {
"description": "Optional. Public URL (http/https) of an input CSV/TSV file, or an S3 object key. Not needed for up to 100 records: omit it and POST the records as a JSON body instead (objects, values, or row arrays), and the response is JSON.",
"type": "string"
},
"filetype": {
"description": "Optional. For a file: its format, csv or tsv. For POSTed JSON records: the output format, json (default), csv, or tsv.",
"type": "string"
},
"function": {
"description": "Enrichment function, for example business-info, email-trust-score, industry-codes, org-standard, or custom. Each has its own inputs, output fields, and per-record price: GET /functions returns the full catalog with a ready-to-run example for each, and /llms-full.txt is the complete guide.",
"enum": [
"address-parse",
"building-profile",
"business-info",
"business-info-domain",
"business-info-name",
"buying-signals",
"city-standard",
"company-verification",
"competitor-analysis",
"country-standard",
"custom",
"customs-duty-rates",
"email-domain-type",
"email-trust-score",
"entity-type",
"esg-profile",
"eu-vat-rates",
"executive-profile",
"facilities-profile",
"gender-from-name",
"gov-contracts",
"industry-codes",
"ip-profile",
"irs-per-diem-rates",
"muni-issuer-profile",
"name-origin",
"org-standard",
"parent-company",
"phone-profile",
"private-company-deal-intel",
"property-history",
"sales-use-tax-rates",
"sic-codes",
"state-standard",
"stock-analysis",
"tech-stack",
"translate",
"university-info",
"x-handle"
],
"type": "string"
},
"language": {
"description": "Optional. Get enriched results in the language of your choice, applied to the whole job. Supported languages (code and English name): fr (French), de (German), it (Italian), es (Spanish), ja (Japanese), pt (Portuguese), zh (Mandarin), ar (Arabic), nl (Dutch), el (Greek), tr (Turkish), ko (Korean), sv (Swedish), vi (Vietnamese), th (Thai), id (Indonesian). Default English. Taken by the premium intelligence functions (for example business-info, parent-company, executive-profile, industry-codes, and custom); GET /functions shows supports_language for each function, and /.well-known/x402.json lists them under languageSupport. Same per-record price in every language. The language value may be a two-letter code, an English name, or the native name, and is not case-sensitive. An unsupported language, or a function that is not a premium function, returns English; it is never an error. Output column names do not change.",
"type": "string"
},
"lookup_column": {
"description": "Optional. For a file or POSTed row arrays: 1-based column index of the value (company, email, name, etc.) the function looks up. Some functions use a different input name (for example email_column); see GET /functions. Not needed for POSTed plain values with a single-input function.",
"type": "string"
},
"lookup_field": {
"description": "Optional. For POSTed JSON objects: the field that holds the lookup value, for example lookup_field=company. Other inputs use <input>_field. Not needed when the objects have a single field or a field named like the input (lookup, email, org, and so on). Each object is returned with the enriched fields appended.",
"type": "string"
}
},
"required": [
"function"
],
"type": "object"
},
"type": {
"const": "http",
"type": "string"
}
},
"required": [
"type",
"method"
],
"type": "object"
},
"output": {
"properties": {
"example": {
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}
},
"required": [
"input"
],
"type": "object"
}