Pricing and access

Start in the playground. Scale through gateway keys.

Test a model, connect wallet-backed access, then move production traffic to the compatible API.

Access lanes

A clear progression from demo to production.

Jatevo

Playground

Live model testing

Try prompts against hosted models before creating an application key.

Builder

$JTVO-backed API key

Connect a wallet, create a scoped gateway key, and track usage from the dashboard.

Network

Reserved capacity

Route heavier workloads through private pools, custom quotas, or dedicated lanes.

Gateway surface

One public API surface for model traffic, usage tracking, and quota enforcement.

Base
/v1
Keys
sk-clb
Quota
$JTVO

Realtime chat

/v1/chat/completions

Send chat workloads through Jatevo with the standard messages request shape.

Responses API

/v1/responses

Run modern agent workloads through the same pooled compute access layer.

Model discovery

/v1/models

List models available to your key without exposing internal pool details.

Quota mechanics

Wallet-backed access needs two limits, not one.

Request quota protects the pool. Dollar credits protect the business. Jatevo can let teams resell or route heavier usage without letting a cheap request count become unlimited expensive model spend.

Access logic

Dual-limit gateway flow

whichever runs out first

Wallet

Hold JTVO

Token balance proves access and backs spend.

Value

USD snapshot

Oracle or admin rate turns holdings into budget.

Credit

Dollar budget

Daily spend ceiling for actual model cost.

Request limit

Remaining API calls

Stops spam, keeps shared routes fair, and gives simple dashboard limits.

Credit limit

Remaining dollar budget

Stops expensive resale loops and charges by model usage, not only request count.

API key

Incoming request

The sk-clb key asks for a model route.

Gate

Both limits available?

Request count remains
Projected cost fits budget
Model is allowed for this key

Allow

Route request and deduct actual cost plus Jatevo margin.

Block

Return quota error or ask user to top up / hold more JTVO.

Dashboard metrics

The dashboard should show both counters side by side so users understand whether they ran out of calls or ran out of compute value.

Limit A

API requests

0 / 11 daily

Controls abuse, concurrency, and fair access to shared pools.

Limit B

Dollar credits

$0.00 / $11.00 daily

Controls economic exposure, reseller use, and model cost drift.

Decision

First empty limit wins

Both must pass

A request is accepted only while request quota and dollar budget remain.

logic diagram

gateway rule
Rendering diagram...

Bring real model capacity into your next AI product.

Test the model lane in the playground, then ship against one compatible Jatevo gateway.