Route every request.Know every cost.

One OpenAI-compatible endpoint with prepaid Coin, spend limits, and a trace for every request you send.

Create account

Read the docs

Request lifecycle

POST /v1/chat/completions

How billing works

Process overview. Your real requests and charges appear in Request Explorer.

Service
Published models
Top-up from

One request. Visible economics.

Understand the range

Model, context, reasoning level and output limits produce an estimate. It is never a guaranteed final charge.

estimated
reserved
actual
released

Control plane

Decide before the request is sent.

SmartRoute

Choose a purpose. Inspect the decision.

Ask for an exact model, or use a policy alias. Every candidate is checked against capabilities, availability, limits and price, and the routing reason stays visible.

Policy aliases

smart-code
smart-fast
smart-value
smart-document
smart-premium

An exact model slug is a strict pin. It bypasses alias scoring and never changes to another model.

A candidate is excluded when

Required streaming, tools, vision or reasoning is missing
The provider route is not active or degraded
Requested output exceeds the model limit
Input plus output exceeds the context window
The reservation exceeds the API key per-request budget

Explore routing

SmartBudget

Set the boundary before the request.

Hard limits reject a request before expensive upstream work starts. Reserved Coin and settled spend are tracked separately, and committed in one transaction.

WorkspaceOwner, admin and billing members set the boundary.
ProjectSeparate limits for each environment you run.
API keyRotated keys share one allowance while they overlap.

Each policy can limit

Per request
Daily
Monthly
Protected balance

A hard limit returns HTTP 402 budget_limit_exceeded. A soft limit records a warning. Chanx AI never reroutes a model because of a budget.

Understand budget controls

Model Lab

Compare evidence with its source attached.

Capabilities and operational measurements are labeled by where they come from. There is no invented overall quality score.

Catalog metadata: Capabilities, context, output limits and the active pricing version.
External benchmarks: Attributed observations with a source, methodology and measurement date.
Your workspace traffic: Success rate, latency and average cost from the last 30 days. Prompts and responses are excluded.

Models you can compare now

...

Read from the published catalog.

Open Model Lab

Know what is available.

Published models and service status come straight from the gateway.

Service status

View service status

Keep your client.
Change the endpoint.

Use a project key with Chat Completions or the supported Responses text API. Stream output and follow the request ID into the console.

Get started with curl

Your endpoint: http://localhost:8080/v1

curl http://localhost:8080/v1/chat/completions \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "YOUR_PUBLISHED_MODEL",
    "messages": [{"role":"user","content":"Hello"}],
    "max_tokens": 128
  }'

No model is published yet, so the model is a placeholder. Create and store your key securely. Never embed it in browser code.

Prepaid Coin

Start with a clear balance.

Packages are read from the billing catalog. Pay through QRIS and receive Coin once the payment is verified.

From invoice to Coin

Choose a package
Check the exact amount and Coin grant first.
Pay the exact amount
The QRIS asks for the package price plus a small unique code.
Payment is verified
An administrator confirms it. A scan or redirect never counts.
Coin is credited
The wallet ledger records the credit with its invoice reference.

Top up Pricing and billing details

Trust

Treat keys and Coin as critical infrastructure.

Private by default

Prompts and responses are not stored by default. Request Explorer shows operational and billing metadata.

Scoped access

Project keys, workspace roles, model restrictions, expiration and revocation keep access explicit.

Auditable money movements

Reservations, settlements, releases and top-ups use an immutable ledger. Browser redirects never confirm payment.

Put your AI requests in view.

Create a workspace, check the catalog, and configure your project.