learn

How signed records work.

Guides for developers and platform teams building verification into API, MCP, agent, gateway, payment, and provisioning workflows.

When automated systems cross boundaries, logs are useful but not portable. These guides explain how signed records work, how policy discovery fits in, and how payment and provisioning context can be reviewed later.

start here

Why logs are not enough

Verifiable Interaction Records

What a signed interaction record contains, how offline verification works, and why server logs are not portable signed records. Includes the JWS payload structure and Ed25519 verification flow.

Interaction RecordsOffline VerificationPortable Records

2 min readRead →

more guides

Machine-readable terms for AI

Policy, Consent and Attribution

How publishers declare what agents may do with their content (AIPREF, peac.txt) and how agents prove they followed those terms. The gap between robots.txt and what AI actually needs.

AIPREFPolicy DiscoveryContent Terms

2 min readRead →

Payment challenges and signed settlement records

HTTP 402 and Payment Records

How HTTP 402 Payment Required works for machine-to-machine interactions. The request, challenge, payment, and record cycle, x402 protocol headers, and how payment records fit into the verification stack.

HTTP 402Payment RecordsSettlement Records

2 min readRead →

The economic layer for AI agents

Agentic Commerce

What happens when machines need to buy API calls, pay for content access, or settle charges with other agents. Covers policy discovery, pricing headers, payment rails, and signed records.

Machine PaymentsAPI MonetizationAgent Workflows

2 min readRead →