Documentation
What opendata is
opendata is a public data API catalog that turns recurring screening, research, and monitoring work into stable endpoints.
Best for
Teams that need repeatable public-data lookups with one workspace, one key, and a clear path from search to export.
What it is
opendata packages public records into stable APIs so teams can reuse the same request path for screening, research, monitoring, and export work.
- • One API key and one request pattern across the catalog
- • Packaged products instead of stitching every source by hand
- • Designed for repeatable lookups, not one-off scraping jobs
Who it is for
It is built for teams that need repeatable public-data lookups and a clear path from search to answer.
- • Compliance and KYB analysts
- • Procurement and sourcing teams
- • Research, monitoring, and operations workflows
Best fit
Use opendata when the job is screening, monitoring, research, or export across public records.
- • Recurring lookups that need stable outputs
- • Teams that want one workspace for docs, products, and billing
- • Workflows that benefit from a single key and plan model
Not a fit
It is not the right choice when you need private internal data, bespoke ingest, or a transactional application backend.
- • Private datasets that never need a public API surface
- • Custom ETL-heavy warehouses built from raw source scraping
- • Real-time transactional systems with per-request custom logic
Start from the answer, then move to the right entry point.
Most teams validate the first request in Playground, choose a solution or product page, then return here when they need the short definition again.