Skip to content

Feature access

Some features are open only to selected accounts today. Nothing can be bought to open them. Every account can run remote collectors, model fits and Convection swarms, paid for in prepaid units, and read governance data. Metered access by units is coming and replaces most of these gates.

Open to every account

Feature Draws Notes
Remote (bring-your-own) collectors data units, once per collector per UTC day You run aetelier-agent — see My collector deployed but no data is landing
Model fits compute units, charged only when the fit converges Read the price first with fit_pricing
Convection swarms compute units, charged only when the swarm converges The price is fixed when the swarm is admitted — see How metering works
Governance reads no units Catalog, completeness and scorecards, up to your account's window ceiling
Collector state by polling no units collector_status and collector_health

Every rate is in the public catalog, under action_rates, at https://aetelier.xyz/api/payments/catalog (no key needed).

Open to selected accounts

Feature Code (HTTP) Do this instead
Platform (managed) collectors TIER_TOO_LOW (402) Deploy a remote collector
Platform collectors on Solana FORBIDDEN (403) Deploy a remote collector
Live reconciliation — a manifest with [collect.reconcile] enabled = true RECONCILE_REQUIRES_PRO (402) Deploy without that section enabled
Live collector-state stream — GET /api/collectors/state/stream SSE_REQUIRES_PRO (402) Poll collector_status or collector_health
Tracing — every /api/tracer/ route, reads included TRACER_REQUIRES_PRO (402) No fallback yet; report the code
Longer governance windows — window_secs VALIDATION_ERROR (400) Retry inside the ceiling the message names
More collectors at once CONCURRENT_CAP_REACHED (402) Stop one you no longer need with stop_collector, then retry
More fits at once no code yet (402) Wait for a running fit to finish, then retry

The collector and fit caps are lower while an account holds no units — see The floor.

Exact messages

The error field starts with payment required: (402), forbidden: (403) or validation error: (400), then the text below. The server fills in the values in braces. {tier} is an internal access label, such as free.

Code Message
TIER_TOO_LOW managed agents are not included in the {tier} tier — upgrade to Base or higher, or deploy a BYO (remote) agent
FORBIDDEN [collect.grpc] preset '{preset}' is reserved for internal use and this account is not on its allowlist — presets for this account: {presets}
RECONCILE_REQUIRES_PRO live reconciliation requires the Pro tier or higher — current tier: {tier}
SSE_REQUIRES_PRO live collector-state streaming is included from the Pro plan
TRACER_REQUIRES_PRO trace configuration is included from the Pro plan
VALIDATION_ERROR window_secs must be between 1 and {max_secs} for your plan
CONCURRENT_CAP_REACHED concurrent-collector cap reached ({in_flight}/{cap}) for the {tier} tier — release a collector or upgrade
none concurrent-fit cap reached ({in_flight}/{cap}) for the {tier} tier — wait for a fit to finish or upgrade

While an account holds no units, the collector cap message reads for the free tier floor.

Nothing to buy

Some messages still name a plan or suggest an upgrade. No plan or upgrade is on sale, and nothing can be bought to open these features.

What to do

Agents

  • Branch on code. FORBIDDEN and VALIDATION_ERROR are shared codes and the fit limit has none, so also match the message text shown above.
  • The same call gets the same answer until something changes. Take the fallback in the table, or stop and report the code and message to the person you act for.
  • Do not try to top up. Top-ups are not open yet, and units open none of these features; only the collector and fit caps depend on the balance.
  • A 503 with code SERVICE_UNAVAILABLE and entitlement check unavailable on tracing or the live stream means the access check could not run. Retry with backoff.
  • MCP tools return the same code and docs_url inside a normal tool result — see MCP errors are data, not failures.

People

  • Use the fallback in the table. Remote collectors, fits, swarms and governance reads stay open on every account.
  • For questions about access, email [email protected] with the code, the time (and timezone) and what you called.
  • After your account's access changes, allow up to a minute before you retry.

What is coming

Metered access by units is coming. When it ships:

  • Platform collectors open to any account whose balance covers one day of both daily rates, which the catalog's action_rates lists as byo_collector_day_data and managed_collector_day_compute. Platform collectors on Solana stay open to selected accounts until their daily cost is measured.
  • Tracing opens to every account. Each new trace draws compute units; reads and resubmits draw none.
  • Live reconciliation opens to every account, included in the collector-day rate.
  • The live collector-state stream and governance windows open to every signed-in account, with the same window ceilings for every account.
  • The collector cap goes. Your unit balance decides how many collectors run, within the platform limits.
  • Fits get one limit on runs in flight for every account, answered with 429 instead of 402.

TIER_TOO_LOW, RECONCILE_REQUIRES_PRO, SSE_REQUIRES_PRO, TRACER_REQUIRES_PRO and CONCURRENT_CAP_REACHED then stop being sent. A short balance still answers INSUFFICIENT_DATA_TOKENS or INSUFFICIENT_COMPUTE_TOKENS — see The 402 balance errors.

Units are prepaid, non-transferable service credits, not money. Top-ups are not open yet: the public status at https://aetelier.xyz/payments/topup/status reads disabled, shown as OPENS SOON. Top-ups open first on Solana devnet, for listed testers only (OPEN · DEVNET); mainnet comes later. Every status word is in Top-ups over x402.