Reference scope
The developer workspace documents the canonical evaluation API, SDK scope, MCP transport, trusted bindings, and protected-receiver evaluation. Inspect each adapter and SDK for its actual supported surface.
2AYE Connect / Shared integration layer
Connect authority to the systems that execute.
Carry exact action authority through MCP, APIs, SDKs, and deployment-owned destination bindings.
Part of All six products. This capability guide introduces no separate product, subscription, or universal integration claim.
Integration and verification requirements
Providers, receiver trust, credentials, and redemption ownership need explicit configuration. Catalog entries are not evidence of deployed adapters. A remote receiver that needs no issuer database remains a separate architecture and acceptance requirement.
Use case / Connector operator
Bind an MCP tool to a fixed protected destination.
Illustrative integration review. These controls explain the design; they do not submit requests, grant authority, or execute an action.
Inspect the flow
Stage 1
Define scope
Bind an MCP tool to a fixed protected destination.