How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

MandateShield Production authority API

Challenge, strict verification, and processor transitions. The documented eight-field invariant establishes only a RESERVED, consumable authorization; a trusted gateway must obtain the single winning PROCESSOR-scoped CONSUME transition and fresh permit claim before attempting an idempotent provider request. MandateShield does not guarantee exactly-once provider delivery.

MandateShield Production authority 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 Production authority. 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 4 operations across 4 paths, and defines 29 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.

4 operations 4 paths 29 schemas 4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.4.0
Base URL
https://mandateshield.com/api/mcp
Authentication
API Key, HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 2

MandateShield Production authority 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 4

Across 4 paths, the API surfaces 4 operations — 4 POST. Each is listed below with its method, path, parameters, and response codes.

Production authority 4

Challenge, strict verification, and processor transitions. The documented eight-field invariant establishes only a RESERVED, consumable authorization; a trusted gateway must obtai…

POST
/api/v2/challenges
Issue a one-time challenge for a registered mandate
createVerificationChallenge body → 201400401403404413428
POST
/api/v2/verify
Verify signed purchase authority and issue a signed receipt
verifyCryptographicAuthority body → 200400401402409413423428
POST
/api/v2/execution-authorizations
Atomically transition one reserved execution authorization
transitionExecutionAuthorization body → 200400401402403409410413
POST
/api/v2/batch
Verify 1–25 distinct strict authority inputs
verifyCryptographicAuthorityBatch body → 200400413

Schemas 29

The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are ExecutionAuthorizationTransitionResult (20 properties), PurchaseEnvelope (19 properties), EvidenceAssurance (16 properties), PreflightDecision (14 properties). Each schema is shown below with its type and property counts.

PublicVerificationJwk
object
Public signature-verification JWK. The release profile supports P-256 with ES256 and 2048–8192 bit RSA with RS256 or PS256. Registration and request verificati…
10 properties 1 required
Finding
object
3 properties 3 required
StrictDecision
StrictBatchResponse
object
2 properties 2 required
LegalAcceptanceRequiredError
object
4 properties 4 required
CryptographicEvidence
object
JWS, an AP2-shaped closed-payment SD-JWT projection with RFC 9901 KB-JWT, or normalized TAP-shaped RFC 9421-style evidence. AP2 checkoutjwt hash, delegate chai…
10 properties 2 required
ProviderEvidenceClass
string
PROVIDERAPIVERIFIED and CHAINFINALIZED are the current hosted terminal evidence classes checked without trusting the caller report. FACILITATORSIGNED is a reta…
PreflightDecision
object
14 properties 12 required
EvidenceAssurance
object
16 properties 16 required
StrictVerificationInput
object
2 properties 2 required
HttpSignatureInput
object
6 properties 5 required
ChallengeRequest
object
3 properties 3 required
ProviderBindingInput
object
Optional only for CONSUME. Requests a portable provider-bound permit rather than direct legacy gateway submission permission.
8 properties 8 required
Risk
object
5 properties 5 required
SignedExecutionReceipt
object
Historical terminal-state evidence. The signed artifact never grants a new provider submission and does not upgrade the evidenceclass.
10 properties 10 required
ProcessorResult
object
Caller-asserted processor outcome authenticated by the live API key and stored as a canonical digest plus bounded non-secret reference. Processor identity is d…
6 properties 6 required
Challenge
object
11 properties 11 required
SignedExecutionPermit
object
Portable cryptographic permit. It is not a bearer proof of unused state and never authorizes direct provider submission without a fresh online claim.
10 properties 10 required
ProviderSubmissionId
string
Error
object
3 properties 1 required
ExecutionAuthorizationState
string
PurchaseEnvelope
object
Normalized purchase facts for policy and authority verification. For X402 this is a pre-payment verification projection, not an x402 challenge, signed payment…
19 properties 6 required
ProviderEvidenceId
string
ExecutionAuthorizationTransitionRequest
object
8 properties 5 required
SignedDecisionReceipt
object
8 properties 8 required
ExecutionAuthorizationTransitionResult
object
20 properties 20 required
ExecutionAuthorizationReservation
object
RESERVED means the strict ALLOW and cumulative-budget reservation committed atomically. It is not a payment instruction: an integrating processor must obtain t…
6 properties 6 required
TransparencyStatus
object
2 properties 2 required
MandateBinding
object
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mandateshield-com-production-authority-api-openapi.yml Raw ↑

Other APIs MandateShield publishes across the network.

MandateShield MCP Server
MandateShield Payment Authority Agent (A2A)
MandateShield Account execution control API
MandateShield Advisory intelligence API
MandateShield Analysis only API
MandateShield Deployment activation proofs API
MandateShield Deployment Proofs API
MandateShield Execution Authorizations API
MandateShield Execution evidence API
MandateShield Execution Permits API
MandateShield Execution Receipts API
MandateShield Normalize API
Where this information came from

This is an independent, third-party profile of MandateShield Production authority 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.