Welcome to the Arxcode documentation — built content-first with MDX.
Arxcode
ARXCODE

Payments & metering

How a build is priced, confirmed, and settled — pay-per-build in $ARX, with the cost shown up front.

ArxCode bills per build, not per seat or per month. The cost of a build is proportional to the compute it consumes, settled in $ARX on Solana.

How a build is priced

  1. Estimate. Before any build runs, ArxCode shows an estimated $ARX cost based on the scope of the work.
  2. Confirm. Nothing is spent until you approve. Set budget caps so a build stops before it exceeds a ceiling.
  3. Settle. On completion, the actual $ARX consumed is burned. You only pay for compute that was delivered.
Costs shown up front

Every product meters transparently — per build, per audit, per query, or per message — and always surfaces the estimate before you commit.

Why on-chain settlement

Settlement occurs on Solana, whose sub-second finality and sub-cent fees make per-build billing economical at the granularity of individual operations. A slower or more expensive chain couldn't support metering this fine.

ArxCodeHosted AI
Billing unitPer buildPer seat / month
CommitmentNone — pay as you goSubscription
SettlementOn-chainOff-chain
Account requiredWallet onlyEmail + card

Lowering your rate

Because the protocol applies hold-for-discount, maintaining a larger $ARX balance reduces the per-build rate across every product.

Next