MandateShield Execution evidence API

Provider-bound permit redemption, caller observation intake, Stripe API or x402 chain reconciliation that does not trust the caller assertion, autonomous terminal authorization finalization and signed execution-evidence verification. A signed webhook is an authenticated hint; terminal authority requires MandateShield to check the configured provider record or canonical-chain proof. This is not verification by an independent organization. Publication does not claim PSP adoption, partnership, certification or PROVIDER_ENFORCED status.

Operations 5

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

POST /api/v2/execution-permits/verify Verify a signed execution permit · Verify a signed provider-bound execution permit #
Ask an LLM
“How do I check that a provider-bound execution permit's signature and structure are valid?”
“Does verifying a permit tell me whether it was already redeemed or revoked?”
Tell an agent
Verify execution permit {compact}.
Check permit {compact} cryptographically and confirm its audience is exactly {expected_audience}.
POST /api/v2/execution-permits/redeem Claim an execution permit before provider submission · Atomically claim one provider-bound execution permit #
Ask an LLM
“How does a payment processor atomically claim a one-use execution permit before submitting?”
“What happens if two executors try to redeem the same permit at the same time?”
Tell an agent
Redeem execution permit {compact} for request {expected_request} with idempotency key {idempotency_key}.
Claim permit {compact} against the exact signed request {expected_request}, sending Idempotency-Key {key}.
POST /api/v2/provider-submissions Report a provider payment attempt for reconciliation · Record one provider attempt and reconcile its outcome without trusting the… #
Ask an LLM
“How do I report what happened when my processor submitted a payment to the provider?”
“Does MandateShield trust my reported outcome, or does it check Stripe and x402 evidence itself?”
Tell an agent
Report provider submission {provider_submission_id} for permit {permit_id} and claim {claim_id}: payment {payment_reference} ended {outcome} at {occurred_at}.
Record that payment {payment_reference} under permit {permit_id} was observed as {outcome} and reconcile it.
POST /api/v2/provider-webhooks/stripe/{connectionId} Receive a Stripe webhook to trigger reconciliation · Authenticate a Stripe event and trigger caller-independent reconciliation #
Ask an LLM
“Where should Stripe send webhook events so payments get reconciled?”
“Is a Stripe webhook treated as proof of settlement or just a reconciliation hint?”
Tell an agent
Deliver this Stripe event to connection {connectionId} with signature {signature}.
Trigger Stripe reconciliation for connection {connectionId} from a signed webhook event.
POST /api/v2/execution-receipts/verify Verify a terminal execution receipt · Verify a signed terminal execution receipt #
Ask an LLM
“How do I verify a signed receipt proving how a payment execution finally ended?”
“Does a valid terminal execution receipt authorize any further execution?”
Tell an agent
Verify terminal execution receipt {compact}.
Check execution receipt {compact} and require its audience to be {expected_audience}.

Documentation

Specifications

Schemas & Data

Other Resources

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/mandateshield-com:mandateshield-com-execution-evidence-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

mandateshield-com-execution-evidence-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: MandateShield Payment Authority Execution evidence API
  version: 3.4.0
  description: Fail-closed authority verification, provider-bound execution permits and provider-outcome reconciliation that is caller-report-independent for autonomous AI-agent purchases.
  termsOfService: https://mandateshield.com/terms
  contact:
    name: Gökhan Vodinali · MandateShield operator
    url: https://mandateshield.com/legal
    email: support@hemelion.com
servers:
- url: https://mandateshield.com
tags:


# --- truncated at 32 KB (35 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/mandateshield-com/refs/heads/main/openapi/mandateshield-com-execution-evidence-api-openapi.yml