Integrations

Classic OAuth Apps cannot request read-only access to private repositories (the 'repo' scope is read/write); the platform only issues read requests. A GitHub App with read-only Contents and Pull requests permissions is the recommended production setup. Pull requests are not complete agent execution traces.

Planned (milestone 4). OAuth with read_api scope.

Planned (milestone 4). Atlassian OAuth 2.0 (3LO), read scopes.

Planned. OAuth with read scope.

Planned (milestone 4). Project API keys; traces may contain end-user content and require rights review.

Planned (milestone 4). Conversations contain personal data; requires DPIA before activation.

Planned. Microsoft Graph; tenant admin consent required.

Planned. Restricted scopes need Google verification.

Planned. Microsoft Graph; tenant admin consent required.

Planned (milestone 4). OAuth; tickets only, contacts excluded.

Planned. Connected app with read-only profile.

Planned.

Planned. Financial records need extra rights review.

Planned.

Planned; only where Stripe's terms permit the intended data use.

Planned. GraphQL API with app approval.

Requires ServiceTitan partner approval; not available until granted.

API access limited to certain plans; requires authorization.

Planned. OAuth add-on registration required.

Read-only access to orders, catalog and locations. Customer details, card data, ticket names and notes are not collected. Use of merchant data must stay within Square's developer terms and the merchant's consent.

Planned. Requires Lightspeed API partner access.

Requires Toast partner approval; not available until granted.

Planned. read_orders/read_products scopes; customer data excluded.

Planned. Read-only REST keys.

Planned. OAuth read scope; requester identities masked.

Planned. API key, read-only agent.

Planned. OAuth with a read-only integration user.

Planned. Restricted read-only role, allow-listed tables, network egress controls.