MandateShield · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Mandateshield Com Production authority API

5 actions 5 updates phrasing extends openapi/mandateshield-com-production-authority-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for MandateShield's API. It is a proposal applied on top of the contract, not a document MandateShield publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 5

$.info
$.paths['/api/v2/challenges'].post
$.paths['/api/v2/verify'].post
$.paths['/api/v2/execution-authorizations'].post
$.paths['/api/v2/batch'].post

OpenAPI Overlay

Raw ↑
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Mandateshield Com Production authority API
  version: 1.0.0
extends: openapi/mandateshield-com-production-authority-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 4
- target: $.paths['/api/v2/challenges'].post
  update:
    x-apievangelist-phrasing:
      intent: Issue a one-time challenge for a mandate
      effect: write
      questions:
      - How do I get a fresh one-time nonce before signing purchase authority for a mandate?
      - How long does a verification challenge last, and can it be reused?
      - What does a challenge require, like a live key and a pinned payment-authority key?
      instructions:
      - text: Issue a verification challenge for mandate {mandate_id} over {protocol} using key thumbprint {key_thumbprint}.
        slots:
          mandate_id: requestBody.mandate_id
          protocol: requestBody.protocol
          key_thumbprint: requestBody.key_thumbprint
      - text: Create a one-time nonce for mandate {mandate_id} bound to pinned key {key_thumbprint}.
        slots:
          mandate_id: requestBody.mandate_id
          key_thumbprint: requestBody.key_thumbprint
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/v2/verify'].post
  update:
    x-apievangelist-phrasing:
      intent: Verify signed purchase authority and get a receipt
      effect: write
      questions:
      - How do I verify that an agent's signed purchase is authorized under a registered mandate?
      - Which evidence formats are accepted, like JWS, AP2 SD-JWT or TAP-style signatures?
      - Does a live ALLOW from strict verification let me submit the payment directly?
      instructions:
      - text: Verify purchase envelope {envelope} with signed evidence {evidence} and issue a receipt.
        slots:
          envelope: requestBody.envelope
          evidence: requestBody.evidence
      - text: Run strict v2 authority verification on {evidence} for this single purchase {envelope}.
        slots:
          evidence: requestBody.evidence
          envelope: requestBody.envelope
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/v2/execution-authorizations'].post
  update:
    x-apievangelist-phrasing:
      intent: Consume, commit, release or expire an authorization
      effect: write
      questions:
      - How does my processor consume a reserved authorization and get an execution permit?
      - Can I still commit or release an authorization while account execution is paused?
      - What does a new account need to supply for CONSUME, like a provider binding?
      instructions:
      - text: '{action} the reserved authorization {compact} for audience {expected_audience} and envelope {expected_envelope}, idempotency key {idempotency_key}.'
        slots:
          action: requestBody.action
          compact: requestBody.compact
          expected_audience: requestBody.expected_audience
          expected_envelope: requestBody.expected_envelope
          idempotency_key: requestBody.idempotency_key
      - text: Consume authorization {compact} with provider binding {provider_binding} to obtain an execution permit.
        slots:
          compact: requestBody.compact
          provider_binding: requestBody.provider_binding
      - text: Release reserved budget for authorization {compact}.
        slots:
          compact: requestBody.compact
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/v2/batch'].post
  update:
    x-apievangelist-phrasing:
      intent: Verify up to 25 purchase authorities at once
      effect: write
      questions:
      - Can I run strict signed-authority verification on many purchases in one call?
      - Does each item in a strict verification batch need its own challenge and idempotency key?
      - Does a successful HTTP response authorize the whole batch?
      instructions:
      - text: Verify this batch of signed purchase authorities with the strict v2 verifier.
      - text: Run strict authority verification for up to 25 distinct purchases together.
      method: generated
      generated: '2026-09-26'

Work with this as data

Every overlay 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 openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay in the catalog.
  • 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 overlay
curl "https://apis.io/api/v1/overlays/mandateshield-com-production-authority-api-phrasing-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?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.