Skip to content

Platform limits

These are the boundaries the platform enforces today. A request that crosses one is refused with a structured error — that refusal is the rule working, not a malfunction. We document what is live; if a capability is not described in these docs, the platform does not currently provide it.

Collectors

  • One collector runs one symbol. A manifest with more than one [[workers]] entry is rejected with VALIDATION_ERROR. Run one collector per symbol you want covered.
  • Venues are fixed: spot markets on twelve CEX venues, perpetuals on Hyperliquid, and on-chain transactions for one account address on Solana. Any other venue or market type is rejected at validation. See Venue coverage and Datasets.
  • Concurrent collectors are capped per account. An account runs up to nine collectors at once, or three while it holds no units; selected accounts have higher caps. Past the cap, a deploy answers 402 with CONCURRENT_CAP_REACHED: stop a collector to deploy another.

Agents

  • Remote (BYO) agents work on every account. You run the container; the dashboard hands you the exact docker run command. A deploy needs at least one data unit, or answers 402 with INSUFFICIENT_DATA_TOKENS.
  • With no units of any kind, an account keeps three remote collectors. It can still deploy and run up to three remote collectors, unmetered. Metering then stops any platform collectors and any remote collectors beyond the oldest three. Running out never closes the account.
  • Platform (managed) agents are open to selected accounts. Elsewhere a platform deploy answers 402 with TIER_TOO_LOW; deploy a remote agent instead. A platform deploy also needs at least one compute unit (INSUFFICIENT_COMPUTE_TOKENS). On Solana, an account not on the provider's list gets 403 with FORBIDDEN first.

Fits

  • Checked before, charged on convergence. A short compute balance answers 402 before any work starts. Only a converged fit is charged; a failed, oversized or timed-out fit is not. Swarms follow the same rule.
  • A fit takes at most 1,000,000 events and runs for at most 300 seconds, by default. Past either limit the fit is refused with 400 (validation error:).
  • An account has up to nine fits in flight at once; selected accounts have higher caps. Past the cap, a fit answers 402 with concurrent-fit cap reached. A fit may wait for a free run slot before it starts.

Features open to selected accounts

Nothing can be bought to open these, and a top-up does not clear their codes. Each feature in the table answers 402 on an account where it is not open:

Feature Code
Platform (managed) collectors TIER_TOO_LOW
Live reconciliation ([collect.reconcile] with enabled = true) RECONCILE_REQUIRES_PRO
Live collector-state stream (GET /api/collectors/state/stream) SSE_REQUIRES_PRO
Tracing, every /api/tracer/ route, reads included TRACER_REQUIRES_PRO
  • Data governance reads draw no units. A live-window read spans at most one hour (window_secs up to 3600); longer windows are open to selected accounts. Past the ceiling a read answers 400 with VALIDATION_ERROR. A seven-day window for every signed-in account is coming. See the governance API.
  • Traces are capped per account: up to 50 by default. Past that, a new trace answers 429 with trace quota reached.

Units

  • Work draws prepaid units. Collectors draw data units once per UTC day for every day they run; a platform collector also draws compute units. Fits and swarms draw compute units. Every rate is in the public catalog, which needs no key:

    curl -s https://aetelier.xyz/api/payments/catalog | jq '.action_rates'
    

    action_rates carries byo_collector_day_data, managed_collector_day_compute, hawkes_fit_compute and swarm_round_compute. tokens_per_usd is the list rate, bundles lists the bundles, and signup_grant is what a verified new account starts with.

  • Units are prepaid, non-transferable service credits, not money. Bundle purchases are final except where the law requires a refund (Terms of Service §4–§6).

Top-ups

  • USDC top-ups are not open yet. The public status endpoint reads disabled, shown as OPENS SOON:

    curl -s https://aetelier.xyz/payments/topup/status
    

    Top-ups open first on Solana devnet, for listed testers only; mainnet comes later. operational with a devnet network reads OPEN · DEVNET. degraded reads DELAYED: top-ups are running slowly. No answer reads UNAVAILABLE: the status could not be read.

  • While top-ups are off, the top-up endpoints answer 503 with code topup_disabled. Once devnet opens, an account not on the tester list gets 403 with code topup_not_allowed.

  • Payments use x402 v2, in USDC on Solana only, with Coinbase Developer Platform as the facilitator that verifies and settles each payment. The facilitator pays the Solana network fee, so the paying wallet needs USDC only. Aetelier never receives or stores wallet keys.
  • Every top-up belongs to an account and needs its bearer token, such as an API key.
  • Once open, a prepared top-up must be signed and submitted within 25 seconds (410 with intent_expired otherwise), and an account holds at most five prepared top-ups awaiting submission at once (429 with too_many_open_intents).
  • A public, signed payer CLI is coming.

Support

  • Support is asynchronous — email [email protected], plus the community channels in your dashboard, under the published support policy. There is no live chat or phone line. Account, billing and payment questions are handled over email only.