Plans and quota

In the current beta, access is quota-gated. Issuance may be payment-gated or entitlement-gated, but the preferred onboarding path is entitlement-based access through operator-created accounts, linked API keys, and account tokens.

For approved beta users, access currently starts on the built-in free tier at no charge. The free tier is meant for real experimentation, not just a quick demo.

If your pilot needs more headroom, operators can extend quota by moving the account to a higher built-in plan or by assigning add-ons. We actively encourage testing and exploration of the protocol — if your use case exceeds the default limits, just let us know.

Free

Built in

1 identity anchor, 25 continuity, 1 lineage

Starter

Built in

3 identity anchor, 100 continuity, 5 lineage

Pro

Built in

10 identity anchor, 500 continuity, 25 lineage

* Plans and quotas are subject to change.

Current built-in add-ons

identity_anchor_2
continuity_50
lineage_5

How quota is enforced

Issuance currently remains API-key-first for the entitlement path.
Per-key quota is enforced for account-linked API keys.
Account-tier caps are enforced at the account level.
Active add-ons increase the effective account cap.
If quota is exhausted, issuance is blocked.

The system does not silently move you into a higher plan. If quota is exhausted, the registry returns structured upgrade guidance instead of auto-upgrading your account.

How to inspect your current quota

If you have an account token, the fastest check is:

iap-agent account usage --json

This shows your current tier, whether the account is active, and the remaining issuance counts.

When to request higher limits

Your remaining continuity quota is repeatedly dropping to zero.
You are onboarding multiple agents under one account.
Your pilot needs more issuance headroom than the current plan allows.

How to prepare a quota request

Include the expected number of agents, expected continuity volume, and whether you need a plan adjustment or a one-off add-on. That is enough for an operator to review the request.

Encouraging experimentation

IAP is in public beta because we want real-world testing. Continuity tracking only becomes meaningful when agents evolve, fork, migrate, and get stressed under real conditions.

If you are actively experimenting with identity anchors or high-frequency continuity flows, quota should not be the limiting factor. Send a brief description of your use case and expected volume, and we can adjust limits accordingly.

Access and quota changes are coordinated through the beta onboarding flow.

Open beta onboarding