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

# APIs

> Every interface OneBucket exposes: the S3 API, MCP tools for data, the events API, and the management API.

OneBucket exposes four interfaces. Applications and engines use **S3**; agents use the **data MCP** tools; audit and monitoring use **events**; and everything you configure in the console is also available through the **management API**.

| Interface | For | Auth |
| - | - | - |
| [S3 API](https://docs.onebucket.io/reference/s3-api.md) | Applications, SDKs, query engines, backup tools | Access key, AWS SigV4 |
| [Data MCP](https://docs.onebucket.io/mcp/overview.md#tools) | AI agents and assistants | OAuth 2.1 with PKCE |
| [Events MCP](https://docs.onebucket.io/mcp/overview.md#events) | Audit, monitoring, troubleshooting | OAuth 2.1 with PKCE |
| [Management API](#management-api) | Keys, endpoints and policies as code | Issued on request |

## Endpoints

Every region exposes an S3 endpoint and two MCP endpoints, one for data and one for events. The global endpoints work from anywhere: each request is routed to the live region nearest the caller. Use a regional endpoint when requests must be pinned to a location. Your policies are active in every region.

| Region | S3 (objects) | MCP (data) | MCP (events) |
| - | - | - | - |
| Global | `s3.onebucket.io` | `data.onebucket.io` | `synapse.onebucket.io` |
| `us-ashburn-1` (Ashburn) | `s3.us-ashburn-1.onebucket.io` | `data.us-ashburn-1.onebucket.io` | `synapse.us-ashburn-1.onebucket.io` |
| `us-sanjose-1` (San Jose) | `s3.us-sanjose-1.onebucket.io` | `data.us-sanjose-1.onebucket.io` | `synapse.us-sanjose-1.onebucket.io` |
| `ap-singapore-1` (Singapore) | `s3.ap-singapore-1.onebucket.io` | `data.ap-singapore-1.onebucket.io` | `synapse.ap-singapore-1.onebucket.io` |

All endpoints use HTTPS. More regions are coming online; the current list is on the [support page](https://www.onebucket.io/support), and live availability is on the [status page](https://status.onebucket.io).

## MCP

The data and events MCP servers share one sign-in model (OAuth 2.1 with PKCE, Dynamic Client Registration, authorization server `https://oauth.onebucket.io`) and one tool list, documented once for every client:

> **[MCP overview & tools](https://docs.onebucket.io/mcp/overview.md)**
>
> Endpoints, sign-in, every tool with its parameters, events, and limits.

> **[Connect a client](https://docs.onebucket.io/connectors/claude.md)**
>
> Step-by-step setup for Claude, ChatGPT and Muse.

## Management API

Everything you set up in the console, from keys to backends to policies, can be done through the management API, so your setup can live in your own scripts and pipelines. The full API reference is available on request after [sign-up](https://app.onebucket.io/sign-up).

## Related

> **[S3 API compatibility](https://docs.onebucket.io/reference/s3-api.md)**
>
> Supported operations, addressing styles and errors.

> **[Policies](https://docs.onebucket.io/concepts/policies.md)**
>
> What governs every call these APIs make.


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