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

# Integration surfaces

> The ways a partner system touches Soteris, and the status of each.

Soteris exposes a small set of integration surfaces. In v0 the set is read-oriented: learn state, inspect records. No surface below is a live public write endpoint unless Soteris has released one by arrangement.

<Card title="Surface map">
  <img className="block dark:hidden" src="https://mintcdn.com/soterislabs-32/59q7FHdZ0a37RCqD/images/diagrams/surface-map-light.png?fit=max&auto=format&n=59q7FHdZ0a37RCqD&q=85&s=81e9f34b7bc077f8e775ff6df0a485be" alt="Surface map: what a partner system reads across the Soteris surfaces" width="3600" height="2025" data-path="images/diagrams/surface-map-light.png" />

  <img className="hidden dark:block" src="https://mintcdn.com/soterislabs-32/59q7FHdZ0a37RCqD/images/diagrams/surface-map-dark.png?fit=max&auto=format&n=59q7FHdZ0a37RCqD&q=85&s=86ae6ac6969f504b48956ea42ab97710" alt="Surface map: what a partner system reads across the Soteris surfaces" width="3600" height="2025" data-path="images/diagrams/surface-map-dark.png" />

  What a partner system reads: docs, portal, data mapping, agent-readable records, and verification.
</Card>

## Surfaces and status

| Surface                | What it is                                                                | Status                             |
| ---------------------- | ------------------------------------------------------------------------- | ---------------------------------- |
| Developer docs         | The contract layer: states, records, boundaries, verification.            | `Available`                        |
| Portal                 | The system of record. Humans act on engagements here.                     | `Available to provisioned users`   |
| Partner data mapping   | An agreed mapping of partner-side fields onto Soteris records and states. | `Available by arrangement`         |
| Agent-readable records | Read models an agent can inspect to reason about an engagement.           | `Available within permitted scope` |
| Verification           | Confirming released-record metadata against a receipt.                    | `Public and permissioned checks`   |
| Public API             | Programmatic read and write over engagement records.                      | `Not currently public`             |
| Webhooks               | Push notifications on state or release changes.                           | `Not currently public`             |
| MCP actions            | Agent-invokable Soteris operations.                                       | `Not currently public`             |
| SDKs                   | Language clients over the public API.                                     | `Not currently public`             |

## Choosing a surface

1. To build a mental model or a partner mapping, start with these docs. The vocabulary is stable enough to map against.
2. To act on a real engagement, use the portal. It remains the authority for state and release.
3. To let an agent reason about an engagement, use the agent-readable records within the permitted scope, following the [Agent guide](/start/agent-guide).
4. To confirm a deliverable, use [verification](/verification/verification-model).

<Info>
  The API, webhooks, MCP actions, and SDKs are named for planning, not as live surfaces. Where a workflow needs a programmatic surface that is not yet public, the current path is the portal plus an agreed data mapping. Coordinate with Soteris before assuming any write capability.
</Info>