Documentation

Introduction

Stop fake signups and free trial abuse before credits burn. Screen costly actions, sell paid API access, and recognize previously enrolled agents across participating websites.

On this page

Choose a capability

Trust Decisions: verify, feedback, challenge. Use it to allow, challenge, or deny signup, trial, API-key issuance, and other costly actions before granting value. Start with the Trust Decisions quickstart.

Agent Paid Access: quote fixed-price API calls, bounded dataset access, or prepaid compute seconds, then manage payment and seller fulfillment. Start with the Agent Paid Access guide.

Agent Identity Resolution. Recognize the same enrolled AI agent across participating websites. Each site receives its own scoped identity, and personal details such as email are disclosed only to recipients the account holder has authorized.

Agent Attribution is the API for this workflow. A person signs in once with an approved identity provider and binds an agent signing key. Each recipient resolves fresh proof independently and receives its own scoped subject. When disclosure is enabled, a recipient grant controls access to verification of the enrolled account, including organization-managed accounts. Start with the Agent Attribution quickstart.

When to use each

Trust Decisions is a security gate: it answers "should this action proceed?" before your app issues credits, quota, or access. A verify verdict is not proof of payment.

Agent Paid Access is a sales lifecycle: it answers "has this agent paid for this resource?" through quote, acceptance, authorization, and usage reporting. Completing a security challenge does not itself authorize paid delivery.

Require a non-degraded allow before granting value through Trust Decisions. For a paid resource, require confirmed capture, local permission, and a fresh execution reservation. Use Attribution evidence as context for your own authorization policy.

Contract source

OpenAPI 3.1 is the source of truth.

The HTTP API is defined in the OpenAPI 3.1 contract. These docs, SDKs, and examples follow that machine-readable specification.

Operational contract

Trust and ops pages live next to the API docs:

TopicWhere
Authentication and API keysAuthentication
Failure behaviorOn error, challenge
Latency targetsPerformance
Service healthStatus
CompanyAbout · Contact
Privacy and retentionPrivacy
Terms and meteringTerms