MCP, A2A, x402, and AP2 already describe connection, collaboration, and payment. EXOCHAIN’s place is the layer they do not replace: legitimate decision-making authority that an independent counterparty can verify.
Payment authorization is not legitimate decision-making authority.
Standardizes how AI systems connect to tools and resources.
A tool call can succeed without a portable proof that the caller was entitled to make that decision.
Lets agents collaborate across systems.
Collaboration still needs a way for each side to verify the other’s delegated authority.
Makes machine-native payments possible.
A payment rail does not decide whether the purchase itself was a legitimate exercise of authority.
Uses signed mandates and receipts for agent-initiated payments.
A mandate to spend is not the same record as vendor selection, evidence, conflicts, constraints, and revocation.
An agent may be authorized to spend. That does not answer whether it had authority to select the vendor, which evidence supported the decision, whether conflicts were disclosed, whether the delegation was still valid, or whether applicable constraints were satisfied. The counterparty should be able to check that chain without access to the issuer’s internal systems.
Bring one constrained, cross-organizational workflow — a procurement decision or an executive approval, for example — where two parties need to verify legitimate authority without sharing an internal system. Developers can start from the SDK in the public repository.