Changelog

OpenAPI tools

A new tool kind, openapi, gives an agent a vendor’s REST API with no connector to write or host. Store the vendor credential with POST /v1/credentials, compile its OpenAPI document with POST /v1/agents/tool-definitions/import-openapi, keep and classify the operations the agent needs, preview one with POST /v1/agents/tool-definitions/test-openapi-call, and create the tool with POST /v1/agents/tool-definitions. Speechify’s servers make every call, on voice, text and durable runs alike, with the credential resolved from your vault.

Each operation can carry a response mapping (max_items, pick and derive) that trims the vendor’s answer to the fields the agent needs and adds derived strings such as links. The same mapping is available per remote tool on an mcp tool as response_mappings, applied on durable runs.

The credentials vault is now in the public reference, and an oauth2_client_credentials credential can authenticate to its token endpoint with HTTP Basic by setting token_endpoint_auth_method: client_secret_basic.

See Connect a REST API.

Hosted API tool routes and the MCP face

A hosted API route with resolver.type: tool serves one read operation of an openapi tool, under the API’s audience, keys and daily caps. The tool’s approval must be null or auto, since a route has nobody to approve a call, and a route whose tool was deleted or moved answers 409 route_tool_unavailable instead of a retryable error. An API with mcp_enabled: true also serves its routes as MCP tools at POST https://<slug>.apis.speechify.ai/mcp, so Claude Code, Cursor or any MCP client attaches to one address. Hosted APIs remain in beta and enabled per workspace.

See Serve tools over MCP.