Skip to main content

Mandata

OpenSSF Scorecard

The mandate toolkit for agent-initiated payments.

When AI agents hold spending authority, someone must answer: what exactly are they allowed to do — and can you prove it afterward? Mandata is a reference implementation of the bounded-autonomy mandate chain:

principal → agent → credential → transaction → evidence

The problem

Agentic payment protocols (AP2, x402, card-network agent programs) let AI agents initiate real financial transactions. But production systems lack a standard way to:

  • Express mandates — bounded permissions: amounts, payees, time windows, velocity limits
  • Bind credentials — cryptographic proof a transaction was made within mandate
  • Enforce at the gate — deterministic checks before settlement, not logs after
  • Produce evidence — an auditable chain showing every agent action against its mandate

Mandata formalizes all four as a small, dependency-light library.

Quickstart

pip install mandata
from mandata import Mandate, Bounds, enforce, settle, to_minor

# A principal grants a bounded mandate to an agent (amounts in minor units)
mandate = Mandate(
    principal="user:alice",
    agent="agent:shopping-bot",
    bounds=Bounds(
        max_amount=to_minor("500.00", "GBP"),  # 50000 pence per transaction
        currency="GBP",
        allowed_payees=["store.example"],
        expires_in_days=30,
        velocity_limit=3,  # max authorizations per day
    ),
)

# At transaction time: deterministic enforcement BEFORE settlement.
# tx_id makes retries idempotent and links the authorization to settlement.
decision = enforce(mandate, payee="store.example", amount=4999, tx_id="order-1")
assert decision.allowed  # → True (status AUTHORIZED, amount reserved)
print(decision.check)  # → "WITHIN" (normative MMF check ID)

# Submit to the rail only an instruction that binds to the approval, then settle
if decision.binds("store.example", 4999):
    ...  # rail.pay(..., idempotency_key="order-1")
    settle(mandate, "order-1")  # or void(mandate, "order-1") if it failed

Architecture

principal issues mandate ──► credential binds mandate to agent
        │                           │
        ▼                           ▼
  agent proposes transaction ──► mandate gate (enforce())
        │                           │
        ▼                           ▼
   allowed? ──► yes: execute    no: reject
        │                           │
        └───────► evidence record appended (hash-chained audit log)

See docs/architecture.md for the full model, docs/mandate-model.md for the schema, and docs/diagrams.md for the system design diagrams.

Roadmap

  • v0.1 — Mandate model, bounds enforcement, evidence chain (Python)
  • Credential signing (Ed25519) + verification API
  • Revocation registry (mandate kill-switch at transaction speed)
  • AP2 / x402 / LangChain adapter layer
  • Multi-hop delegation (agent → sub-agent mandate weakening)
  • v0.3 — MMF-v0.2: credential-bound gate, chain-wide delegation enforcement, fail-closed registry, canonical evidence hashing, 43 conformance vectors
  • v0.4 — MMF-v0.3: integer minor-unit amounts, tx_id idempotency, authorize/settle/void lifecycle, payee binding in adapters, gate-signed evidence, cross-process serializable SQLite store, 58 conformance vectors
  • TypeScript implementation (core gate scaffold only — not yet MMF-v0.3 conformant)

Research

This project is the open-source implementation arm of the survey:

Agentic AI in Payments and Financial Transactions: A Survey of Architectures, Safeguards and Open Problems — S.C. Aji, 2026. doi:10.13140/RG.2.2.13674.89288

Contributing

We welcome contributors — see CONTRIBUTING.md. Good entry points are labelled good first issue.

License

Apache-2.0 — see LICENSE.

Demo app

examples/demo_app.py runs a full simulated deployment over real HTTP — a revocation-registry service, a mock payment rail, and an agent whose every proposed payment goes through the gate: signed credentials, sub-agent delegation, x402 intake, compromise attempts, remote revocation, then a full evidence-chain audit. python examples/demo_app.py — stdlib only.

For a shorter single-process walkthrough see examples/end_to_end.py.

Metadata

Release files for mandata 0.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mandata 0.4.0
File Size Uploaded Provenance Actions
mandata-0.4.0.tar.gz 36.8 kB With provenance Details for mandata-0.4.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for mandata 0.4.0
File Interpreter ABI Platform Actions
mandata-0.4.0-py3-none-any.whl Python 3 none any Details for mandata-0.4.0-py3-none-any.whl

Total release size: 67.8 kB

Release files / mandata-0.4.0.tar.gz

Download URL mandata-0.4.0.tar.gz
Size 36.8 kB
Tags Source
SHA-256 checksum
How to use checksums
bbac3720b95a3d9ce127170b22dcd1509fb4afbc8724eaa51d27c01ce0ed844f
BLAKE2b-256 checksum
How to use checksums
8ed70204b93a84d12bc18f82c2ed5947f0e89545400620fec12a19136383b9e9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 15, 2026.

Transparency log

Release files / mandata-0.4.0-py3-none-any.whl

Download URL mandata-0.4.0-py3-none-any.whl
Size 31.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d1cd6987efab0304aee0c42e8da34a8807f6c3d1dea5b1eadcf12260712d4e5e
BLAKE2b-256 checksum
How to use checksums
5b001aa6caf4da3b6794e5cb7509f4a5da3a9360e3ef414c7928c1bc98458c68
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 15, 2026.

Transparency log

Security for mandata 0.4.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for mandata-0.4.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 15, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page