Managed access for Anthropic-compatible clients.

Coreqm accepts messages-style requests from supported clients and routes them to an enabled model provider while enforcing access, limits and usage accounting.

Create free account Read the API docs

What the compatibility layer does

The gateway normalizes supported Anthropic-style requests, resolves model access and forwards the request using the provider configuration selected by the service. Clients keep a straightforward base URL and authentication setup.

A controlled proxy layer

Messages-style requests

Connect clients designed around the Anthropic messages request format.

Secure provider configuration

Keep provider keys encrypted and separate from client-facing Coreqm keys.

Streaming support

Receive compatible streaming responses for supported models and providers.

Limits before forwarding

Check account, key and token allowances before an upstream request proceeds.

Request path

The client sends a supported messages request to Coreqm.
Coreqm authenticates the key and checks available quota.
The gateway resolves an enabled model and compatible provider.
The response streams or returns to the client and usage is recorded.

Frequently asked questions

Does Coreqm claim to be Anthropic?

No. Coreqm is independent and provides a compatibility and management layer.

Are prompts stored?

By default, Coreqm keeps billing and operational metadata rather than prompt or completion content.

Can a key be rotated?

Yes. Client-facing Coreqm keys can be revoked, reactivated where allowed or rotated from the dashboard.

Does compatibility guarantee every provider feature?

No. Support is limited to the endpoints, request fields and models documented by Coreqm.

Connect with Coreqm

Create your account, generate an API key and connect a compatible tool in minutes.

Create free account