Pricing and limits
Plan details, session limits, retention periods, and what happens when you hit a limit.
Plans
| Plan | Price | Sessions / month | Retention |
|---|---|---|---|
| Free | $0 | 100 | 7 days |
| Pro | $49 / month | 5,000 | 90 days |
| Business | $199 / month | 50,000 | 1 year |
All plans include the same features: hash chain verification, compliance metadata, human review tracking, and all SDK wrappers. Plans differ only in session volume and retention. Start for free and upgrade when you need more.
Session limits
What counts as a session
A session is one end-to-end agent run. Processing one invoice, handling one support ticket, generating one report. Each session can contain up to 200 events. The monthly limit counts sessions, not events. A session with 3 events and a session with 200 events both count as one session.
What happens when you hit your limit
When you reach your monthly session limit, the ingest endpoint returns HTTP 429 with the error code LIMIT_REACHED. Your agent keeps running. The SDK logs a warning and continues. The session is not recorded, but your agent code executes normally.
Existing sessions that started before you hit the limit can still receive events. The limit only blocks the creation of new sessions.
If you are regularly hitting your session limit, upgrade your plan from the billing page.
Retention
Events older than your plan's retention period are deleted automatically. Deletion happens in two stages:
- Raw payloads (stored in Cloudflare R2) are deleted first. This removes the actual LLM input and output content.
- Event metadata (timestamps, event type, hash chain) is deleted shortly after.
If an event has a retentionOverride set via compliance metadata, that override takes priority over the plan default. This lets you keep healthcare or financial data for longer than your plan would normally allow.
Once data is deleted, it cannot be recovered. If you need to preserve receipts for longer than your plan allows, export them before the retention window closes or upgrade your plan.
Event limits
Each session can hold a maximum of 200 events. This prevents unbounded event growth within a single session, which would generate disproportionate storage costs regardless of the plan.
When a session reaches 200 events, the ingest endpoint returns HTTP 429 with the error code SESSION_EVENT_LIMIT. A system error event is recorded so the receipt shows exactly where and why ingestion stopped.
If your agent workflow needs more than 200 events, split the work into multiple sessions at logical boundaries. For example, if you are processing a batch of 50 invoices, create one session per invoice instead of one session for the entire batch.