basis-m4max-01
Apple M4 Max (Metal, unified memory) · 36GB
basis-default
ollamaPrompt / 1M
88 cr
$0.0880
≈ 0.088 $BASIS
Output / 1M
352 cr
$0.3523
≈ 0.3523 $BASIS
- ctx
- 32,768
- max out
- 2,048
- concurrency
- 1
The inference layer for the agent economy
Workers publish models, prices, and capacity. Basis verifies offers, routes requests, records receipts, and settles jobs through $BASIS on Base.
Agents need inference. Workers set the market. $BASIS settles the job.
Worker offers · live market
$0.001 / credit · USDC-peggedSelf-reported offers — verification opening.
basis-m4max-01
Apple M4 Max (Metal, unified memory) · 36GB
basis-default
ollamaPrompt / 1M
88 cr
$0.0880
≈ 0.088 $BASIS
Output / 1M
352 cr
$0.3523
≈ 0.3523 $BASIS
Network status
The exact state of each path — inference, the worker market, payments, the on-chain fee route, and settlement. Read live from the same sources the API serves, and published at /api/launch-status.
Inference API
liveOpenAI-compatible. Served now through a hosted upstream; the public demo is free and metered.
Orchestrator
live · hostedThe hosted orchestrator is up and authenticates worker dispatch. It selects an eligible worker when one is online.
Worker market
storage liveSigned worker model, price, and capacity offers. Offer storage is live and durable.
Worker offers
1 publishedLive published offers right now. Run a worker to publish yours.
Payment routing
quote-onlyThe router quotes WETH, ETH, or USDC into $BASIS. Your wallet signs the swap — Basis never signs or custodies.
Fee router
configuredThe on-chain spend sink that splits spent $BASIS 10% burn / 90% worker. Deployed and wired to the credit vault.
10% burn / 90% worker route
mainnet-provenThe on-chain 10% burn / 90% worker reward split has been proven by a controlled mainnet transaction — not a continuous live feed.
Paid inference
free demoThe public API does not require credits today — it is the free metered demo. Paid $BASIS credits come online behind their own gate.
Public worker routing
onRequests route to a worker only when a real verified worker is online and eligible. Today the gateway serves through the hosted upstream.
Settlement
keeper-drivenWorker rewards batch deterministically. Settlement is operator and keeper driven, prepared off-chain first — not a continuous automatic service.
Today the public API serves a free, metered demo through a hosted upstream; it does not require $BASIS credits and does not route to contributor workers. Worker routing turns on when a real verified worker is online and eligible. The 10% burn / 90% worker reward route has been proven by a controlled mainnet transaction; it is not a continuous live feed. This is not yield and not an investment.
Try inference
Sign in, pick a model, and send a prompt straight to the network. The same request travels the same path every job does — routed, served, and recorded to a receipt. Behind the scenes it is the OpenAI-compatible API any client can call.
Initializing console…
Worker-powered inference
A model call enters the gateway and is served by compute on the network. Apps pay in $BASIS, workers earn $BASIS for the completed, verified jobs they serve, and every job is accounted to a verifiable receipt. The on-chain reward route is proven; routing public jobs to contributor workers turns on as verified workers come online.
Agents
Send model calls to an OpenAI-compatible endpoint.
Workers
Supply compute to serve those calls.
Base
Settles the accounting for every completed job.
A request enters the gateway and is routed across a coordinated network of GPU workers. The contributor worker network is being activated.
Agents
Query
Gateway
Route
Workers
Serve
Point any OpenAI client at Basis and call chat completions.
base_url = https://basis.watch/api/v1
model = basis-default
client.chat.completions.create(…)
ETH, WETH, or USDC can route into $BASIS at payment time.
$BASIS
via router
Credits
usage unit
The request path
Every request travels the same path. An app or agent calls the API, the gateway routes it, compute serves the model, tokens stream back, and a receipt records the job.
Point an OpenAI client at the Basis base URL.
The request enters the gateway and is dispatched.
A model is served and tokens stream back.
Model, tokens, worker, and pricing are hashed.
Query → Route → Stream → Receipt → Reward → Settle
Query
Route
Stream
Receipt
Reward
Settle
Workers earn $BASIS
A worker serves a job, a receipt records it, and a completed, verified job pays a $BASIS reward to the worker’s reward address. A failed or rejected job creates no payable reward, and a worker needs a valid EVM reward address to earn. The contributor worker network is being activated; this is not yield and not an investment.
GPU worker → Receipt → $BASIS reward
GPU worker
serves the job
Receipt
records the job
$BASIS reward
completed jobs
soon
Receipts & accounting
A receipt records the accounting fields of a job — model, tokens, worker, pricing, and settlement — hashed over its immutable economic core. It never records prompt or completion text. Server token counts are authoritative; duplicate jobs and receipts are rejected.
Accounting fields only. Receipts never record prompt or completion text.
Base settlement
Worker rewards accumulate in the ledger. A keeper batches them into a deterministic batch and prepares an on-chain settlement that settles once — a batch settles a single time. The settlement contracts are deployed on Base; settlement runs operator and keeper driven, prepared off-chain first, not as a continuous automatic service.
Ledger → Keeper → Base
Ledger
worker rewards
Keeper
batch · prepare
Base
settles once
soon
on-chain settlement activating
$BASIS & Bankr
Apps and agents pay in $BASIS, workers earn $BASIS, and the two fee streams are kept apart. $BASIS is live on Base — it came to market through Bankr, which is the launch rail, not the inference backend. This is not yield and not an investment.
Pay
Apps and agents pay for inference in $BASIS.
Earn
Workers earn $BASIS for completed, verified jobs.
Fee rails
WETH-side and $BASIS-side fee streams stay on separate rails.
Launch rail
$BASIS came to market through Bankr on Base and is live.
WETH-side · $BASIS-side
WETH-side
ETH-denominated
separate
soon
$BASIS-side
token-denominated
separate
soon
The WETH side and the $BASIS side are never blended into one number.
Developer quickstart
Point any OpenAI client at Basis. Use the model basis-default, stream /v1/chat/completions, and the request flows through the same loop every job does.
Stream a completion
curl -N https://basis.watch/api/v1/chat/completions \
-H "Authorization: Bearer sk-basis-..." \
-H "Content-Type: application/json" \
-d '{"model":"basis-default","stream":true,
"messages":[{"role":"user","content":"Summarize this for an agent."}]}'Same client, one base URL
from openai import OpenAI
client = OpenAI(
base_url="https://basis.watch/api/v1",
api_key="sk-basis-...",
)
client.chat.completions.create(
model="basis-default",
messages=[{"role": "user", "content": "Hello from an agent."}],
)Worker quickstart
A worker registers, heartbeats, and serves inference. The orchestrator counts output tokens server-side — worker-reported counts are advisory. Completed, verified jobs earn $BASIS; failed jobs earn nothing. The contributor worker network is being activated.
Connect wallet
A worker needs a valid EVM reward address to earn.
Register
Announce the worker to the network.
Heartbeat
Stay live so the orchestrator can route to you.
Serve
Run inference jobs the gateway dispatches.
Earn $BASIS
Completed, verified jobs earn. Failed jobs do not.
Build on Basis
An OpenAI-compatible API, contributor GPUs that earn $BASIS, and a verifiable receipt for every job — settled on Base.