API-first · Company data from DACH
Company data via API.
The way you need it.
Whatever your stack looks like: query via REST or through your AI assistant, combine the filters any way you like, and pay only for what you get. Every value with its source and date.
$ curl -X POST \ https://indizio.rexago.com/api/v1/companies/search \ -H "Authorization: Bearer $INDIZIO_KEY" \ -d '{ "postal_prefixes": ["70","71"], "employees_min": 20, "hiring_since": "2024-06-01" }'
{ "data": [{ "id": 10176026, "name": "…", "legal_form": "GmbH", "address": { "city": "Stuttgart", … }, "provenance": { "company_record": { "source": "…", "recorded_at": "2026-06-12" } } }, …], "meta": { "total": …, "dataset": { … } } }
source and recorded_at on every data point. Real response structure — values only the dataset knows are left out as “…” rather than invented.
Sound familiar?
Stale lists, blind scores, five IDs. Doesn’t have to be.
On the left, what costs you time. On the right, what Indizio delivers instead — backed up on every value.
Without
The list is two years old.
And nobody notices until the number goes dead.
With Indizio
Every value has a date.
recorded_at sits on every field. You see how old it is before the first call — and drop what is too old for you.
"recorded_at": "2026-06-12"
Without
The score says 87.
Based on what? It doesn’t say.
With Indizio
No score. A source.
source tells you where a value comes from: commercial register, job posting, company website. What that is worth to you is your call.
provenance.source
Without
Five vendors, five company IDs.
And no join between them.
With Indizio
One company ID for everything.
Master data, job postings and register announcements share the same ID. One query: companies with 20+ staff around Stuttgart that have been hiring since June.
"employees_min": 20, "hiring_since": "2024-06-01"
Without
All you have is a website address.
And you need the company behind it — today, not next week.
With Indizio
Send us the URL.
You get the company back: name, seat, legal form, size, register data. One call, one record. No match, no cost.
POST /api/v1/enrich/company
Interfaces
Two doors. One key. You decide what happens behind them.
REST for your code, MCP for your AI assistant. Same key, same billing — and no rules about what you work with.
REST API
Eight endpoints under /api/v1: company search, job postings, register announcements, enrichment. JSON in, JSON out — from any language that speaks HTTP.
As in the request above: company attributes, region and hiring activity in a single query.
MCP server
Your AI assistant connects at /mcp to ten tools and translates your question into the right filters itself.
“Which companies in Bavaria have balance-sheet data on file and are currently hiring?”
Sign in instead of copying keys: applications that support it connect via OAuth 2.1 — you confirm once and can always see what is connected.
Works with what you already use.
Guides for Claude, ChatGPT, Cursor, Claude Code, n8n, Python and curl are in the customer area. Everything else speaks HTTP — and therefore to Indizio.
How it works
Three steps to your first query
Create an account
Done in a minute once sign-up opens. Today this step is not possible yet.
Get a key
One key for both doors, REST and MCP. Or sign your assistant in via OAuth.
Send your first query
Via curl, from your own code, or as a question to your assistant.
Pricing
Pricing
Pricing follows shortly.
Prices are not settled yet. Until they are, we would rather quote you none than one that changes again.
Indizio is aimed exclusively at businesses (§ 14 German Civil Code). We do not enter into contracts with consumers (§ 13).
Why Indizio
Data from people who have done this since 2008.
Indizio is the API access to REXAGO’s company dataset. Market leaders have bought that same dataset as address lists since 2008 — you get it as an interface, with source and date on every value.
Counted on 2026-09-01 against the production dataset — not a marketing figure. The cutoff date is in every API response under meta.dataset.
German provider, European processing
REXAGO Information GmbH, based in Germany. Processed under the GDPR, servers in Germany. Transport is encrypted end to end (TLS 1.3); plain HTTP is redirected to HTTPS.
Evidence, not claims
Every response carries meta.dataset with the dataset’s cutoff date, every value its source. What we cannot back up is not on this page.
What customers say about the data
Mit Rexago360 finden wir haargenau unsere Zielgruppen. Die Daten sind im Vergleich zu den Mitbewerbern sehr hochwertig und preisgünstig.
Die umfangreichen Branchenzuordnungen, die schnellen Selektionen und nicht zuletzt die positiven Qualitätsmerkmale der Adressen haben uns überzeugt, Premiumkunde bei Rexago zu werden.
Durch die hohe Datenqualität unterstützt Rexago nach erfolgtem Produkt Relaunch die Markteinführung unserer neuen Software im Bereich „Business Solutions" maßgeblich.
Said about REXAGO’s products — the dataset Indizio delivers via API.
Beta
What we are working on
Indizio is in beta. The interfaces already run against the real dataset — what we are still finishing is everything around them. Until that is done, we are not opening accounts yet.
In progress
- Accounts that manage themselves: sign up, issue keys, review usage and transactions — without going through us.
- Billing where the cost of a call is known before you make it.
- The legal texts: privacy policy and data processing agreement, reviewed by lawyers rather than written by us.
Already in place
- Company data with evidence — every field carries its source and the date it was recorded.
- Two doors into the same data: REST and MCP — plus OAuth for assistants that support it.
- A query that finds nothing costs nothing: you are billed per delivered record.
Questions about Indizio? Write to [email protected].
API-first · Company data from DACH
Your next list — dated.
One account, one key, one query. The rest is in the response.