# Platform

Architecture, the response envelope, auth, rate limits, error codes and versioning.

Source: https://docs.omazy.ai/reference/platform/

How the platform behaves, for people building against it rather than clicking
through it.

## What lives here

| Topic | Covers |
|---|---|
| **Architecture** | The services, what each owns, and how a message becomes an answer. |
| **Response envelope** | The `success`, `data` and `meta` shape every endpoint returns. |
| **Auth** | Install-scoped tokens, PKCE, and how revocation works. |
| **MCP server** | The tool surface an MCP client administers a business through, and the OAuth flow that reaches it. |
| **Rate limits** | The limits, the headers, and what to do when you hit one. |
| **Error codes** | Every code the platform emits, what triggers it, and what to do. |
| **Versioning** | What is stable, what can change, and how changes are announced. |
| **Changelog** | What shipped, in order. |

## Error codes

The error code is the stable part of a failure. Messages get reworded, HTTP
status codes are coarse, but the code is what you should branch on and what
support will ask you for.

All 33 of them are listed in [Error codes](/reference/platform/error-codes/),
with what triggers each one and what to do about it.

## MCP server

An MCP client can administer a business over
[the MCP server](/reference/platform/mcp-server/): 26 tools covering the agent
and its Brief, knowledge, catalog and widget, reached through OAuth 2.1 with
per-connection read-only or read-write access.

## Coming in this section

The architecture overview, rate limits, and the changelog.