Available
Trust Decisions
Get an allow, challenge, or deny verdict and wire it into your signup handler.
See the workflowVerify your first actionThree workflows for screening costly actions, controlling paid access, and recognizing enrolled agents.
Available
Get an allow, challenge, or deny verdict and wire it into your signup handler.
See the workflowVerify your first actionAvailable
Get a price quote and follow the purchase through hosted checkout and seller-controlled delivery.
See the workflowTry the paid access integrationAvailable
Resolve a site-specific subject for an enrolled agent. Principal details require a recipient grant.
See the workflowExplore Agent AttributionScreen costly actions before granting value.
Your app receives a signup, trial, or other costly request.
Send the action and context to POST /v1/verify.
Read one verdict: allow, challenge, or deny.
Your app grants value, requires step-up, or stops the action.
When the outcome is known, report it on the stored eventId.
For a free trial, check the request before issuing credits. Hold the grant during step-up or if verification is unavailable.
Use it for Signup abuse, trial and credit farming, costly account changes, and API-key issuance.
Verify your first actionSell controlled access to API resources.
The buyer requests fixed terms for a seller-configured resource.
The buyer accepts before expiry, within its spending ceiling.
The payer completes checkout. The seller checks local permission and reserves execution after confirmed capture.
Your backend serves the resource within the granted reservation.
The seller records the execution result and units used.
For a paid dataset lookup, use POST /v1/charge to manage the purchase. Release the lookup only when the seller has a fresh reservation for that operation.
Use it for Fixed-price API calls, bounded dataset access, and prepaid compute with enforced deadlines.
Try the paid access integrationRecognize enrolled agents with fresh signed proof.
Start with an exact site origin and a server-selected session credential or agent proof.
Attach a fresh proof from an enrolled agent or supply a site session.
Resolve checks the enrolled key and the signature for this recipient.
An enrolled network agent can match as verified_agent_account. Principal details require a current grant for the recipient and purpose.
An enrolled assistant can sign one proof for Site A and another for Site B. Both sites can recognize the agent and receive distinct subjects.
Use it for Cross-site recognition with fresh proof, site session continuity, and authorized principal attribution.
Explore Agent AttributionChoose a product to see its endpoint and setup.
POST /v1/verifyA server-side API key with verify:write. Add feedback:write to report outcomes.
Verify your first actionYour app holds the action when a verdict is unavailable, withholds paid resources without a valid reservation, and applies its own authorization policy to attribution evidence.
The four checkpoints can share one server-side record: resolve the actor, decide the action, confirm payment, then execute. See the composed transaction and what is still manual today.