economy

the tova token

The TOVA token is the settlement asset for the credit system. Credits are purchased with TOVA, and every token used for a credit purchase is burned on-chain — tying token sink activity directly to paid network usage.

credit purchase flow

user signs a credit purchase transaction with the TOVA token
tokens used for the purchase are permanently burned from circulating supply
credits are issued to the user account in the off-chain ledger
credits are consumed through inference usage at the API gateway

burn verification

Every credit purchase produces a verifiable burn transaction and a matching credit issuance record. The on-chain burn and the off-chain credit issuance can be cross-referenced from the dashboard.

{
  "purchase_id": "cp_123",
  "wallet": "0x...",
  "tova_spent": "12500",
  "credits_issued": "100.00",
  "burn_tx": "0x..."
}

dashboard metrics

total tokens burned
tokens burned in the last 24 hours
credits issued
credits consumed
inference requests served
average credits per request
burn distribution by usage category

usage vs cumulative tokens burned● modeled projection

Modeled projection of the burn-vs-usage relationship. Not measured production data.

why this design

Most utility tokens lack a direct sink. The TOVA token supply decreases when users purchase credits, tying token burn activity directly to paid network usage rather than promotional events. Burns are how credits come into existence in the first place.

info

Wallet authentication (used for purchasing credits and signing burn transactions) is separate from API authentication (used to make inference requests). API keys can be created, rotated, and revoked from the dashboard without touching the wallet.

observability

The dashboard and metrics surface expose the operational state of the network:

request latency and provider latency
time to first token and tokens per second
provider error rates and fallback rate
average cost per request
credits consumed and tokens burned

security

API keys can be created, rotated, and revoked from the dashboard
provider keys are never exposed to users — they live inside the gateway
wallet authentication is independent of API authentication
rate limits help prevent credit draining and abuse
request logging supports metadata-only or privacy-conscious modes

roadmap

phase 1 — unified API

OpenAI-compatible endpoint
wallet login and credit purchases
API key dashboard
basic usage tracking

phase 2 — smart routing

cost and latency routing policies
fallback provider selection
provider health monitoring
model aliasing and route metadata

phase 3 — network expansion

more provider integrations
permissioned provider onboarding
capacity marketplace
regional routing and SLA tiers

phase 4 — agent execution layer

long-running agent jobs
budget controls and tool execution credits
task-level routing
workflow usage tracking

← previous

unified credits

autonomous agents