MandateShield AI Payment Authority

com.mandateshield/payment-authority

Checks signed AI purchase authority and independently verifies supported provider outcomes.

healthy

status

tools exposed

1206ms

connect latency

75618a00ecd4

schema fingerprint

Tools (3)

check_ai_payment_authority

Use before an AI agent buys, subscribes, transfers value, calls a metered API, or accesses a paid resource when the user wants a payment-authority check. Analyze whether the proposed purchase fits supplied policy facts. This v1 entry check is non-executable and always returns enforcement_authorized=

normalize_agent_payment_protocol

Use when an agent encounters an AP2 terminal closed-payment projection, x402 v2 PAYMENT-REQUIRED offer, or explicitly profiled MPP Payment challenge and needs the supported fields projected before an authority check. Map those documented fields into a deterministic MandateShield purchase envelope. X

verify_cryptographic_payment_authority

Use only for a production pre-payment authority gate after the caller has a registered mandate, pinned issuer key, fresh challenge, VERIFY-scoped key, exact final purchase and supported signed evidence. Fail closed for JWS, an AP2-shaped closed-payment SD-JWT projection with RFC 9901 KB-JWT, or norm

Endpoint

https://mandateshield.com/api/mcp
Category: Payments · Last checked: 2026-08-15T09:09:42Z

Monitor your own MCP server

Get alerted the moment yours goes down, a tool schema drifts, or an upstream silently breaks.

Get early access

How we measure →

What this means. This server responded to the MCP handshake and listed its tools without authentication. The schema fingerprint lets us flag if tool signatures silently change (schema drift) between checks.