ENFORCEMENT FOR THE AGENTIC ECONOMY

Agents can pay.
Mandates decide.

The contract-enforced authorization layer for AI agents using x402.SEE THE CONTRACT DECIDE →
USER-DEFINED AUTHORITYSTELLAR SETTLEMENTPAYMENT + POLICY EVIDENCE

WHY ACKRATE

An agent can request a payment.
It cannot approve its own request.

Ackrate moves spending authority out of agent software and into a live, user-defined mandate enforced by the contract.

HOW ACKRATE WORKS

One path from human intent
to enforced action.

Scroll the full authority lifecycle. Select any stage to inspect what the protocol enforces.

01USER MANDATES

A human defines the authority.

The user signs who may act, which merchant may receive value, the permitted asset, budget, expiry, and next sequence.

02REGISTRY

The mandate stays live.

MandateRegistry holds the source of truth: current status, budget already consumed, expiry, and sequence.

03AGENT ACTION

The agent proposes. It never approves.

Every money-moving action must carry a live mandate. An action without a mandate has no authority.

04EXECUTION

The request reaches the boundary.

The proposed action and mandate enter one contract-authoritative execution path before settlement begins.

05ENFORCEMENT

The contract checks every constraint.

MandateRegistry re-checks the live rules at execution. One failed condition rejects the entire payment.

06PAYMENT + RECEIPT

Settlement resolves with evidence.

A valid request consumes budget and sequence before atomic SEP-41 settlement. The result is recorded for reconciliation.
REQUEST RESOLVEDThe contract decides whether money moves.

ONE AUTHORITATIVE BOUNDARY

Simple at every surface.
Strict where it matters.

01

Enforcement layer

MandateRegistry validates identity, merchant, asset, amount, budget, expiry, status, and sequence before atomic settlement.

execute_payment
02

SDK

The TypeScript SDK prepares the exact x402 request and carries settlement proof. It is useful—and deliberately untrusted.

agent.fetch()
03

CLI

Create mandates, inspect live state, journal evidence before broadcast, and reconcile safely before retry.

ackrate mandate
04

Marketplace

A mandate-gated catalog helps agents discover approved services without inventing payment terms or new authority.

approved scope

THE SECURITY INVARIANT

Compromise the agent.
The limit still holds.

The allowance belongs to MandateRegistry—not the agent, SDK, or CLI.

Wrong merchant. Wrong asset. Expired mandate. Overspend. Replay.

ZERO VALUE MOVED.

ACKRATE

Agents propose.
Mandates decide.

Explore the protocol ↗