Skip to content
Enterprise

Governance for
autonomous agent spending

Your agents make thousands of micropayments autonomously. Enterprise gives you policy controls, approval workflows, real-time analytics, and emergency kill switches — without slowing agents down.


Agents spend money. Who watches the agents?

Autonomous AI agents with wallet access can execute thousands of transactions per hour. Without governance, a misconfigured agent or prompt injection attack can drain budgets in minutes. Enterprise solves this.

Runaway spending

An agent in a loop can burn through USDC in seconds. You need per-transaction caps, daily budgets, and automatic circuit breakers.

Multi-agent chaos

Ten agents, five teams, three cost centers. Without role-based controls and per-agent policies, there's no accountability.

Zero visibility

On-chain transactions are public, but without indexed analytics you can't answer "which agent spent the most this week?" in real time.


Policy Engine

Define rules. Enforce them in real time. Every payment is evaluated against your policy before it executes — no exceptions.

policy.yaml
# Example policy: limit agent spending
rules:
  - name: "per-tx-cap"
    condition: "payment.amount > 10.00"
    action: "queue_for_approval"

  - name: "daily-budget"
    condition: "agent.daily_spend > 500.00"
    action: "block"

  - name: "merchant-allowlist"
    condition: "merchant not in allowlist"
    action: "block"

  - name: "token-restriction"
    condition: "payment.token != 'USDC'"
    action: "block"

Per-transaction limits

Set maximum amounts per payment. Anything over the threshold auto-routes to an approval queue or gets blocked outright.

Rolling budgets

Daily, weekly, and monthly spending caps per agent, per team, or organization-wide. Budgets reset on your schedule.

Merchant allowlists

Restrict agents to approved merchants only. Wildcard patterns and category-based rules supported.

Token and chain restrictions

Lock agents to specific tokens (e.g., USDC only) and specific chains (e.g., Base only). No surprises.

Time-of-day rules

Block payments outside business hours, or require approval for weekend transactions. Timezone-aware.


Approval Workflows

When a payment exceeds policy thresholds, it enters a review queue. Designated approvers get notified, review context, and decide — all without blocking the agent's other operations.

Multi-level approvals

Single approver for routine payments, multi-level chains for high-value transactions. Escalation rules with configurable timeouts.

Real-time notifications

Slack, email, webhook, or in-dashboard alerts. Approvers see the full context: agent ID, merchant, amount, policy that triggered the queue.

Timeout policies

If no one approves within the SLA, auto-escalate, auto-approve (for low-risk), or auto-deny. No payments stuck in limbo.

Audit trail

Every approval, rejection, and modification is logged with timestamp, approver ID, and rationale. Full compliance readiness.

Mobile approvals

Approve or reject from any device. The review interface shows payment context, policy details, and agent history at a glance.

Conditional routing

Route approvals based on amount, merchant category, or agent risk score. Low-risk payments skip the queue entirely.


Analytics Dashboard

Real-time visibility into every payment across all agents, teams, and merchants. Drill down from organization-wide trends to individual transactions.

$12,847 Total spend (7d) +8.2%
24,391 Transactions (7d) +12.5%
$0.53 Avg transaction -3.1%
99.7% Success rate +0.1%

Spend breakdown

Slice by agent, team, merchant, token, chain, or time period. Exportable reports for finance and compliance teams.

Anomaly detection

Automatic alerts when spending patterns deviate from baselines. Catch runaway agents before they become expensive.

CSV and API export

Pull analytics data via API or download CSV reports. Integrate with your existing BI tools and accounting systems.


Team and Agent Management

Register agents, organize into teams, assign policies, and control access — all from a single dashboard.

Agent registry

Register each agent with a name, wallet address, team assignment, and policy binding. Track agent health and payment history.

Team hierarchy

Organize agents into teams and departments. Policies cascade from organization to team to agent, with overrides at each level.

Role-based access

Admin, Manager, Viewer, and Approver roles with granular permissions. SSO and SCIM provisioning on Enterprise plans.


Emergency Controls

When something goes wrong, you need to act in seconds — not minutes. Emergency controls give you instant override capabilities.

Global kill switch

One click halts all agent payments across the organization. Instantly. No payments process until you re-enable.

Per-agent freeze

Freeze individual agents without affecting others. Useful when one agent behaves anomalously while the rest operate normally.

Circuit breakers

Automatic triggers when spending velocity exceeds thresholds. The system halts payments and alerts admins before damage accumulates.

Incident log

Every emergency action is timestamped and attributed. Full incident timeline for post-mortems and compliance reporting.


Scale as you grow

Start free. Add governance when your agents handle real money.

Free
0.25% routing fee
  • Core routing (quote + fulfill)
  • Searchable receipts
  • Discovery index access
  • Single agent
  • Basic spending alerts
  • Community support
Get Started
Enterprise
Custom (0.10–0.15%)
  • Everything in Growth
  • Unlimited agents and teams
  • Emergency controls + kill switch
  • SSO / SCIM provisioning
  • Custom SLAs
  • Dedicated account manager
  • On-prem deployment option
Contact Sales

Common questions

What is a policy engine for AI agent payments?

A policy engine enforces spending rules on autonomous AI agents before payments execute. It evaluates conditions like per-transaction limits, daily budgets, approved merchants, and token restrictions — then auto-approves, queues for review, or blocks the payment in real time. Think of it as a firewall for agent spending.

How do approval workflows work for agent payments?

When an agent payment exceeds policy thresholds, it enters an approval queue. Designated reviewers receive notifications via Slack, email, or webhook and can approve, reject, or modify the payment. Multi-level approval chains support escalation for high-value transactions. Timeout policies ensure no payment gets stuck indefinitely.

Can I set spending limits for individual AI agents?

Yes. The policy engine supports per-agent, per-team, and organization-wide spending limits. You can set per-transaction caps, daily/weekly/monthly budgets, and restrict which merchants or token types each agent can use. Policies cascade from org to team to agent level, with overrides at each tier.

What happens during an emergency with autonomous agent spending?

Emergency controls include a global kill switch that halts all agent payments instantly, per-agent freeze capabilities, and automatic circuit breakers that trigger when anomalous spending patterns are detected. Every emergency action is logged with full attribution for post-incident review.

Is Agent First API non-custodial even at the enterprise tier?

Yes. Agent First API never holds or controls your funds at any tier. Payments always route directly from agent wallet to merchant wallet on-chain. Enterprise features add governance and visibility layers around the routing — they don't change the non-custodial architecture.

How does the off-chain billing model work?

Routing fees are collected off-chain via USDC prepaid credits. You purchase credits in advance (non-refundable), and fees are deducted from your balance as payments route. Auto-top-up is available to prevent service interruption. This keeps the on-chain payment flow clean — only merchant payments go on-chain.


Ready to govern your agents?

Start with the free tier. Add enterprise governance when your agents handle real volume. No long-term contracts.

Contact Sales View Core API