Mizan Verification, Inc. Requirements API

The Requirements API from Mizan Verification, Inc. — 8 operation(s) for requirements.

GitHub OpenAPI

Operations 9

POST /api/requirements/compile Api Compile #
POST /api/requirements Api Publish #
GET /api/requirements Api List #
GET /api/requirements/{ref} Api Get #
POST /api/requirements/{rid}/fork Api Fork #
GET /api/requirements/met-by/{subject} Api Met By #
GET /api/requirements/{ref}/meeting Api Meeting #
GET /api/requirements/{ref}/bindings One rule, every surface: all seven bindings #
GET /api/requirements/{ref}/bindings/{kind} One binding, as copy-ready text or JSON #

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-requirements-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-requirements-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: Requirements
paths:
  /api/requirements/compile:
    post:
      summary: Api Compile
      operationId: api_compile_api_requirements_compile_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                text:
                  type: string
                  description: your bar in plain words, e.g. 'a forward performance record of at least 90 days, PROVEN, with no single bar losing more than 12%'
              required:
              - text
      tags:
      - Requirements
  /api/requirements:
    post:
      summary: Api Publish
      operationId: api_publish_api_requirements_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - Requirements
    get:
      summary: Api List
      operationId: api_list_api_requirements_get
      parameters:
      - name: q
        in: query
        required: false
        schema:
          type: string
          default: ''
          title: Q
      - name: limit
        in: query
        required: false
        schema:
          type: integer
          default: 50
          title: Limit
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Requirements
  /api/requirements/{ref}:
    get:
      summary: Api Get
      operationId: api_get_api_requirements__ref__get
      parameters:
      - name: ref
        in: path
        required: true
        schema:
          type: string
          title: Ref
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Requirements
  /api/requirements/{rid}/fork:
    post:
      summary: Api Fork
      operationId: api_fork_api_requirements__rid__fork_post
      parameters:
      - name: rid
        in: path
        required: true
        schema:
          type: string
          title: Rid
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Requirements
  /api/requirements/met-by/{subject}:
    get:
      summary: Api Met By
      operationId: api_met_by_api_requirements_met_by__subject__get
      parameters:
      - name: subject
        in: path
        required: true
        schema:
          type: string
          title: Subject
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Requirements
  /api/requirements/{ref}/meeting:
    get:
      summary: Api Meeting
      operationId: api_meeting_api_requirements__ref__meeting_get
      parameters:
      - name: ref
        in: path
        required: true
        schema:
          type: string
          title: Ref
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Requirements
  /api/requirements/{ref}/bindings:
    get:
      summary: 'One rule, every surface: all seven bindings'
      operationId: api_bindings
      tags:
      - Requirements
      parameters:
      - name: ref
        in: path
        required: true
        schema:
          type: string
        description: req_<id>@<version>
      description: 'A published rule rendered as the seven hooks a requirer can put it behind: release (payment hold pinned to the rule, released on a live ALLOW; curl/python/javascript), payment (x402 accepts[i].extra.mizan {requirement, requirement_hash, check}), listing (venue policy {require, requirement_hash, on: listing, action: hide_until_allow} + one GET per candidate), deploy (MIZAN_REQUIRE=req_…@v#hash read by the SDKs'' auto()), questionnaire (a plain-words clause with the verify URL), contract (a code-checkable verdict: seven fields, Ed25519 over canonical JSON, verified offline with /.well-known/mizan-keys.json). Every binding carries the SAME rule id and the SAME published hash; a check at any hook settles the same immutable version. Also inlined as `bindings` on GET /api/requirements/{ref}. Reply: {requirement, hash, name, same_rule_everywhere, release, payment, listing, deploy, questionnaire, contract, raw}. No key; a private rule is visible only to its author.'
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '404':
          description: no such requirement
  /api/requirements/{ref}/bindings/{kind}:
    get:
      summary: One binding, as copy-ready text or JSON
      operationId: api_binding_text
      tags:
      - Requirements
      parameters:
      - name: ref
        in: path
        required: true
        schema:
          type: string
        description: req_<id>@<version>
      - name: kind
        in: path
        required: true
        schema:
          type: string
          enum:
          - release.txt
          - payment.txt
          - listing.txt
          - deploy.txt
          - questionnaire.txt
          - contract.txt
          - release
          - payment
          - listing
          - deploy
          - questionnaire
          - contract
          - reliance.txt
          - reliance
        description: with .txt the binding's text (text/plain); without it the same binding as JSON
      description: 'Seven kinds: release, payment, listing, deploy, questionnaire, contract, reliance. `.txt` returns the text field as text/plain for copy; `` returns the full JSON binding.'
      responses:
        '200':
          description: Successful Response
          content:
            text/plain:
              schema:
                type: string
            application/json:
              schema: {}
        '404':
          description: no such requirement, or no such binding (the reply lists the six kinds)
components:
  schemas:
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
  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/'