apis.credit · the use restriction · the document permitted_use.terms resolves to
The use restriction.
restrictionCommercial credit, KYB, and simulation use only. No consumer purpose. This restriction is a term of the call.
This is the whole restriction. Everything below defines its terms, states the two statutory limbs it turns on, names the four facts that would falsify it, and prints the closed list on the other side of the line. It is the same text the API types into every response as the permitted_use object, and it is served here because a term you cannot fetch is not a term. A machine twin of this document is at /use-restriction.json.
The COMMERCIAL regime
"regime": "COMMERCIAL" means the subject of every record served from this door is an entity, and the purpose of every call is a commercial one. The SKUs are commercial: business credit on entities, KYB, lien intelligence from public filing offices, and simulation arithmetic on published criteria. "fcra_consumer_report": false travels on the record itself.
A request declared for a consumer purpose does not return a thinner file. It returns a typed BLOCKED with reason PURPOSE_OUT_OF_REGIME and cure CONSUMER_REGIME_NOT_SERVED, and nothing is metered, because a refusal is not a product.
Not a consumer reporting agency
apis.credit is not a consumer reporting agency as defined by the Fair Credit Reporting Act, and nothing served from this door is a consumer report. The reason that holds is worth stating, because a posture you cannot check is an adjective. A consumer report is defined by two limbs and both have to be true:
- information bearing on a consumer's credit standing,
- assembled for the purpose of establishing eligibility for consumer credit or another purpose the statute enumerates.
This door is built on the first limb, not the second.
Its subjects are entities: a registered company, a filing office's own record of a lien against a debtor, the entity's own bank data under the entity's own consent, and arithmetic against criteria a Lender published. There is no consumer subject, which is why no permissible purpose is required and why none is claimed. That is a fact about the product, not a position the platform took.
The four falsifiers
Four things would change the answer, and they are named here so you can check them rather than trust them.
- A subject who is a natural person. No row on this door takes one, and an Obligor-Guarantor appears in a record as a named party and never as a scored subject.
- A consumer purpose. Declared, it is refused: typed
BLOCKED, nothing metered. - Mixing. Consumer-report data is never pooled into a response on this door, because one mixed field would convert the whole response.
- Furnishing. Sending data to a bureau carries accuracy and dispute duties of its own, which is why the furnishing row in the register is stamped ROADMAP and will not ship without the dispute investigation that legally comes with it.
If any of the four ever changes, this document changes with it in the same commit, and the stamps change first.
The closed list, on the other side of the line
It is worth saying plainly what is on the other side of that line, since a boundary you cannot see the edge of is not much use. A consumer report may be furnished only for a purpose the statute enumerates, and the list is closed:
- a credit transaction involving the consumer,
- the consumer's own written instructions,
- employment,
- insurance underwriting,
- a legitimate business need in a transaction the consumer initiated,
- and review of an account already held.
Each one presupposes a transaction this door does not have. It extends no credit, holds no account, takes no written instruction from a consumer, underwrites nothing, and hires nobody. And a permissible purpose is a recorded fact about a transaction, carrying its purpose, its scope, and its timestamp, never a value set on a request: there is no route on this door that records one, which is the mechanical reason the rows requiring one are typed and refused rather than sold.
What that means for your own use of your own data is a question for your counsel. This document is written to be forwarded to them rather than to answer it.
Standing of this document
No row on apis.credit is callable today; every SKU is stamped ROADMAP and the posted prices are DRAFT until the owner ratifies them. This restriction is published in advance of the first call rather than after it, and it binds every call from the first one. Statutory references: 15 U.S.C. 1681a(d), 15 U.S.C. 1681b, 12 CFR 1002.2(f).
Who publishes this document
apis.credit is published by Do Industries, which operates the apis.finance family and answers keys@apis.finance. Its registered form and jurisdiction of organization are not posted here yet: they are owner-ratified and publish in this document and in the door's footer before the first callable row. A door that states its standing may not state one it cannot evidence, and an operative term is worth less when nobody is named behind it, so the gap is printed rather than filled with a claim.