Private AI, paid on Fuel.

Fuel Computer is an AI chat and OpenAI-compatible API funded with FUEL or USDM on Fuel Ignition. The public service is currently a staging implementation with wallet login, API keys and prepaid accounting; on-chain payment acceptance remains disabled until production network and treasury configuration is independently verified.

API quick start

Base URL: https://api.fuel.computer/v1

curl https://api.fuel.computer/v1/chat/completions \
  -H "Authorization: Bearer fuel_…" \
  -H "Content-Type: application/json" \
  -d '{"model":"fuel-fast","messages":[{"role":"user","content":"Hello"}]}'

V1 supports text Chat Completions. Trial requests may stream; authenticated paid streaming remains disabled until terminal token usage can be settled safely. Unsupported fields are rejected rather than silently reinterpreted.

Payments

After a small trial allowance, requests require prepaid USD-denominated credit. A time-limited invoice will quote an exact FUEL or USDM amount, recipient, asset ID, Ignition chain ID and expiry. The service credits only independently verified, final transactions. Ignition transfers require the network base asset for fees.

Payments are public on-chain and prepaid service credit is custodial after receipt.

Privacy

Fuel Computer does not write prompts or completions to its application databases, analytics, or queues. This staging build calls Workers AI directly and does not use AI Gateway; provider retention must be independently verified before production privacy claims are expanded. Chat history is stored only in your browser and can be cleared at any time. Minimal accounting metadata—model, token counts, charge, status and timestamp—is retained. Fuel Computer is private, not anonymous.

Errors

401

Invalid or revoked API key.

402

Insufficient credit. The response contains a funding URL.

413

Input exceeds the service limit.

429

Rate limit reached.

503

Inference or payments are not configured.

Pi provider

The staging @fuel-computer/pi-provider package skeleton registers this API as an OpenAI-compatible provider. It uses FUEL_COMPUTER_API_KEY, never a wallet private key, and presents funding instructions when the API returns HTTP 402.