OMP/1 · v0.5.2 · English
The profile that gives agent standards verifiable, jurisdiction-aware authority
A profile, not a rival
AP2 lives at the FIDO Alliance, MCP at the Linux Foundation, XAA is open. OMP defines how jurisdiction-aware, machine-verifiable mandates sit on top: AP2 payment mandates become a payment.* subtype, XAA identities carry OMP mandates externally, EUDI and Swiss E-ID wallets provide the identity root.
Law first
Each mandate hash-binds a reviewed legal text (Swiss CO Art. 32 et seq., BGB §164 et seq.). contract.sign does not exist in the taxonomy — final signatures remain human (QES). No other agent-economy standard carries this layer.
Proof as an obligation
Verifiers must check live status (no-store). Every decision carries exactly one of 19 stable codes plus a signed receipt; the evidence chain is append-only, enforced in the database.
Implemented bridges
MCP (5 tools, verified over stdio). OAuth/RAR (RFC 9396) is preview and currently disabled — the token endpoint returns 410 Gone. Use /v1/verify for the full trust path.
The emerging agent standards, mapped field by field
Verifiable Intent (Mastercard), AP2 (Google), the FIDO working groups and Web Bot Auth (RFC 9421) describe the same core OMP carries: SD-JWT credentials, selective disclosure, key-bound delegation from human to agent, machine-readable limits. The mapping is published field by field, using both sides' real claim names — including what is not congruent. The Verifiable Intent bridge runs both ways: the export passes the verification chain of Mastercard's reference implementation, and the same chain is taken in as a presentation and decided by our engine. The classic AP2 trio (intent/cart/payment) is taken in as well — built and signed with Google's reference models, decided by the same engine. The FIDO Alliance has been merging both contributions in its Payments TWG since April 2026 — exactly the two references running here. Verifiable Intent standardizes the credential for the purchase; Mandact is the layer that format deliberately leaves out — the qualified identity anchor, runtime revocation, escalation with evidence, signed receipts, and the action types beyond purchasing.