Platform fundamentals
Versioning and compatibility
Track the stable REST version, MCP capability discovery, and changes to the public platform.
Verified against the implementation ·
REST versioning
- The current stable REST base path is /v1.
- The OpenAPI document currently reports version 1.0.0 and OpenAPI 3.1.0.
- Integrations should ignore unknown response fields and should not rely on JSON property ordering.
- Breaking request or response changes belong in a new major API path. Additive endpoints, optional fields, and enum expansion may occur within v1.
- When a v1 endpoint or field is scheduled for removal, PrompTessor announces it in the changelog and returns Deprecation and Sunset headers for at least 90 days before removal, except when an urgent security or legal change requires faster action.
- Read the developer changelog before upgrading SDKs or expanding enabled features.
Legacy API key prefix
pt_test_ is accepted only for existing credentials during migration. New keys use pt_live_. Rotate legacy credentials promptly; PrompTessor will publish their final sunset date in the changelog and response headers before support is removed.
MCP compatibility
MCP negotiates protocol and server capabilities during initialization. Clients should not assume every host exposes tools, prompts, and resources identically. Refresh server metadata after PrompTessor adds or changes tools.