VERIFIABLE INTEGRATION EVIDENCE

Implemented provider contracts, without inflated partnership claims.

This register documents provider integrations represented in the current RYTHM execution gateway. It distinguishes implemented technical capability from customer availability, marketplace approval, certification, or official partnership.

CLAIM BOUNDARY

RYTHM does not claim an official partnership with the providers listed here unless separate reciprocal evidence exists. A registered tool or adapter proves an implemented integration boundary; it does not prove that every customer can connect every provider today.

CURRENT PROVIDER EVIDENCE

Eight provider families are represented in the governed gateway.

All consequential writes remain subject to the applicable permissions, scopes, risk policy, approval path, execution mode, and configured credentials.

REPRODUCIBLE SOURCES

The public evidence can be checked against the implementation.

Tool registry

Provider IDs, tool IDs, operations, scopes, risk levels, approval policy, idempotency, rollback support, and execution mode.

Inspect registry source

Provider adapters

Provider host allowlists, adapter routing, execution, verification, health checks, and supported compensating actions.

Inspect adapter source

Machine-readable register

Versioned provider, operation, documentation, execution-mode, and partnership-claim fields.

Open JSON evidence register

INTERPRETATION

Connection, authorization, and execution are separate states.

Provider credentials and customer-specific availability remain deployment-specific. A connected account still requires the correct scope, Agent capability, user permission, policy result, and Human CEO approval where consequential action is involved.

Review integration architectureReview AI governance

Reviewed and updated 2026-09-03.