Licensing
Terms for when register data is part of what you sell. If you only display it inside your own product, you do not need a licence.
Annual, and priced by volume, by which endpoints are in scope, and by how far redistribution extends. Tell us what you are building and we will come back with terms.
When you do not need one
If you display register data to support your own product — a supplier name on an invoice-processing screen, a seller’s verified state at onboarding, a number checked during tax processing — an ordinary paid plan covers it. You do not need a licence. Clause 4 of the terms asks you to carry the National Tax Agency attribution near that data, and that is the whole of it.
Three forms
API redistribution licence
For when the register data is itself what you sell. You call the API in real time and your customers buy Japan coverage from you. Annual fee, volume tiers, an SLA on the endpoints served from the stored corpus, and refresh commitments. No sublicensing: your own customers may receive the data, another provider who redistributes it again may not.
White-label
Unbranded access, and a dedicated endpoint where that is warranted.
Bulk data
Periodic dumps that you host. Base registers only — never the change history, and never the matching corpus.
Why the bulk form is restricted
The base registers are rebuildable by anyone from the same public sources, so a bulk copy of those costs you nothing in accuracy and costs us nothing to give. The accumulated cross-sectional change record — what changed across every entity on a given day — is not rebuildable after the fact, and neither is the matching corpus once it exists. Both are therefore excluded from a bulk licence and available through the API instead.
Attribution flows through
Japan’s public data terms permit redistribution; they do not permit unattributed redistribution. If a partner’s product drops the National Tax Agency attribution, that is our breach and not only theirs. Every licence therefore carries the obligation through to you, and to anyone you serve.
Scope of an SLA
An SLA covers the endpoints served from registers we hold and operate. Any source we proxy rather than store carries the upstream service’s availability rather than ours, so it is priced and committed separately rather than folded into one number. Daichodo is operated by a sole proprietor; the operator’s details are published in the commercial transactions disclosure, and agreement structure is part of the conversation.