Mizan Verification, Inc. Allocate Check API
The Allocate Check API from Mizan Verification, Inc. — 4 operation(s) for allocate check.
The Allocate Check API from Mizan Verification, Inc. — 4 operation(s) for allocate check.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/mizan-market:mizan-market-allocate-check-api"
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.
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: 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: Allocate Check
paths:
/api/allocate-check/verify:
post:
summary: Api Verify
operationId: api_verify_api_allocate_check_verify_post
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- Allocate Check
/api/allocate-check:
post:
summary: Api Allocate Check
operationId: api_allocate_check_api_allocate_check_post
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
agent:
type: string
description: credential id, alias, wallet, ERC-8004 id, agent-card URL or registry id (ag_…)
credential:
type: string
receipt:
type: string
description: signed receipt JWS; subject taken from it
amount:
type: number
currency:
type: string
default: USD
purpose:
type: string
allow_not_significant:
type: boolean
default: false
require_forward:
type: boolean
default: false
policy:
type: object
description: 'inline venue policy: min_record_days, min_trades, require_forward, min_provenance_grade, min_forward_commitments, allow_not_significant'
policy_id:
type: string
description: a policy registered via POST /api/venues/policy; unknown id → REFUSE
record:
type: boolean
default: false
description: 'with an API key: log the check as a public leaf'
description: 'The one call before money moves (Agent profile §06). Body: {agent|credential|receipt, amount?, currency?, purpose?, require_forward?, allow_not_significant?, record?}. Returns decision ALLOW/REFUSE, reasons[], checks[] (clause A-26..A-31), verdict_object, token (EdDSA 24 h), check_id. Fail closed.'
tags:
- Allocate Check
/api/allocate-check/program:
get:
summary: Api Program
operationId: api_program_api_allocate_check_program_get
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- Allocate Check
/api/allocate-check/{subject}:
get:
summary: Api Allocate Check Get
operationId: api_allocate_check_get_api_allocate_check__subject__get
parameters:
- name: subject
in: path
required: true
schema:
type: string
title: Subject
- name: allow_not_significant
in: query
required: false
schema:
type: boolean
default: false
title: Allow Not Significant
- name: require_forward
in: query
required: false
schema:
type: boolean
default: false
title: Require Forward
- name: policy_id
in: query
required: false
schema:
type: string
default: ''
title: Policy Id
- name: requirement
in: query
required: false
schema:
type: string
default: ''
title: Requirement
description: 'req_<id>@<version>: answer this published rule clause by clause. The reply then carries `requirement` {id, version, hash} and `contract_message` {message, canonical, signature, alg, public_key, verify}: the code-checkable verdict (seven fields, Ed25519, verifies offline). Add requirement_hash=<hash> to pin the exact published version.'
- name: requirement_hash
in: query
required: false
schema:
type: string
default: ''
description: pins the published hash of the requirement; the reply's requirement.hash must equal it
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
description: Every ALLOW / REFUSE reply also carries `required_by` {count, public, since} (distinct requirers whose published bar this subject meets now by the record of real checks; names only where the requirer opted in; null + unknown_reason when unknown, never zero) and, for an agent hosted by an enrolled platform, `runs_on` {platform, counted_since, rung, name when the platform opted in public}. With ?requirement= the reply carries `contract_message`, the signed code-checkable verdict.
tags:
- Allocate Check
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/'