Payment Model
Autonomi uses a pay-once storage model. You pay in Autonomi Network Token (ANT) when you upload data, then retrieve it later without ongoing storage charges or download fees.
Why it matters
You cannot treat uploads as fire-and-forget writes. antd, the CLI, and Direct Rust all require wallet context for paid storage operations, and they differ in where they expose cost estimation, wallet approval, and payment-mode control.
How it works
Pay once on upload
Autonomi is designed around immutable storage rather than renewable storage leases. In practice, that means the payment event happens when you upload data. There are no recurring storage fees or separate retrieval payments.
Wallet-backed writes
The tools use different wallet inputs:
antdusesAUTONOMI_WALLET_KEYfor direct-wallet uploadsantandant-coreuseSECRET_KEYor an attachedWallet
Without wallet configuration, direct-wallet write endpoints fail. External-signer preparation endpoints can collect quotes without giving antd custody of the wallet key.
The OpenAPI description and antd runtime behavior are not fully aligned for public external-signer preparation. Follow Use External Signers for Upload Payments for supported operations and known limitations before integrating this flow.
When you use the CLI or Direct Rust with ant-core, the client asks close peers for signed storage quotes, validates them, and uses them to construct the on-chain payment.
Ethereum Virtual Machine network choices
The ant CLI exposes these Ethereum Virtual Machine (EVM) network values:
arbitrum-onearbitrum-sepolialocal
The antd external-signer flow also exposes the Remote Procedure Call (RPC) URL and payment contract addresses the signer needs to submit the transaction for the selected EVM network.
Cost estimation
The antd surface exposes cost estimation explicitly:
POST /v1/data/costPOST /v1/files/cost
Those endpoints return a structured estimate with cost, file size, chunk count, estimated gas, and the payment mode that would be used.
Payment modes
The supported payment modes are:
auto
Choose Merkle batch payment for larger batches and single payments otherwise
merkle
Force Merkle batch payment
single
Force per-chunk payment
In ant-core, the Merkle batch payment threshold is 64 chunks.
Nodes verify the payment proof that arrives with each write. That includes signature checks, on-chain payment verification, and record-level validation before content is accepted into the chunk store.
Node-side storage pricing follows BASELINE + (n * n * K) / (D * D), where n is the key_count in the node's signed storage commitment, K is a fixed coefficient, and D is a fixed divisor. If no commitment is available, the node uses the non-zero baseline price. The client recomputes the expected price from the same committed key count before paying.
What happens on retrieval
Downloads do not require a separate payment step. Payments are tied to storage writes such as storing data, chunks, or files.
Practical example
Two payment patterns show up across antd and the CLI:
Estimate and upload through
antd
Upload directly with
ant
In both examples, payment happens as part of the upload flow, but the antd example exposes explicit cost-estimation endpoints while the CLI example emphasizes direct upload flags and wallet setup.
Related pages
Last updated