Commercial / analytics
The default on every rail. Risk analytics, portfolio and counterparty analysis, reputation, fraud and sanctions screening. Not a consumer report.
Consumer report
For credit decisions about individuals. Available only to certified consumer-credit customers, and carries the processes a consumer report requires.
Commercial / analytics delivery
Commercial delivery is what you get by default, whichever way you call the API:
A commercial response is not a consumer report and is not to be used to determine an individual’s eligibility for credit, insurance, employment or housing. Use it for what it is: an analytical view of an address’s on-chain history. Typical uses are risk analytics, portfolio and treasury analysis, counterparty and protocol due diligence, agent reputation, fraud and sybil detection, and sanctions screening.
Anonymous rails (x402, MPP, MCP, the Snap) always receive commercial delivery: they carry no certification, so the consumer-mode fields are never included.
Consumer-report delivery
Lending to an individual on the strength of their score, or otherwise using it to decide whether an individual gets credit, is consumer-report delivery. It is available only on API keys whose owner has been vetted by Cred Protocol and has accepted the consumer-use certification on that key. Consumer-report responses add what a consumer-credit customer needs:- Ranked key factors — up to four factors, ranked by how much each lowered this address’s score, with reason codes, the score range and the date, for adverse-action notices
- Inquiry record — every request about the address is recorded and can be disclosed to the address’s owner
- Obsolescence window — negative items older than seven years are excluded from the score
- Dispute process — the owner of an address can dispute how their activity has been interpreted, with a defined reinvestigation period
Becoming certified
- Contact us. Email team@credprotocol.com with your company details and how you intend to use scores in credit decisions. We review your legal entity, lending licence or exemption, product and borrower relationship, permissible purpose, data handling and adverse-action process, and ask for a named compliance contact.
- We approve your account. Once the review is complete, we enable consumer-credit certification on your console account.
- Accept the certification on a key. In the console, create an API key (or edit one) with the Consumer credit purpose and accept the consumer-use certification. You certify, among other things, that you will request consumer reports only for a permissible purpose, will not resell them, will send adverse-action notices citing the key factors, and will not use them for employment, insurance or housing decisions. Keys with any other purpose are unaffected.
Stating the purpose of each request
Every consumer-mode request must say why it is being made, in theX-Cred-Purpose header:
If you request reports on behalf of a lender, name it in
X-Cred-End-User (up to 200 characters). Both values are recorded with the inquiry and shown to the owner of the address when they review who has accessed their file.
When a certification lapses
If your certification is withdrawn, or we publish a new version of the certification that you have not yet accepted, your consumer-credit keys keep working but are served in commercial mode: responses carrydelivery.mode: "commercial" and no key factors. Accept the current certification on the key in the console to restore consumer-report delivery.
How a response says which mode it is in
Score and report responses carry adelivery block, and the same mode is set in the X-Cred-Delivery-Mode response header.
Subject type: is the address an individual’s wallet?
Single-address scores and full and single-chain reports carrysubject_type (on the report, under report.account), which says what kind of subject the address is:
A multisig, a token or another contract is not an individual, so it cannot be the subject of a consumer report. In consumer-report delivery such a response omits the key factors, and its
delivery block carries a subject_warning:
eoa, smart_wallet and unknown are delivered normally. In commercial delivery subject_type is informational and no warning is added.
What this means for the use-case guides
The use-case guides show how to turn a score into product rules — collateral tiers, pool access, personalised experiences. Applied to protocols, treasuries, agents and other non-individual subjects, those patterns are commercial delivery. Applied to decide whether an individual gets credit, they need consumer-report delivery and a certified key.Disputes
The owner of an address can dispute their own file. Sign in with the address’s wallet on score.credprotocol.com or in the Cred MetaMask Snap (or callPOST /wallet/disputes with the wallet token from POST /wallet/verify) and describe what is wrong: an event that is inaccurate, a wallet that is not yours, the wrong kind of subject, or anything else, with the transaction hash if you have one and an email address for the outcome.
- Every dispute is reinvestigated within 30 days; the confirmation email gives the due date.
- While a dispute is open, the address’s score and report carry
under_dispute: true, so anyone reading them knows the file is being reviewed. - If an event turns out to be wrong, it is removed from scoring and the score is recomputed at once. The report shows how many events were removed in
credit_events.excluded_by_dispute. - The outcome (corrected, reviewed without change, or rejected) is emailed with an explanation.
GET /wallet/disputeslists your disputes and their status.