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

# Schemas & SDKs

> Quick-start reference for AdCP schemas and client SDKs: installation, schema URLs, version discovery, and where to go next.

This page orients you to the two foundational resources for building with AdCP: the JSON schemas that define every request and response, and the SDKs that turn those schemas into typed code.

## SDKs

AdCP ships official SDKs for TypeScript, Python, and Go. Each SDK absorbs the protocol layers (wire format, signing, auth, lifecycle semantics) so you write business logic only.

> **[TypeScript](https://www.npmjs.com/package/@adcp/sdk)**
>
> `npm install @adcp/sdk`

> **[Python](https://pypi.org/project/adcp/)**
>
> `pip install adcp`

> **[Go](https://github.com/adcontextprotocol/adcp-go)**
>
> `go get github.com/adcontextprotocol/adcp-go`

For the full coverage matrix (which layers each SDK ships today), version pinning guidance, and package export details, see [Choose your SDK](https://docs.adcontextprotocol.org/dist/docs/3.1.24/building/by-layer/L4/choose-your-sdk).

For the layered model behind the SDKs — what L0 through L4 each contain and why SDKs matter more in AdCP than in simpler protocols — see the [SDK stack reference](https://docs.adcontextprotocol.org/dist/docs/3.1.24/building/cross-cutting/sdk-stack).

## Schema URLs

AdCP schemas are published at `https://adcontextprotocol.org/schemas/` under the current major-version alias:

| Pattern | Example | Use |
| - | - | - |
| **Current major** | `https://adcontextprotocol.org/schemas/3.1.24/media-buy/create-media-buy-request.json` | Pin validators to the AdCP 3.x schema family |

Schemas cover every task's request and response, shared enums, governance objects, creative formats, and signal definitions. Use the current major-version URL in production and CI so links stay stable across major releases.

For how wire-level `adcp_protocol_version` relates to schema bundle versions, and why those are different things, see [Versioning & governance](https://docs.adcontextprotocol.org/dist/docs/3.1.24/reference/versioning).

## Authorization in adagents.json

Publishers declare their agent endpoints and authorization scopes in `adagents.json`. The schema supports six authorization types — `property_ids`, `property_tags`, `inline_properties`, `publisher_properties`, `signal_ids`, and `signal_tags` — each scoping which inventory the agent is authorized to act on.

For the full authorization type reference and worked examples, see [Authorization Patterns](https://docs.adcontextprotocol.org/dist/docs/3.1.24/governance/property/adagents#authorization-patterns) in the governance docs.

## Where to go next

> **[Choose your SDK](https://docs.adcontextprotocol.org/dist/docs/3.1.24/building/by-layer/L4/choose-your-sdk)**
>
> Coverage matrix, install commands, and version pinning for each language.

> **[Build an agent](https://docs.adcontextprotocol.org/dist/docs/3.1.24/building/by-layer/L4/build-an-agent)**
>
> Skill files and step-by-step guide for building a seller agent.

> **[Build a caller](https://docs.adcontextprotocol.org/dist/docs/3.1.24/building/by-layer/L4/build-a-caller)**
>
> Buyer-side reference for discovering capabilities and handling responses.

> **[Validate your agent](https://docs.adcontextprotocol.org/dist/docs/3.1.24/building/verification/validate-your-agent)**
>
> Run the compliance suite to verify your implementation.


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