Skip to main content
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.

Surface map

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

​
Surfaces and status

​
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.
  4. To confirm a deliverable, use verification.
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.