# For AI agents

These docs are designed to be read by LLMs and coding agents as well as people. If you are an agent building an integration against Sodot MPC Infra, start here.

## Reading the docs as an agent

* **`/llms.txt`** is a concise, link-indexed map of the whole site.
* **`/llms-full.txt`** is the full documentation as a single Markdown file.
* Append `.md` to any page URL for clean Markdown. For example, this page is available at `/for-ai-agents.md`.
* Every page also has a "copy as Markdown" action in the bottom bar.

An MCP endpoint for these docs arrives when the site moves to a server runtime; until then, `llms.txt` and the `.md` twins are the intended machine interface.

## The shape of the product (what to explore)

* **[MPC Infra](/mpc-infra/intro)**: the product overview. Keys are generated and used as Multi-Party Computation between SDKs and a self-hosted signer; no complete private key ever exists anywhere.
* **[Vertex](/vertex/overview)**: the self-hosted MPC signer, driven over a REST API. Most integrations are "call Vertex endpoints in the right order".
* **SDKs** ([Web](/web/getting_started), [Node](/node/getting_started), [React Native](/rn/getting_started), [Go](/go/getting_started), [Kotlin](/kotlin/getting_started), [Swift](/swift/getting_started), [Unity](/unity/getting_started), [Rust](/rust/getting_started)): client-side parties for the MPC protocols. Web, Node, React Native, and Go include full API references under `/<sdk>/api-ref/` (Markdown, agent-friendly).
* **[Cryptography](/cryptography/signature-scheme)**: the protocol background (DKLs23, FROST) if you need to reason about the security model.
* **[Relay Server](/relay-server/relay_dev_env)**: the message-relay component every MPC operation runs through.

## Using the Vertex API from an agent

Vertex is a REST API with an OpenAPI-documented surface:

* **Interactive API reference:** [docs.sodot.dev/vertex-api-reference/](https://docs.sodot.dev/vertex-api-reference/) (Scalar viewer with the full spec, including request/response schemas and error types).
* Authentication is an API key in the `Authorization` header; user- and admin-level keys have different permission scopes (see [Users and Access Control](/vertex/users_and_access_control)).
* Typical flow for a signing integration: create a relay room, run keygen across parties, then sign. The endpoint order is shown concretely in the [Solana example](/examples/mpc-infra/solana-example) and each SDK's Getting Started page.

## Ground rules worth knowing

* Rooms are single-use: every MPC operation (keygen, sign, refresh, export) needs a fresh room from `/create-room`.
* Thresholds are t-of-n: any t parties can sign; keygen requires all n online.
* Signing policies, [groups](/vertex/groups), and the [kill switch](/mpc-infra/kill-switch) constrain what any identity (human or agent) can do with a key; agents get no special bypass.