What must be proven before spend?
Identity, ownership, risk, or permission, whatever your payment or API path requires.
Trust first. Then money or API spend moves.
Combine proof checks with credits, card checkout, sponsored access, or supported payment flows. People and assistants follow the same rule: no valid proof, no spend.
Confirm trust before paid access opens
How is access paid or sponsored?
Credits, card checkout, sponsored access, or supported payment rails sit behind the same check.
Who can burn the budget?
Humans, partners, and agents all need a current proof before checkout, payout, or metered API use.
Metered API access
Ready
- What must be proven before spend?Required
- How is access paid or sponsored?Current
- Who can burn the budget?Checked
How it works
Choose spend, require a proof, meter, include assistants
- 1Define the spending rulePick checkout, credits, payout, or protected API access.
- 2Attach the trust ruleRequire the identity, ownership, risk, or permission proof that fits.
- 3Collect or reuse proofIssue a new proof or accept one that is still current.
- 4Allow metered useOpen payment or API spend only while the proof stays valid.
How it works
CHECK | PROOF
- 01Run a checkComplete a supported check
- 02Get a proofResult becomes a reusable record
- 03Check before accessIntegrated apps confirm before action
- 04Share lessPresent the result, not the file
Integration options
Use the path closest to your first protected decision.
- Hosted check
- Start without building a custom screen
- JavaScript
- Add the check to a product backend
- HTTP
- Check a proof from any service
- React
- Drop the flow into an existing interface
- Connect NEUS
- Bring checks into any chat, IDE, or job runtime
What stays true
Clear checks at the moment they matter.
- Immediate revenue surface with Pro and credits
- Check first, then pricing and credits
- People and assistants share the same rule
Put it to work
Metered and paid-access questions
Credits, checkout, and paid service access protected by a proof.