---
title: Contract coverage
description: Understand what the generated reference currently verifies and how it stays current.
---

## Current boundary

The published OpenAPI reference currently covers two read contracts: public endpoint inventory at `GET /api/agents` and the internal MCP observations hop at `GET /api/mcp/endpoint`. The latter is loopback-only; external callers use the native MCP `observations` tool.

Download the [StratifyIQ OpenAPI contract](/stratifyiq.openapi.json) for tooling. The site's own `/openapi.json` describes its documentation retrieval API.

That download preserves the source artifact exactly. Its observations schema describes the internal hop; combine it with the MCP connection contract rather than joining that path to a public HTTP base.

These contracts are generated from backend wire types and the native MCP input catalog. They pass generation drift checks, consumer compilation, and schema checks against real handler fixtures.

Other HTTP operations, MCP tools, streams, binary transfers, and website database interfaces are still being reconciled. A discovered route is not a verified request and response contract.

## How the reference stays current

Cloudflare Forge generates the supported artifacts from source-owned contracts. CI checks for source and artifact drift. This documentation site reads the generated OpenAPI at build time and publishes from reviewed main.

Each contract must preserve source validation, authentication, tenant boundaries, attribution, and actual consumer behavior. Streams and MCP discovery retain their native formats.

## Client behavior

Use the schemas and required headers for the operation you call. Preserve nullable values, offline endpoint state, and errors. Runtime authorization and approval remain authoritative as coverage expands.