Skip to content

Pricing and payments

Prices: the public catalog at https://aetelier.xyz/api/payments/catalog, no key needed · Top-ups: USDC over x402, not open yet

Aetelier meters work in two kinds of prepaid units: data units and compute units. Every rate and bundle price comes from one public catalog, so this page quotes none of them. Read the catalog, price a run, then start it.

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

Prerequisites: curl and jq.

What you pay for

Module Action Units When Catalog field
Collectors Remote collector, per day data Once per UTC day action_rates.byo_collector_day_data
Collectors Platform collector, per day (selected accounts) data, plus a compute add-on Once per UTC day action_rates.byo_collector_day_data + action_rates.managed_collector_day_compute
Convection Hawkes fit compute Only when it converges action_rates.hawkes_fit_compute
Convection Swarm, per member for every round in its round limit compute Only when it converges action_rates.swarm_round_compute
Provenance (Data Governance) Catalog, completeness and scorecard reads none Never —
Clarion Attestation on Solana devnet none Never —
Backtracing (tracing) New trace compute (coming) Coming not in the catalog yet
  • Collectors. An hourly sweep charges each running collector once per UTC day, so a part day costs a full day. A collector stopped before the sweep sees it draws nothing. Redeploying mints a new collector, which is charged again that day.
  • Fits. The balance is checked against the price before the fit starts, and the fit is charged only when it converges. A fit that fails validation, times out or does not converge draws nothing.
  • Swarms. The price is swarm_round_compute × members × the round limit, fixed when the swarm is admitted. A swarm always runs its full round limit and is charged once, when it converges. An aborted swarm, or one that ends above its tolerance, draws nothing.
  • Traces. Tracing is open to selected accounts and draws no units today. Each new trace will draw compute units once metered access ships; reading results stays free.

Price a run

The catalog returns plain JSON, so any client can price a run before starting it.

A remote collector for seven days, in data units:

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

A swarm with 2 members, the run wizard's minimum, and 2,000 rounds, its default and its ceiling, in compute units:

curl -s https://aetelier.xyz/api/payments/catalog \
  | jq '.action_rates.swarm_round_compute * 2 * 2000'

A Hawkes fit at the list rate, in USDC:

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

For a fit, fit_pricing returns the same price over MCP.

The catalog

GET https://aetelier.xyz/api/payments/catalog needs no key and no account.

Field Holds
tokens_per_usd The list rate, in units per USDC
action_rates.byo_collector_day_data Data units per collector per UTC day, remote and platform alike
action_rates.managed_collector_day_compute Compute units added per platform collector per UTC day
action_rates.hawkes_fit_compute Compute units per converged Hawkes fit
action_rates.swarm_round_compute Compute units per swarm member per round
bundles[] One entry per bundle: sku, kind, units, price_atomic, price_usdc, discount_pct
signup_grant The data and compute units a verified new account starts with; total sums every kind
  • price_atomic is the price in USDC's smallest unit (6 decimals); price_usdc is the same price as a decimal string.
  • The reply also carries plans and packs. They are legacy fields, and nothing in them is for sale.
  • free_caps holds the collector and fit caps of an account with units, and floor_caps the lower caps on the floor. Selected accounts have higher caps.
  • bundles also lists networking bundles, and signup_grant a networking amount. Nothing draws networking units.

Bundles

Data and compute bundles come in four sizes each. List them:

curl -s https://aetelier.xyz/api/payments/catalog \
  | jq '[.bundles[] | select(.kind != "networking") | {sku, units, price_usdc}]'
  • Data bundles pay for collector-days.
  • Compute bundles pay for fits, swarms and the platform collector add-on.
  • Today the larger bundles are priced below the list rate, as discount_pct shows. Every bundle will be priced at the list rate, with no volume discount.
  • Bundles cannot be bought yet; see Top-ups over x402.

The signup grant

A verified new account starts with the units in signup_grant. The grant is credited once, the first time the account reads its entitlements (GET /api/payments/entitlements) after its email is verified, for example when the webapp loads. The balance checks behind a deploy, fit or swarm do not credit it. Google and GitHub sign-ups count as verified. Signup credits may expire or be adjusted (Terms of Service §4).

What is free

  • Data Governance reads: catalog, completeness and scorecards.
  • Clarion attestations on Solana devnet.
  • Reading the catalog and the top-up status.
  • On the floor, the oldest remote collectors up to its collector cap.
  • A fit or swarm that does not converge, and any action refused with 402.

When the balance is short

A short balance answers 402, almost always before any work starts, and nothing is charged. A fit whose balance drops while it runs also answers 402 and is not charged.

Code Means
INSUFFICIENT_DATA_TOKENS Not enough data units to deploy a collector
INSUFFICIENT_COMPUTE_TOKENS Not enough compute units for a platform collector
none, this fit costs … or this run costs … Not enough compute units for a fit or a swarm

Other 402 codes are not balance errors. TIER_TOO_LOW, RECONCILE_REQUIRES_PRO, SSE_REQUIRES_PRO and TRACER_REQUIRES_PRO mark features open to selected accounts, and adding units does not clear them. CONCURRENT_CAP_REACHED and a fit's concurrent-fit cap reached mean a cap is in use; the collector cap is lower on the floor.

Every string and its fix: Units and the 402 error and the error-code index.

Top-ups over x402 (coming)

Top-ups are not open yet. They open first on Solana devnet, for listed testers only; mainnet comes later. Check the live state, no key needed:

curl -s https://aetelier.xyz/payments/topup/status
Reply Status
"status": "disabled" OPENS SOON
"status": "operational" with a devnet network OPEN · DEVNET
"status": "degraded" DELAYED
no answer UNAVAILABLE
  • Top-ups use x402 v2, the open payment protocol that uses HTTP's 402 Payment Required status to request and settle a payment. You pay in USDC on Solana from your own wallet.
  • Coinbase Developer Platform is the facilitator: it verifies and settles each payment and pays the Solana network fee, so the paying wallet needs USDC only.
  • A top-up is two HTTP calls. Prepare answers 402 with the price in PAYMENT-REQUIRED; submit carries the signed payment in PAYMENT-SIGNATURE.
  • Each payment is credited once, keyed to its on-chain signature, with a receipt fetched by memo.
  • Aetelier adds the prepare step before the 402, so a stock x402 client will not work unchanged.

The full flow, its error codes and receipts: Top-ups over x402 and I paid but my units are not credited.

Terms

  • Units are prepaid, non-transferable service credits. They are not cryptocurrency, securities or stored value, and have no monetary value outside the platform.
  • Bundle purchases are final, except where the law requires a refund.
  • Aetelier never receives or stores wallet keys.

The full policy: Terms of Service §4–§6.