One-install Fivetran front door over five bounded capability packs and 55 non-chat, uncached, read-only workflows. It admits 168 of 171 official operations across 99 paths. Exactly one provider-deprecated certificate route and two Connector SDK ZIP upload routes that the current REST transport cannot represent are excluded. Connections, schemas, destinations, groups, identities, teams, keys, certificates, external secrets managers, hybrid and proxy deployment, transformations, logs, and webhooks are covered. The public metadata route is isolated in a connectionless ingredient; all 167 remaining capabilities use connection-owned API-key/API-secret Basic authentication at api.fivetran.com. Nineteen operations retain their exact application/json;version=2 Accept header. Thirty-one documented cursor collections automatically request up to 1000 items per page; two ESM responses whose official requests omit cursor and limit remain explicit single-page gaps. All 64 admitted JSON bodies are required and sent verbatim because the OpenAPI omits requestBody.required. The Connector SDK download is captured as a private ZIP because its operation description contradicts the generated JSON response media. Recoverable-token and credential-capable reads remain callable but are excluded from rendering workflows. Reads are uncached and require no approval, every mutation requires approval, unsafe response integers remain exact strings, and rate-limit failures surface without hidden retries. No pipeline, account, or infrastructure object is claimed as a task, note, or user-work project Source.