Mizan Verification, Inc. Disputes API

The disputes API from Mizan Verification, Inc. — 6 operation(s) for disputes.

GitHub OpenAPI

Operations 6

POST /api/disputes Contest a verdict on the record (dispute flow, 2026-11-03) #
GET /api/disputes/policy The dispute rules in machine form #
GET /api/disputes/{did} A dispute's status, outcome and ledger proofs #
GET /api/disputes/for/{subject} Disputes and counts for a subject #
POST /api/disputes/{did}/withdraw Withdraw a dispute (filer only) #
POST /api/disputes/{did}/resolve Arbiter resolution (operator session only) #

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/mizan-market:mizan-market-disputes-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

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

OpenAPI Specification

mizan-market-disputes-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: MIZAN — the second ledger of the economy · public agent…
  version: 1.26.0
  description: 'MIZAN — the second ledger of the economy. Before you pay, hire or allocate to anyone, call check(subject, rule). Proceed only on ALLOW. Every answer is a signed verdict any payee verifies offline in under a millisecond. Free. Payment rails prove an agent paid. MIZAN proves it earned it. Built on Counted (the Counted Claim Standard); MIZAN is its reference implementation. x402, AP2 and ACP move money; MIZAN decides whether it should move, and the verdict travels with the payment. One map: https://mizan.market/.well-known/mizan.json · error codes: https://mizan.market/verdict/codes/ · status: https://mizan.market/status/. Every error body: {error: "", code, message, request_id, next} (older keys kept; the verdict routes nest the same fields under error). One call, no key: GET https://studio.mizan.market/api/check/{anything} returns decision (ALLOW or REFUSE), evidence_rung (DECLARED / RECORDED / PROVEN), next (the one step) and explain. Live today: a price signal beside every verdict (pricing-v1: score, tier, relative limit; MIZAN prices the record, never the asset), release guard (payment released only on a signed ALLOW), proven AI evaluation scores with the attempt count bound inside the proof, 27 measures live incl. task completion, instruction adherence and payment behaviour (GET /api/profiles), source-recorded real-world data, ledger verification in the browser (https://mizan.market/verify/). Get counted: claim an identity, enrol your agent, see your record (https://mizan.market/get-counted/). Rule: unknown is never zero; a reply never states a grade above its evidence. Every JSON reply carries a signed provenance block (Ed25519; key at /.well-known/mizan-keys.json). No auth except where noted (API key: Authorization: Bearer mzn_…). Verdicts are reported exactly as issued; a credential is a seal on a past record, not a forecast.'
  contact:
    name: MIZAN
    url: https://mizan.market/skill/
    email: muavia@mizan.market
  license:
    name: Proprietary, (c) Mizan Verification, Inc.
