# APIs

::::card-grid
:::card{title="Assistant API reference" href="/guides/apis-assistant-introduction"}
Assistant API reference overview covering document upload, chat, and RAG endpoints supported by the Pinecone Python and Node.js SDKs.
:::

:::card{title="Authentication" href="/guides/apis-assistant-authentication"}
Assistant API authentication with API keys, HTTP headers, and SDK client initialization for Pinecone Assistant requests and RAG apps.
:::

:::card{title="Pinecone Assistant limits" href="/guides/apis-assistant-assistant-limits"}
Reference for Pinecone Assistant limits, including file size, storage, chat token, and rate limits across the Starter, Builder, Standard, and Enterprise plans.
:::

:::card{title="API reference" href="/guides/apis-introduction"}
Pinecone API reference overview for Database, Inference, and Admin endpoints with supported SDKs including Python, Node.js, Java, and Go.
:::

:::card{title="Authentication" href="/guides/apis-authentication"}
Pinecone API authentication guide covering API key generation, SDK client setup, and HTTP header configuration for authorized requests.
:::

:::card{title="Pinecone API versioning" href="/guides/apis-versioning"}
Learn how Pinecone versions its APIs by release date, how long each stable version is supported, and how to set the X-Pinecone-Api-Version header.
:::

:::card{title="Errors" href="/guides/apis-errors"}
Look up the HTTP status codes the Pinecone API returns, what each 2xx success and 4xx or 5xx error means, and where to handle them in production.
:::
::::

## Related pages

- [Account management](./account-management-index.md)
- [Admin](./admin-2-index.md)
- [Admin](./admin-index.md)
- [Architecture](./architecture-index.md)
- [Assistants](./assistants-index.md)
- [Bring Your Own Cloud](./bring-your-own-cloud-index.md)
- [Build an assistant](./build-an-assistant-index.md)
- [Build an integration](./build-an-integration-index.md)
- [Changelog](./changelog-index.md)
- [Changelog](../changelog.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.