merkiinference

Endpoints and compatibility

Merki exposes endpoints that are compatible with OpenAI and Anthropic clients. You can point an existing OpenAI SDK or Anthropic SDK at Merki by changing the base URL and the API key, and keep your current code.

Base URLs

  • OpenAI compatible: https://api.merki.dev/v1
  • Anthropic compatible: https://api.merki.dev/v1/messages

Use a Merki API key as the bearer token. See Authentication.

OpenAI compatible

Clients and libraries built for the OpenAI API work against Merki. Change the base URL to https://api.merki.dev/v1 and use a Merki key.

Supported shapes: chat completions (including streaming), embeddings where the model supports them, and usage reporting. Model-specific limits apply, so check the model catalog for context and modalities. Full field coverage: OpenAPI and SDKs.

Anthropic compatible

Clients built for the Anthropic Messages API work against Merki at https://api.merki.dev/v1/messages in the same way.

What this buys you

  • Reuse existing tooling, harnesses, IDE integrations, and agent frameworks.
  • Move between providers by changing a base URL, not a codebase.
  • The same endpoints serve hosted models and BYOK routes, where the provider supports the shape. See BYOK routing.

Notes

  • Compatibility covers the common request and response shapes for each API family. Fields outside the common shapes return a validation error. See Errors.
  • Authentication uses Merki API keys. See API keys and Authentication.
  • Rate limits apply per key and per account. See Rate limits.