QuickBooks API integration with managed OAuth. Install only if you need QuickBooks accounting administration. Connect with a least-privileged QuickBooks account, verify the intended connection ID before each request, and revoke unused connections promptly. This integration can mutate accounting records — approve only specific write actions after checking the exact endpoint, account, resource ID, amounts, and consequence. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. The endpoints documented here are the intended surface, not a technical limit — the `maton api` passthrough can reach others the connection permits. Default to read and list calls, and confirm every write or new connection with the user.
Judge writes by what the call does rather than its HTTP method: QuickBooks routes updates and deletes through POST with ?operation=, so the verb carries no intent. Also replace the generic high-impact category list with QuickBooks operations (money and ledger state, closed or reconciled periods, void versus delete, record merges, batch requests) and name QuickBooks' own fields as the untrusted-input sources