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. Rates below are indicative — final rates are shown at key creation.
| Workload | Unit | Indicative Price | Provider Share | Treasury Share |
|---|---|---|---|---|
| Chat Input (aicf-chat-1) | 1K input tokens | 0.012 ANM | 85% | 15% |
| Chat Output (aicf-chat-1) | 1K output tokens | 0.018 ANM | 85% | 15% |
| Chat Request Base Fee | request | 0.00015 ANM | 85% | 15% |
| Embeddings Input (aicf-embed-1) | 1K input tokens | 0.008 ANM | 82% | 18% |
| Embedding Vectors (aicf-embed-1) | vector | 0.00005 ANM | 82% | 18% |
| Embeddings Request Base Fee | request | 0.0001 ANM | 82% | 18% |
Indicative — final rates are shown at key creation. Values above are read from the live AICF model registry
(GET https://aicf.animica.org/api/models) and may change with governance updates.
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.