MandateShield · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Mandateshield Com Public proof network API

6 actions 6 updates phrasing extends openapi/mandateshield-com-public-proof-network-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 6

$.info
$.paths['/api/v1/proof-network/challenges'].post
$.paths['/api/v1/proof-network/attestations'].post
$.paths['/api/v1/proof-network/proofs'].get
$.paths['/api/v1/proof-network/proofs/{proofId}'].get
$.paths['/api/v1/proof-network/proofs/{proofId}/badge.svg'].get

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 Public proof network API
  version: 1.0.0
extends: openapi/mandateshield-com-public-proof-network-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: 5
- target: $.paths['/api/v1/proof-network/challenges'].post
  update:
    x-apievangelist-phrasing:
      intent: Create a subject-binding proof challenge
      effect: write
      questions:
      - How do I get a DNS TXT or GitHub commit challenge to bind my conformance self-report to my domain?
      - Does MandateShield run my implementation when I submit a conformance report?
      - How long is a proof network binding challenge valid?
      instructions:
      - text: Create a proof network binding challenge for subject {subject} with conformance report {report}.
        slots:
          subject: requestBody.subject
          report: requestBody.report
      - text: Start a self-report binding for my domain {subject} using report {report}.
        slots:
          subject: requestBody.subject
          report: requestBody.report
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/v1/proof-network/attestations'].post
  update:
    x-apievangelist-phrasing:
      intent: Bind and sign a self-report attestation
      effect: write
      questions:
      - Once my DNS TXT record or GitHub binding is in place, how do I get the signed self-report attestation?
      - What terms do I have to accept before a proof attestation is published?
      - When is a repository commit required for issuing an attestation?
      instructions:
      - text: Issue the attestation for challenge {challenge_token}, accepting publisher terms {publisher_terms_accepted}.
        slots:
          challenge_token: requestBody.challenge_token
          publisher_terms_accepted: requestBody.publisher_terms_accepted
      - text: Bind challenge {challenge_token} to GitHub commit {repository_commit} with publisher terms accepted {publisher_terms_accepted}.
        slots:
          challenge_token: requestBody.challenge_token
          repository_commit: requestBody.repository_commit
          publisher_terms_accepted: requestBody.publisher_terms_accepted
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/v1/proof-network/proofs'].get
  update:
    x-apievangelist-phrasing:
      intent: List published self-report proofs
      effect: read
      questions:
      - Which externally bound self-report proofs have been published?
      - Are sandbox runs or telemetry included in the public proof list?
      instructions:
      - text: List the published proof network self-reports.
      - text: Show {limit} externally bound self-report summaries.
        slots:
          limit: query.limit
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/v1/proof-network/proofs/{proofId}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get one signed self-report proof
      effect: read
      questions:
      - Can I see the full claimant report and subject binding behind a published proof?
      - What caveats come with a single externally bound self-report?
      instructions:
      - text: Get the full signed self-report for proof {proofId}.
        slots:
          proofId: path.proofId
      - text: Show the subject binding and claimant report of proof network entry {proofId}.
        slots:
          proofId: path.proofId
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/v1/proof-network/proofs/{proofId}/badge.svg'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a self-report proof badge
      effect: read
      questions:
      - How do I embed an externally bound self-report badge on my site?
      - Is the self-report badge a certification or audit mark?
      instructions:
      - text: Fetch the self-report SVG badge for proof {proofId}.
        slots:
          proofId: path.proofId
      - text: Get the externally bound self-report badge image for {proofId}.
        slots:
          proofId: path.proofId
      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-public-proof-network-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.