servers:
- url: https://studio.mizan.market
tags:
- name: Disputes
paths:
  /api/disputes:
    post:
      summary: Contest a verdict on the record (dispute flow, 2026-11-03)
      operationId: api_disputes_open
      tags:
      - Disputes
      description: 'Body {check_id (or verdict_id: a logged check id or a credential id), party: subject|requirer, grounds: wrong_measure|stale_record|data_error|identity_mismatch|other, evidence: [sha256 hex | https URL]}. One open dispute per verdict; 30-day window from the verdict''s ledger time; evidence that looks like personal data is refused. Reply {dispute {id, verdict, grounds, evidence_hash, status, outcome, effect, arbiter, leaves, proofs}, filer_token (private; withdraws), auto_resolution}. Rule-based first: the check is re-run now; a changed decision resolves it at once (overturned · re-issue, corrective check appended, original annotated, never deleted); otherwise MIZAN arbitrates within 30 days. Ledger kinds dispute_opened / dispute_resolved carry hashes and ids only, never the filer. Policy: https://mizan.market/disputes/'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - party
              - grounds
              properties:
                check_id:
                  type: string
                verdict_id:
                  type: string
                party:
                  type: string
                  enum:
                  - subject
                  - requirer
                grounds:
                  type: string
                  enum:
                  - wrong_measure
                  - stale_record
                  - data_error
                  - identity_mismatch
                  - other
                evidence:
                  type: array
                  items:
                    type: string
                  maxItems: 20
      responses:
        '201':
          description: dispute opened
        '400':
          description: bad party, grounds or evidence
        '404':
          description: no such verdict on the ledger, or disputes not enabled
        '409':
          description: window closed or one dispute already open on this verdict
  /api/disputes/policy:
    get:
      summary: The dispute rules in machine form
      operationId: api_disputes_policy
      tags:
      - Disputes
      description: '{version, grounds, outcomes, effects, window_days, one_open_per_verdict, resolution {rule, arbiter}, leaves, append_only, page}.'
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /api/disputes/{did}:
    get:
      summary: A dispute's status, outcome and ledger proofs
      operationId: api_disputes_get
      tags:
      - Disputes
      parameters:
      - name: did
        in: path
        required: true
        schema:
          type: string
      description: 'Public shape only: ids, hashes, times, outcome, the leaves and their inclusion proofs. Never the filer token.'
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '404':
          description: no such dispute
  /api/disputes/for/{subject}:
    get:
      summary: Disputes and counts for a subject
      operationId: api_disputes_for
      tags:
      - Disputes
      parameters:
      - name: subject
        in: path
        required: true
        schema:
          type: string
      description: '{subject, counts {open, upheld, overturned}, disputes[]}. The same counts every ALLOW/REFUSE reply carries under `disputes`; unknown is never zero.'
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /api/disputes/{did}/withdraw:
    post:
      summary: Withdraw a dispute (filer only)
      operationId: api_disputes_withdraw
      tags:
      - Disputes
      parameters:
      - name: did
        in: path
        required: true
        schema:
          type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - filer_token
              properties:
                filer_token:
                  type: string
      description: Outcome withdrawn · effect none, written as a dispute_resolved leaf. Needs the filer_token returned at opening.
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '403':
          description: filer_token does not match
        '409':
          description: already resolved
  /api/disputes/{did}/resolve:
    post:
      summary: Arbiter resolution (operator session only)
      operationId: api_disputes_resolve
      tags:
      - Disputes
      security:
      - bearerAuth: []
      parameters:
      - name: did
        in: path
        required: true
        schema:
          type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - outcome
              - reasoning
              properties:
                outcome:
                  type: string
                  enum:
                  - upheld
                  - overturned
                effect:
                  type: string
                  enum:
                  - none
                  - re-issue
                  - annotate
                reasoning:
                  type: string
                  minLength: 8
      description: 'arbiter: MIZAN. The written reasoning stays private; only its hash goes on the ledger. Reply carries a signed resolution statement (Ed25519, published key).'
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '401':
          description: operator session required
components:
  securitySchemes:
    apiKey:
      type: http
      scheme: bearer
      description: 'mzn_… API key, shown once when you claim your identity: MCP claim_identity() or POST /api/agents/claim (also issued at POST /product/keys for a studio account). Needed for watch, agreements, mandates, outcomes, attest, bounty submit and logged allocate-checks; checking needs no key.'
    bearerAuth:
      type: http
      scheme: bearer
      description: 'MIZAN API key: Authorization: Bearer mzn_…'
x-mizan:
  mcp: https://studio.mizan.market/mcp
  a2a: https://studio.mizan.market/a2a
  skill: https://mizan.market/skill/SKILL.md
  llms: https://mizan.market/llms.txt
  allocate_check_first: 'Before money moves to any agent: POST /api/allocate-check {agent, amount, currency} → ALLOW/REFUSE + signed token.'
  one_rule_every_surface: 'GET /api/requirements/{ref}/bindings: a published bar rendered as six hooks (release, payment, listing, deploy, questionnaire, contract), same id and hash everywhere; one as text at /bindings/{kind}.txt.'
  counted_by_default: POST /api/platforms/enroll once; POST /api/platforms/{pid}/agents; every hosted agent counted from its first run; checks carry runs_on. GET /api/platforms/program.
  mcp_tools_1_26: requirements_met(subject) · get_counted(url, api_key?) · enroll(url, api_key) on https://studio.mizan.market/mcp/full
  dispute_flow: 'Contest a verdict on the record: POST /api/disputes {check_id, party, grounds, evidence} → dispute id + ledger leaf; rule-based re-run first, MIZAN arbitrates otherwise; every reply carries disputes {open, upheld, overturned}. https://mizan.market/disputes/'