Integration Guides
Where PayReality connects to the rest of your stack, and an honest split between what works today and what's a dedicated connector we haven't built yet.
Authorization is a call site, not a platform integration. PayReality doesn't need to be built into a given agent framework to work with it: any Python process can call the SDK's authorize() before taking an action, at the exact point where the agent would otherwise act. That's why LangGraph, CrewAI, AutoGen, MCP, the OpenAI Agents SDK, and Anthropic's Claude Agent SDK all already work today, without a dedicated connector or a named integration package for any of them, and why PayReality stays independent of whichever framework or orchestration layer you're running.
None of the entries below are a fabricated "it just works" integration, though. Cloud platforms and enterprise systems that would need a dedicated connector, rather than a direct SDK call, are marked accordingly.
This page is specifically about that connector surface: where an Agent's own SDK call reaches a given framework or platform. It's a different surface from the Trusted Adapter observation boundary, which reports what a real enterprise operation actually is, independently of what an Agent says about it.
Agent frameworks and protocols
Already usable today via authorize(), as described above: these frameworks are all Python-native.
Cloud AI platforms
These require a dedicated connector to bridge the platform's own agent runtime to the Intent API, not yet built.
Enterprise systems
The system of record a compatible enforcement point ultimately writes to, once it has independently verified and acted on a decision, connector work not yet started.
DevOps
Microsoft Agent Governance Toolkit
Microsoft Agent Governance Toolkit is one possible agent-runtime and enforcement environment. PayReality does not replace its identity, sandboxing, technical policy, monitoring, or agent-SRE capabilities; PayReality adds the cross-system organizational-authority decision and authority-lifecycle evidence a runtime like AGT doesn't itself produce. PayReality does not depend exclusively on Microsoft AGT: the same authority contract described in Architecture is intended to work with other runtimes, gateways, and customer-controlled enforcement points. There is no shipped AGT adapter today, and no formal partnership or endorsement between PayReality and Microsoft; if and when an AGT connector is built, it will appear in the table above the same way any other connector does.
What "Early Access" means here
There's no PayReality-published package for any of the frameworks above: "Early Access" means the existing Python SDK already gives you what you need to wire it in yourself (call authorize() at the point your agent would otherwise act), not that a named integration package exists. See SDKs and Integration Examples for the calls involved.