Developer Billing Rules
- All projects maintain ANM-denominated balances.
- Budget caps are enforced per request and per async job.
- Escrow reserves budget before provider execution starts.
- Usage rows include charge, provider, and settlement identifiers.
ANM-Native Billing
Compute Pricing in ANM
Developers pay in ANM. Jobs reserve ANM in escrow before execution. Settlements distribute ANM to providers and treasury with transparent economics.
| Workload | Unit | Base Price | Provider Share | Treasury Share |
|---|---|---|---|---|
| Chat Inference | 1K input tokens | 0.72 ANM | 82% | 18% |
| Chat Output | 1K output tokens | 1.08 ANM | 84% | 16% |
| Embeddings | 1K input tokens | 0.22 ANM | 80% | 20% |
| Batch Compute | GPU-minute | 1.95 ANM | 86% | 14% |
| Agent Tasks | task-step | 0.34 ANM | 79% | 21% |
Provider Earnings Rules
- Rewards accrue from successful verified completions.
- Higher benchmark class unlocks premium queues.
- Reputation and stake influence routing confidence.
- Disputes/slashing can reduce rewards for faulty execution.
Network Economics
- Treasury can subsidize strategic workloads with ANM credits.
- Governance can tune provider/treasury split by model class.
- Contract jobs can lock dedicated ANM budgets in escrow.
- Economics are transparent and auditable by design.