overlay: 1.0.0 info: title: API Evangelist enhancements for the Tiger Cloud API version: 1.0.0 extends: openapi/timescale-tiger-cloud-openapi-original.yml x-generated: '2026-08-05' x-method: generated x-source: openapi/timescale-tiger-cloud-openapi-original.yml actions: - target: $.info update: x-apievangelist-provider: timescale x-apievangelist-provider-name: Tiger Data (formerly Timescale) x-apievangelist-harvested-from: https://raw.githubusercontent.com/timescale/tiger-cli/main/openapi.yaml x-apievangelist-note: >- The spec is not published at a docs URL. It lives in the Tiger CLI repository, where oapi-codegen generates the CLI's API client from it. This overlay records what the raw document omits. - target: $.components update: securitySchemes: basicAuth: type: http scheme: basic description: >- HTTP Basic authentication with Tiger Cloud client credentials — the public access key as the username and the secret key as the password. Documented at https://www.tigerdata.com/docs/get-started/quickstart/rest-api ; credentials are created in Tiger Console. The source spec declares no securitySchemes at all, which is why authentication_documented cannot be read from it directly. bearerAuth: type: http scheme: bearer description: >- OAuth user bearer token, used by Tiger Console and the Tiger CLI after `tiger auth login`. The getAuthInfo response discriminates PAT (`apiKey`) callers from OAuth (`oauth`) callers. - target: $.servers update: x-apievangelist-alternate-hosts: - https://console.cloud.timescale.com/public/api/v1 x-apievangelist-note: >- The legacy timescale.com console host still answers on the same path and returns the same JSON error envelope; both hosts were probed and returned HTTP 401 {"code":"UNAUTHORIZED"} for an unauthenticated request. - target: $.info update: x-apievangelist-agentic-surface: mcp_tools_bound: 11 destructive_operation_without_a_tool: deleteService crosswalk: mcp/timescale-tool-crosswalk.yml