> ## Documentation Index
> Fetch the complete documentation index at: https://docs.myrouter.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# OpenRouter Compatibility

> Compatibility stance and differences.

MyRouter V0 uses OpenRouter/OpenAI-style conventions where they reduce customer integration cost.

Aligned:

* `POST /api/v1/chat/completions`.
* `GET /api/v1/models` with model-level `pricing`.
* `GET /api/v1/credits`.
* `GET /api/v1/key`, `GET /api/v1/keys`, and `/api/v1/keys/{hash}`.
* `GET /api/v1/activity`.
* `GET /api/v1/generation`.

MyRouter additions:

* Anthropic-compatible platform-backed surface.
* Product-owned prepaid credits.
* Stripe-style checkout sessions, balance transactions, and invoices.
* Usage and costs reports.
* Account/key abstraction backed internally by platform labels after platform June 4 delivery.

Not V0:

* Postpaid billing.
* Credit line.
* Enterprise contract billing.
* Invoice-grade charge evidence.
* Complex organization/team/project model.
* Cafe24-specific custom fields.
* Public Responses, Embeddings, Rerank, or Gemini runtime APIs.
* Public prompt/completion body retrieval.

Cafe24 requests should be accepted only if they fit the product-standard API or can be added as a general MyRouter capability. Otherwise they should be deferred or rejected.