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.
MandateShield Execution evidence API is one of 22 APIs that MandateShield publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 2 JSON Schema definitions.
Tagged areas include Execution evidence. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, rate-limit docs, and 2 JSON Schemas.
This API exposes 5 operations across 5 paths, and defines 24 schemas. It is described by OpenAPI 3.2.0, at version 3.4.0.
Requests are made against a single base URL, https://mandateshield.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
MandateShield Execution evidence API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as OAI-Authenticated-User-Email (hostingSession).
It accepts HTTP bearer tokens (ms_test_… or ms_live_…) (bearerAuth).
hostingSession— Hosting-injected authenticated account-owner identity. The hosting boundary validates the user session and injects this assertion; callers cannot authenticate…bearerAuth— Keep API keys server-side and isolate them by purpose. VERIFY keys can issue challenges and strict decisions. Paid live PROCESSOR keys are bound to one process…
Paths & Operations 5
Across 5 paths, the API surfaces 5 operations — 5 POST. Each is listed below with its method, path, parameters, and response codes.
Provider-bound permit redemption, caller observation intake, Stripe API or x402 chain reconciliation that does not trust the caller assertion, autonomous terminal authorization fi…
Schemas 24
The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are ProviderSubmissionReportResult (15 properties), ExecutionPermitRedemptionResult (13 properties), SignedExecutionReceipt (10 properties), ExecutionPermitVerification (9 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from MandateShield 12
Other APIs MandateShield publishes across the network.
This is an independent, third-party profile of MandateShield Execution evidence API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.