Skip to main content
Valkyrie’s public, client-facing API is the inference API: once you’ve deployed a model, you call it over a standard, OpenAI-compatible (and Anthropic-compatible) endpoint from any client or SDK.
This is the only externally-supported programmatic surface. Operating Valkyrie, creating deployments, launching fine-tuning jobs, managing datasets, is done through the dashboard or the MCP server, not a public REST API. There is no public control-plane API to program against.

Base URL

Use the API base URL for your environment. If your organization runs a separate environment, substitute its host. API keys are environment-specific.

Endpoints

A ready deployment is addressed by its slug, deployment-{id} (for example deployment-227), or by an alias:
An alias points at a deployment or an inference pool. A pool alias serves only the OpenAI-compatible routes, plus GET /{account_slug}/{alias}/v1/status and DELETE /{account_slug}/{alias}/v1/session. Its Anthropic-compatible routes return 400. See Point an alias at an inference pool.
  • OpenAI-compatible follows the Chat Completions contract, see Chat Completions.
  • Anthropic-compatible follows the Messages contract, so Claude clients work, see Connect Claude Code.

Authentication

Send a deployment API key (vk_dep_). An alias that points at an inference pool needs an account-wide key. Keys scoped to one endpoint get 403 there. See Authentication.

Compatibility

Because the inference API is OpenAI- and Anthropic-compatible, you can use the official SDKs, LangChain, and most third-party clients by pointing them at your deployment’s base URL. See Connect a model.