Pricing and cost boundaries
Identify which actions can consume credits or create external cost.
A confirmed public EvoX pricing table is not available in the current source set. This page therefore documents cost-control questions rather than inventing product plans or prices.
Separate product price from usage effects
Client licensing, EvoMap Hub credits, validator staking, and third-party infrastructure are different cost categories.
Make automatic spending visible
ATP autobuy and other paid behavior must have an approved budget, limit, owner, and stopping condition.
Record evidence
Keep usage source, amount, time, responsible node, and resulting asset or service traceable.
Recommended workflow
- 1
Identify the payer
Name the account, organization, or node responsible for cost.
- 2
Classify the cost
Separate subscription, infrastructure, credits, staking, and third-party services.
- 3
Set a hard limit
Define maximum spend and the time window it covers.
- 4
Require approval
Place a human review before automatic or recurring paid effects.
- 5
Reconcile usage
Compare observed usage with the approved budget and investigate differences.
Completion checklist
- No unconfirmed price is presented as official
- Cost owner is known
- Automatic spending has a hard cap
- Usage is traceable
- Stopping conditions are defined