OpenAPI 1.7.0
Adds an optional API-key lifecycle version to rotation requests. The Developer Portal uses it to reject stale concurrent rotations while legacy callers remain compatible.
OpenAPI 1.6.1
Corrects the Developer Portal organization-list schema to match its runtime envelope, detects membership overflow beyond the Production PostgREST row ceiling without returning a truncated list, and binds release verification to the exact API and Developer Portal deployments.
OpenAPI 1.6.0
Separates committed measured usage from active reservations while preserving quota consumption as their sum, retains terminal audio overage after provider completion, and hardens Developer Portal authorization and E2E receiver access.
OpenAPI 1.5.0
Hardens the developer credential surface: the Portal uses retry-safe idempotency, replays never redisplay plaintext secrets, legacy direct calls remain compatible, key metadata is owner/admin-only, and usage exposes only producer-backed practices and measured audio minutes.
OpenAPI 1.4.0
Added eight tenant-scoped webhook management, test, history, retry, and secret-lifecycle operations.
MCP server 1.0.0
The controlled-access PsyMind MCP server adds six scope-filtered tools over existing API v1 operations. It supports the current MCP revision and stateless 2025-era clients, requires an organization-bound service credential, and adds no parallel business logic.
get_client_history, get_usage, and unpaginated outcomes remain API gaps and are not exposed as MCP tools.
Versioning policy
- The URL major version is
/api/v1. - Backward-compatible additions increment the minor version.
- Documentation-only corrections increment the patch version.
- Removing or narrowing a documented request or response contract requires a new URL major version.
This policy is published in the API v1 contract. The API Reference is generated from OpenAPI and shows the current operation-level contract; it does not independently establish the policy.
Current published contract
1.7.0 — current canonical OpenAPI contract for API v1. Inspect the generated reference for the complete current operation set and schemas.
Deprecation and rollout
Breaking changes are not introduced under the existing /api/v1 contract. Operational rollout and rollback are controlled procedures; this page does not promise a fixed deprecation window, SLA, or advance-notice period.
Traceability
The API Reference shows the OpenAPI SHA-256 and developer-site source commit generated during deployment. Use those values together with the request headers documented in the API contract when escalating an integration issue.