Documentation
Technical docs for consuming, publishing and auditing ForgeRouter endpoints.
ForgeRouter is an open marketplace for OpenAI-compatible inference endpoints. These docs separate client API usage, provider publication, marketplace trust, billing and security controls.
API clients
Consume OpenAI-compatible endpoints, configure policies and inspect request audit data.
Providers
Publish endpoints and deployments with explicit pricing, checks and proof labels.
Admins
Operate accounts, legal acceptances, billing corrections, suspensions and incidents.
Operators
Use internal runbooks for preprod, queues, gateway incidents, billing reconciliation and rollback.
Documentation overview
Audience map, documentation conventions and public documentation boundaries.
Client guide
Create keys, fund inference credits, choose routing policies and inspect requests.
OpenAI-compatible API
ForgeRouter API routes, authentication, streaming and marketplace audit metadata.
Provider guide
Publish endpoints, deployments, pricing and ForgeNode-reported runtime data.
Trust and routing
Marketplace tiers, proof labels, routing profiles, Community opt-in and request audit.
Billing, wallet and statements
Client-first billing, provider prices, platform fees, append-only ledger and statements.
Security and data handling
Gateway controls, logs, secrets, limits, Community caveats and compliance boundaries.
Content conventions
- Provider claims are labelled as declared by provider until verified.
- Availability and performance samples are labelled as measured by ForgeRouter.
- Manual checks are labelled as verified by ForgeRouter with the checked dimension.
- ForgeNode inventory and heartbeat data are labelled as reported by ForgeNode.