AINumbers.co Payment Mandate API
The payment_mandate API from AINumbers.co — 1 operation(s) for payment_mandate.
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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/ainumbers-co:ainumbers-co-payment-mandate-api"
All apis
curl "https://apis.io/api/v1/apis?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.
OpenAPI Specification
openapi: 3.2.0
info:
title: AINumbers.co Fintech Intelligence Suite Payment Mandate API
version: 1.0.0
description: '**1255 fintech intelligence tools** covering ISO 20022, A2A payments, CFPB §1033, EU AI Act, DORA, MiCA, AML/KYC, BaaS, DLT/tokenization, ESG/climate finance, agentic payments (AP2, ACP, x402, Visa TAP, Mastercard Agent Pay), PQC migration, sanctions screening, and OpenChainGraph v0.4 computation chains.
## Transport
> **The live transport is MCP JSON-RPC 2.0 at `https://mcp.ainumbers.co/mcp` — not REST.**
>
> This OpenAPI file is a **descriptive data-room artifact** — a machine-readable index of all tools and their input/output schemas. The REST paths (`POST /v1/tools/{name}`) described here are a projection; they become functional only if the optional REST shim (Area 2 Path B) is deployed.
>
> To call tools today, connect via the official MCP client SDKs. TypeScript: `@modelcontextprotocol/sdk`. Python: `mcp`.
## Architecture
All tools run **entirely client-side** (browser JavaScript). Zero PII. Zero server calls after page load. Deterministic, reproducible outputs. Licensed CC BY 4.0.
OpenChainGraph v0.4 compute-binding nodes additionally run **server-side on the MCP Worker** and emit verifiable artifacts with `execution_hash` (WebCrypto SHA-256 over RFC 8785 canonical JSON).'
contact:
name: Post Oak Labs
url: https://postoaklabs.com
email: tim@postoaklabs.com
license:
name: CC BY 4.0
url: https://creativecommons.org/licenses/by/4.0/
servers:
- url: https://ainumbers.co
description: Static browser-based tool host (DreamHost). Tools run client-side — no REST gateway is active on this origin. See x-mcp for the live MCP endpoint.
tags:
- name: payment_mandate
paths:
/v1/tools/authorize_payment_against_mandate:
post:
operationId: authorize_payment_against_mandate
summary: Mandate Authorization Gate
description: 'Automated payment approval gate with no human step: a fixed ten-rule mandate check lists every failing rule with a named reason, issues a one-use authorization bound to the exact request digest with a window clipped to the mandate expiry, and re-verifies the committed request at commit time. Integer minor units, no float anywhere.
**Tool URL:** https://ainumbers.co/chaingraph/art-703-mandate-authorization-gate.html
**AP2/Policy Mandate export:** yes'
tags:
- payment_mandate
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- mode
- as_of
properties:
mode:
type: string
description: authorize evaluates the mandate and request; verify_commit re-verifies a presented authorization.
as_of:
type: string
description: Decision time as a UTC timestamp, YYYY-MM-DDTHH:MM:SS ending in Z. The node reads no clock.
ttl_seconds:
type: integer
description: 'authorize only: window seconds, clipped into 1 to 900 and to the mandate expiry.'
mandate:
type: object
description: 'authorize only: the mandate drawn on; commonly the canonical pivot from art-476.'
extensions:
type: object
description: 'authorize only, optional: revoked_at, budget minor integers, allowed_rails, verified_payees.'
request:
type: object
description: 'authorize: the proposed payment. verify_commit: the request being committed, as presented.'
authorization:
type: object
description: 'verify_commit only: the authorization this node issued, presented back for commit.'
responses:
'200':
description: Successful tool execution result
content:
application/json:
schema:
type: object
properties:
authorization:
type:
- object
- 'null'
authorization_id:
type: string
decision:
type: string
enum:
- authorize
- commit_ok
- reject
domain_errors:
type: array
items:
type: object
properties:
code:
type: string
text:
type: string
required:
- code
- text
additionalProperties: false
mode:
type: string
enum:
- authorize
- verify_commit
primary_reason:
type:
- 'null'
- string
reasons:
type: array
items:
type: object
properties:
code:
type: string
text:
type: string
required:
- code
- text
additionalProperties: false
remaining_budget_minor:
type:
- number
- 'null'
scope_note:
type: string
required:
- decision
- domain_errors
- mode
- reasons
additionalProperties: false
x-derived-from: fixture
x-mcp-tool-name: authorize_payment_against_mandate
x-tool-url: https://ainumbers.co/chaingraph/art-703-mandate-authorization-gate.html
x-source: manifest
x-ap2-export: true
x-mcp:
transport: MCP JSON-RPC 2.0 (streamable HTTP)
endpoint: https://mcp.ainumbers.co/mcp
protocol_version: '2025-11-25'
authentication: none
registry: co.ainumbers/tools (official MCP registry)
note: Connect any MCP-compatible client (Claude, ChatGPT, custom agent) directly to this endpoint. The REST paths in this file are descriptive only — they do not exist on the live server unless the REST shim is deployed.