Documentation

How to use Apidentity, in plain language — added to as questions come up, not written once and left. If something you needed isn’t here yet, it will be.

• What Apidentity is A certificate a company earns once and shows to everyone.
• One certificate, not a new report each time The usual model has each counterparty commission its own check. This flips who does the verifying.
• How the answer is reached Five sources, cross-compared — never two readings of one counted as two.
• KYB and KYC, and where the line sits here Two different questions -- is this company real, is this person real -- and Apidentity answers mostly the first one.
• Checking a certificate Free, and it always will be. A certificate nobody can check is a private note.
• Getting your own certificate By invitation, not by signing up — on purpose.
• Simulated identity, on a demo certificate What it means when a certificate says the identity step was not real.
• Understanding your grade Two axes, cross-referenced into one letter — never a single score standing in for both.
• What screening covers The restricted-party and destination-control sources behind the trade axis — and what sits outside them.
• Sharing your grade and dossier Three tiers. You decide who sees the last two, and every read is visible to you.
• Managing what you've shared A standing door, not a one-time decision — reviewed and narrowed whenever you like.
• API reference: sharing and consent For a developer wiring up disclosure requests, grade reads, and permission management directly against the API.
• Adding the badge to your site A link, not a picture — so a copied badge can't lie on somebody else's site.
• Keeping your certificate current Re-checked, not issued and forgotten — and never revoked without a person deciding.
• Requesting erasure Removes the name from the record. The record itself has to survive.