ForgeRouter docs

Client guide

Create keys, fund inference credits, choose routing policies and inspect requests.

Community routing warning

The default balanced profile excludes Community deployments. Automatic Community routing is available only after explicit, versioned and revocable opt-in on each API key.

Getting started

  1. Create an account from Create account and verify the email address.
  2. Accept the active Terms of Service and Privacy Policy before creating billable API keys.
  3. Open Billing and add inference credits to the client wallet.
  4. Create a key from API keys and copy the secret when it is shown once.
  5. Call the OpenAI-compatible API with the key stored in an environment variable.

First API call

Examples use environment variables for secrets. Do not paste API keys into source control, tickets or shared logs. 

export FORGEROUTER_API_KEY="your_key_from_the_dashboard"

curl "$FORGEROUTER_BASE_URL/v1/models" \
  -H "Authorization: Bearer $FORGEROUTER_API_KEY"

Client workspace

Client workspace

The dashboard summarizes wallet status, API keys, routing controls and recent requests.

Prepaid inference credits

The client wallet is debited at the provider inference price. ForgeRouter platform fees are charged separately during top-up or contract billing.

Request history

Request history shows routing snapshots, token accounting and billing status without storing prompts or responses by default.

Community status

Community consent is tracked per API key with a policy version, acceptance date and revocation action.

API key policies

  • Routing profile: balanced is the default and excludes Community.
  • Daily budget: caps spend for the key; it is a control, not a service guarantee.
  • Max tokens: limits request and response budget before routing.
  • Maximum provider price: blocks deployments above the accepted price per million tokens.
  • Provider allow or deny lists: restrict eligible providers when the account configures them.
  • Community opt-in: enables automatic Community routing only for that key and can be revoked.

Blocked actions

ForgeRouter fails closed when account state, legal state, wallet state or routing policy is incompatible with the request.

  • Unverified email addresses are redirected to verification before dashboard actions.
  • Suspended accounts and suspended keys cannot create new billable requests.
  • Missing legal acceptances block API key and billing workflows until accepted.
  • Insufficient wallet credits block billable calls before routing.
  • Incompatible policy constraints return an error instead of weakening tier, country, price, data policy, exact deployment or capability constraints.