Save a completed check. Reuse it where accepted.
A portable proof records the check, subject, status, scope, and expiry when one applies. Each connected product decides whether the proof meets its own rule.
What a proof covers
The result, scope, and current status in one record.
Record who or what was checked, the accepted result, what it covers, and whether it is still current. Source data remains subject to the original flow and visibility settings.
- IdentityPerson, org, social, agent
- OwnershipWallets, domains, accounts
- PermissionLimits, spend, expiry
- StatusCurrent, expired, revoked
NEUS vs a one-off check
A one-off result usually stays inside the service that ran it. A portable proof gives compatible integrations a stable reference they can check again.
Read the NEUS standard specification
| Dimension | One-off check | NEUS portable proof |
|---|---|---|
| Reuse | Usually stays inside the product that ran it | Can be checked by another integration that accepts it |
| Audit trail | Depends on the source system | Preserves the check result and proof metadata |
| Control | Managed inside the source product | Profile owners control supported public visibility |
| Expiry and revocation | Varies by provider and integration | Connected systems can check current status and expiry |
Where teams use it
Gates that need a firm yes or no — without starting from zero.
Sign-up and access
Skip repeat verification when the next gate accepts the same check.
Marketplaces
Buyer, seller, and membership decisions that stay checkable.
Agent permissions
Explicit, checkable, and revocable limits before action.
Payouts and partners
A decision record for handoffs without the full source file.
Proof layer FAQ
How portable proofs work and where they fit.
Ready to build?
Try the demo or read the developer docs.