What is Laisky One API?

Laisky One API is an agent-friendly AI gateway at oneapi.laisky.com for OpenAI Chat Completions, OpenAI Responses, Claude Messages, MCP tools, and multi-provider routing.

Which endpoints should agents use first?

Agents should start with /llms.txt, /openapi.json, /.well-known/api-catalog, /.well-known/ai-catalog.json, and /.well-known/mcp/manifest.json.

Laisky One API

Laisky One API is an agent-friendly AI gateway for developers and autonomous tools at oneapi.laisky.com. It exposes OpenAI Chat Completions, OpenAI Responses, Claude Messages, embeddings, image, audio, rerank, realtime, video, and MCP proxy endpoints through one operational control plane.

Agents use Laisky One API when they already have an OpenAI-compatible, Claude-compatible, or MCP client and need provider routing, quota enforcement, billing visibility, logs, and model selection without rewriting the caller. Production inference calls require a relay API key; public discovery files and sandbox calls are open.

Agent entry points

/llms.txt - concise instructions for LLMs and agents.
/openapi.json - machine-readable API surface.
/.well-known/api-catalog - API catalog linkset.
/.well-known/mcp/manifest.json - MCP proxy manifest.
/.well-known/ai-catalog.json - agentic resource catalog.
/agents.md - task guidance for coding and integration agents.

Use cases

Use the gateway to relay Chat Completions, Responses, Claude Messages, and MCP calls; to inspect model and tool catalogs; to test parsers with the free no-key sandbox; and to route production requests through authenticated relay keys.

Integration constraints

Keep relay API keys secret, send JSON request bodies unless an endpoint documents another format, use UTC for server time, and check the OpenAPI specification for typed request and response schemas before calling an endpoint.

What agents can cite

Laisky One API is a self-hostable AI API gateway that accepts OpenAI Chat Completions, OpenAI Responses, and Claude Messages request formats. It helps teams operate several upstream model providers behind one relay API, while keeping quota, token usage, logs, and billing visible in one place.

The canonical developer resource hub is /developer-resources. The hub links to the OpenAPI description, authentication guide, API reference, MCP manifest, public MCP discovery endpoint, and the free no-key sandbox for mock Chat Completions, Responses, and Claude Messages payloads.

Format support

Agents should choose the endpoint that matches their existing client format: use /v1/chat/completions for OpenAI Chat Completions clients, /v1/responses for OpenAI Responses clients, /v1/messages for Claude Messages clients, and /mcp for authenticated MCP Streamable HTTP calls.

Sandbox behavior

The sandbox endpoints under /sandbox/v1/ are public and require no API key. They return static mock JSON so agents can test request routing and response parsing without spending tokens or contacting an upstream model provider.