# RunPane API docs

The RunPane website API gives agents public product context. It doesn't create panes or read local repos. Use the local [`runpane` CLI](/docs/runpane-cli) for that.

## Start here

1. Read the [RunPane OpenAPI document](https://runpane.com/openapi.json).
2. Use [Ask Pane](/docs/ask-pane) for public product questions.
3. Read [RunPane API auth](/docs/auth) before sending a request.
4. Follow the response schema and media types for each operation.

Every OpenAPI operation has a unique `operationId`, a description, typed parameters, and a typed response schema. You can turn those operations into function calls without guessing field names.

## Versioning and deprecation

The current API version is `2026-07-09`. Responses include `API-Version` and `RunPane-API-Version` headers.

Additive changes stay on the current paths. A breaking API gets a new path version, such as `/v2`. Unversioned paths point to the current version.

When we retire an old path:

1. We send a `Deprecation` header.
2. We send a `Sunset` header with the retirement date.
3. We send a `Link` header to the migration guide.
4. We give you at least 90 days of notice before the Sunset date.

Current endpoints aren't deprecated.

## Response formats

Most discovery endpoints return JSON, Markdown, XML, or plain text. Check the `content` map for the exact media type. Redirect operations use the `Location` header.

All public API responses include rate limit and lifecycle links. You don't need to send a version header today.