Pricing

Contract-change authorization for AI agents

Analyze for free. Pay for private authorization and enforcement.

1,000 requests per key per month. A keyed caller is limited to 100 requests per minute. A keyless call on the agent bucket, including POST /api/v1/preflight, is limited to 60 per minute (x-ratelimit-limit: 60). Hosted verification may be rate-limited. Offline verification is unlimited and always free.

Public beta

During the public beta every organization gets Team features at $0 with a self-serve key, public and private repositories alike, no separate Team key to request, and each key allows 1,000 requests a month: after that, /preflight authorize returns BETA_LIMIT_REACHED while its analysis keeps working; other API routes return 429. There are no subscription or overage charges during beta.

No payment method is required. There is no automatic conversion. We will give at least 30 days’ notice before paid plans begin. After beta, you may remain on Free or explicitly subscribe to Team.

When the beta limit is reached the state is named BETA_LIMIT_REACHED, and a manual raise can be requested.

Launch pricing after beta

Free — $0

Analyze contract changes, authorize public ones, and verify every receipt.

Boundary: After the beta, the planned Free boundary is a provider-verifiable public repository. Authorization cases: 1,000 per month. Verification: always free.

Get a self-serve key.

breaking-change detection · change intent · confidence scoring · auth scheme diff · semver suggestion · API design lint · changelog · documentation coverage · lifecycle labels · deprecation tracking · CODEOWNERS suggestion · migration assessment · consumer-aware risk · CLI · web · REST · MCP (preflight_change_set, verify_receipt, get_decision_details)

signed analysis receipt · offline verification

Team — $149 per month, free during beta

Authorize and enforce private contract changes at supported boundaries.

Boundary: private production. Authorization cases: 10,000 per month. Overage: $15 per 1,000, prorated.

The overage rate is a planned launch rate, subject to beta validation.

managed contract-change enforcement

required merge gate · freeze windows · breaking budgets · approval matrix · signed grants · execution evidence

Enterprise, from $1,500 per month

Enforce organization-wide contract-change policy across teams and repositories. What that tier covers, in detail: Enterprise.

Boundary: private, bespoke. Authorization cases: volume commitment. Overage: discounted.

multi-repository and cross-service controls · organization registry · consumer-aware risk scoring · durable compliance ledger (the ledger has no export; the cross-domain evidence bundle is not yet a public gate) · custom retention, not yet a public gate · SLA and procurement · OEM and embedded use

No seats. No per-repository fee. No agent tax. Users, agents and repositories are unlimited on every plan.

What counts as an authorization case

An authorization case is one supported contract change evaluated to a conclusive authorization verdict: ALLOW, WARN, REQUIRE_APPROVAL or BLOCK. Each case counts once, regardless of later verdict transitions. Technical retries carrying the same idempotency key do not count again.

not billed: retry · cache hit · verification · read-only · analysis-only · unsupported artifact or operation type · UNKNOWN · timeout · service failure

What free analysis returns, in its own words

An analysis-only response says so in its signed envelope. It is not permission, regardless of plan, and it cannot be used as a grant.

analysis_outcome     : BREAKS_DETECTED
may_execute          : false
authorization_effect : NONE

The same envelope is published and verifiable on verify. The artifact is a signed analysis receipt, not a grant: it is verifiable offline, and it authorizes nothing. The analysis endpoints also return their own limits inline: a does_not_prove list naming what that particular answer does not establish. It ships on six analysis surfaces today, the free diff among them.

When a hard limit is reached

What happens depends on the state you are in. Only two of these stop authorization, and none of them stops the checks. The authorization-case counter is a label, and it is not the live 1,000-request cap.

state	what happens
After the beta, planned: Free, 1,000 authorization cases used	No new grant.
Beta, 1,000 requests in the month used	Authorize returns 429 `BETA_LIMIT_REACHED`. Analyze continues, and a manual raise can be requested.
After the beta, planned: Team on a paid plan, 10,000 authorization cases used	Overage begins and authorization continues. This is the one state in which passing the included allowance does not stop a grant being issued.
Any state	Analysis and verification continue. Reading a contract and checking a receipt never depend on the allowance.

There is never a fail-open. An exhausted allowance removes the permission, not the checks.

Terms

One Free or Team subscription covers one CodeRifts organization. Multi-tenant, resale and embedded use require Enterprise. Prices are in USD and exclude applicable taxes. Usage is calculated monthly. Automatic overage requires an active payment method.

Get an API key Verify a receipt The claim table