Introduction
Webway is one OpenAI-compatible endpoint in front of every provider, billed per token from prepaid credit.
Point your existing OpenAI client at Webway, change the base URL, and keep the rest of your code. One key reaches every model in the catalogue.
There is no subscription and no per-seat pricing. You hold prepaid credit, and each request draws down what it costs — exact to the micro-dollar, priced at the rates on the model's own page.
How it fits together
Three things make up an account:
- An organization holds the credit and owns everything below it. Signing up provisions one; teams are people you invite into it.
- API keys authenticate requests. They belong to the organization, not to you, so revoking a teammate does not break production.
- Usage is one row per request — tokens, cost, latency, and whether it succeeded. It is what the dashboard reads and what the invoice is made of.
What is different
Nothing about the request shape. POST /v1/chat/completions takes the body you
already send and returns the response you already parse, so a migration is a
base URL and a key.
What changes is underneath: routing to whichever provider serves the model, metering every call, and drawing the cost from credit rather than from a card at the end of the month.
Where next
- Quickstart — from nothing to a reply.
- Models — what is in the catalogue and what it costs.
- Credits and billing — how the money works.