ATP CORE · INTEROPERABILITY

Trust travels across systems.

ATP is meant to integrate with existing protocols and frameworks, adding identity, trust evidence, authority, policy, audit, and privacy around agent interactions. It does not replace MCP, A2A, ANP, or ADK.

Explore an integration pattern.

These pages describe possible boundaries and available examples. Implementation coverage varies; inspect the canonical ATP Core repository before relying on an adapter.

PROTOCOL

MCP

Explore where identity and trust evidence could surround MCP servers and tool calls.

Explore pattern →FRAMEWORK

LangChain

Consider ATP at an agent or tool boundary in LangChain and LangGraph applications.

Explore pattern →LEGACY · OPTIONAL

OpenClaw

Inspect the optional legacy adapter example. ATP Core does not depend on OpenClaw.

Explore pattern →

Building another adapter?

Start with the SDK and a concrete conformance case. We welcome examples for any agent ecosystem.

Explore ATP Core and contribute →

ATP Community Group drafts are not W3C Standards. Integration examples do not certify a deployment.