Developers

A programmable surface for the work your product owns.

These resources document the production surface behind our research and advisory engagements. Access is currently arranged with our team. The interfaces let AI assistants inspect and update product-owned customer work. Code mode is the primary agent interface where it is enabled for an integration; REST provides the versioned protocol surface and MCP supports compatible clients. The public resources below document only currently exposed production capabilities.

Quickstart

Start from the work your product should own.

curl --fail --silent --show-error \
  https://api.thruwire.ai/api/v1/healthz
  1. Define the customer-specific goals, evidence, decisions, artifacts, actions, and outcomes the product maintains.
  2. Choose the available code-mode, REST, or MCP surface that fits the agent integration.
  3. Obtain an identity token through the ThruWire Studio authentication flow and send REST credentials only as an Authorization: Bearer header.
  4. Keep project, version, and execution identities explicit; inspect current work before updating it.

Developer resources

REST API

The production origin is https://api.thruwire.ai. Public operations and protected project workflows are described at /docs. Streaming execution operations use server-sent events. Handle authentication, authorization, conflicts, validation, throttling, and server errors as distinct cases.

Model Context Protocol

Connect to https://api.thruwire.ai/mcp. The authorization server advertises authorization-code, refresh-token, and client-credentials grants, PKCE, and the mcp scope. Use OAuth discovery and send access tokens in the Authorization header.

Access and environments

These docs describe the production API. A public sandbox, self-serve API-key process, and published CLI are not currently claimed. Contact hello@thruwire.ai for access questions.