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

# Overview

Klavis API is built on REST principles. We enforce HTTPS in every request to improve data security, integrity, and privacy. The API does not support HTTP.

## API Structure

**Server:** `https://api.klavis.ai`

> [card] [Sandbox API](https://www.klavis.ai/docs/api-reference/sandbox/create.md)
>
> Use the Sandbox API to manage isolated MCP sandbox environments for LLM training and evaluation. Handles account pooling, state initialization, export, and teardown for reproducible AI workflows.

> [card] [Local Sandbox API](https://www.klavis.ai/docs/api-reference/local-sandbox/acquire.md)
>
> Use the Local Sandbox API to manage k8s-pod local sandboxes for filesystem, terminal, browser, and document workflows during agent training and evaluation.

> [card] [Universe API](https://www.klavis.ai/docs/api-reference/universe/list-universes.md)
>
> Use the Universe API to acquire benchmark task environments and verify task completion for end-to-end agentic evaluation.

> [card] [Strata API](https://www.klavis.ai/docs/api-reference/strata/create.md)
>
> Use the Strata API to manage the unified MCP server that guides AI agents to use tools progressively. Solves tool overload, context limits, and coverage gaps for reliable agentic workflows.

> [card] [Single Integration API](https://www.klavis.ai/docs/api-reference/mcp-server/create-a-server-instance.md)
>
> Use the Single Integration API to manage individual MCP server instances. This allows you to provision and control specific tool integrations one by one.

> [card] [User API](https://www.klavis.ai/docs/api-reference/user/get-user.md)
>
> Use the User API to manage users within your organization. This includes retrieving user details, managing user-specific integrations, and handling user deletion.

> [card] [OAuth API](https://www.klavis.ai/docs/api-reference/oauth/airtable-oauth/authorize-airtable.md)
>
> Use the OAuth API to handle authentication flows for your integrations. This covers the authorization processes required to connect third-party services securely.

> [card] [White Label API](https://www.klavis.ai/docs/api-reference/white-labeling/create.md)
>
> Use the White Label API to manage white-label configurations, allowing you to present integrations under your own branding.

## Response codes

Klavis uses standard HTTP codes to indicate the success or failure of your requests.

In general, 2xx HTTP codes correspond to success, 4xx codes are for user-related failures, and 5xx codes are for infrastructure issues.

| Status | Description |
| - | - |
| 200 | Successful request. |
| 400 | Check that the parameters were correct. |
| 401 | The API key used was missing. |
| 403 | The API key used was invalid. |
| 404 | The resource was not found. |
| 429 | The rate limit was exceeded. |
| 5xx | Indicates an error with Klavis servers. |

Check Error Codes for a comprehensive breakdown of all possible API errors.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.