Business-license data infrastructure
Know a business is licensed. Instantly, and always.
We turn thousands of fragmented government licensing sources into one queryable API — current status, resolved to a persistent entity, with full history. No portals, no PDFs, no manual checks.
Sourced entirely from public government licensing records.
The problem
License status carries real value, and nobody has it cleanly.
Insurers underwriting licensed operators, lenders assessing counterparty risk, and marketplaces onboarding sellers all depend on a counterparty holding a valid license — whatever that license is. Today that means manual portal checks, stale vendor lists, or trusting the applicant's own paperwork.
Fragmented
Thousands of authorities
Every state, county, and municipality publishes differently, on its own cadence and format. There's no single programmatic source of truth.
Stale
Point-in-time at best
A lookup tells you about today, if you're lucky. A lapse or suspension mid-term goes unnoticed until it costs someone.
No memory
History is thrown away
Almost no one retains how a license's status changed over time — the exact signal needed to monitor risk and spot trends.
What we do
One layer: aggregated, resolved, continuously refreshed.
We ingest public business-licensure records, resolve them to persistent entities, and deliver the result through the API and bulk feed. Three things make the data different.
01 · Current
Status on demand
Is this business licensed and in good standing right now — answered programmatically, not by a manual portal lookup.
02 · Resolved
Entity resolution
Licenses roll up to a persistent entity identifier, so one operator's licenses across locations — and over time, jurisdictions — become a single view a raw portal can't give you.
03 · Longitudinal
Accumulating history
Every record is captured as a dated, immutable snapshot, building a queryable status-change history — an asset that can't be back-filled after the fact.
Who it's for
Anyone whose risk depends on a counterparty's license.
Compliance & KYB providers
Embed license status as a verified attribute in existing onboarding and monitoring workflows — one integration, national coverage as it grows.
Commercial insurers
Verify and monitor license status across a book of policies, and catch a lapse or suspension mid-term instead of at renewal.
Lenders & underwriters
Confirm a licensed operator's standing at origination and continuously over the life of the relationship.
Marketplaces & platforms
Vet and re-check that sellers and counterparties remain licensed, automatically.
How it compares
There's no substitute for a live, resolved, historical record.
A manual check and a purchased list both answer a narrower question than the one you actually need answered.
| Capability | Manual portal check | Purchased list | Dokibase |
|---|---|---|---|
| Reflects status today | Only if you check today | Stale on delivery | Continuously current |
| Resolved to a persistent entity | No | No | Yes |
| Historical record of changes | No | No | Yes |
| Programmatic (API / feed) access | No | Sometimes, as a flat file | Yes |
| Scales across jurisdictions | One lookup at a time | Rarely maintained | Yes |
FAQ
Questions we hear a lot.
What exactly do you deliver?
The API and bulk feed of business-license data: current status, resolved to a persistent entity across locations and jurisdictions, plus a dated history of every status change. You integrate it as a verified attribute in your own workflow — we're infrastructure, not a lookup tool you use by hand.
How is this different from a manual portal check or a purchased list?
A portal check is a manual, point-in-time answer with no memory of what changed. A purchased list goes stale the moment it's delivered. We continuously ingest, resolve, and snapshot the underlying records, so what you get is current, deduplicated to a real entity, and queryable historically — programmatically, not by hand.
What is entity resolution, and why does it matter?
Individual license records get tied to a persistent entity identifier, so one operator's licenses across locations — and over time, jurisdictions — collapse into a single view instead of a pile of disconnected records a raw portal would give you.
Which jurisdictions and license types are covered?
Coverage is expanding based on design-partner demand. Get in touch and we'll walk through what's available today and what we're building next for your use case.
Is this a self-serve marketplace?
No. This is a direct API/feed integration built for a small number of design partners right now, not a self-checkout data marketplace. Access starts with a conversation.
How do I get access?
Reach out at [email protected] and tell us about your workflow — we're onboarding design partners and shaping the roadmap around what they actually need.
Design partnerships
If verifying business licenses is a real cost in your workflow,
we'd like to learn how you handle it today.
We're onboarding a small number of design partners and building the license types and jurisdictions they need first.
Start a conversation