agentbox documentation

Choose an interface

• Repository CLI quickstart — the implemented local and remote lifecycle, while public writes remain explicitly gated.
• CLI reference — checkout command usage, retry artifacts, price ceiling, capability files, and JSON output.
• HTTP API — human-readable context for the endpoints, required headers, limits, and structured errors.
• OpenAPI path — /openapi.json is the canonical machine contract. Stop and report any prose/schema mismatch; public paid creation remains separately gated.

Availability is gated

These pages define the durable production interface; they do not announce that public paid writes are live. The Worker, OpenAPI document, repository client, and monthly settlement cap must land together before these docs can be deployed as production truth. Creation and upload can be disabled independently of existing authorized reads and deletes.

Trust boundary

The repository CLI encrypts plaintext locally for one age-compatible X25519 recipient. agentbox receives only opaque ciphertext, its byte count, its SHA-256 digest, and payment/control metadata. The service never receives the recipient identity or any decryption key.

Write, read, and delete access use independent bearer capabilities. Anyone holding one can exercise its scoped operation until the box expires, so transfer and store capability files as secrets.

Read the security and recovery model.

Policy and support

The published site footer links the release-approved Terms, Privacy, Retention, and Deletion, Acceptable Use, and Abuse and Legal Notices before paid creation is enabled. Read the exact published version and policy digest; this security summary does not replace those policies. For support, send only a non-secret request ID, UTC timestamp, and stable error code to [email protected].

Fixed service limits

Property	Production launch contract
Network	Base Mainnet (eip155:8453)
Asset	Canonical Base USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)
Price	10000 atomic USDC ($0.01) per box
Ciphertext	One upload, 1 byte to 10 MiB
Lifetime	24 hours from successful creation; no renewal
Capacity	500 live boxes
Support	[email protected]

The production payee must be published and pinned by the companion Base Mainnet client release before payment is enabled. Do not trust an unexpected payTo value merely because it appears in a payment challenge.