Agentic Finance / design vision

An agent with a wallet is easy. An agent with governed authority is the interesting problem.

Pegas explores a simple idea: once an AI agent can create financial side effects, prompts are no longer enough. Identity, authority, limits and evidence have to become first-class parts of the system.

The framework that changed the design

Lead → from agent payments to governed agentic finance

Lead's September 2026 Leading into the AI Revolution paper frames the important problem around governance questions that sit above a payment API. Pegas uses a subset of those ideas as the conceptual starting point for the prototype.

Who is acting?
On whose authority?
Within what limits?
Against which counterparties?
With what revocation path?
With what audit trail?

Pegas takes those governance questions and explores what they can look like in working software today: a known agent identity, recorded delegation, hard transaction limits, a revocation path and evidence that can be reconstructed after the fact.

Framework → prototype

From framework → working prototype

Lead frames the harder questions around identity, delegated authority, transaction constraints, revocation and auditability. Pegas takes a subset of those ideas and makes them concrete in a working software prototype.

Lead

Principal ↔ agent identity

Pegas

KYA-lite Agent Registry

Lead

Recorded delegated authority

Pegas

Agent Mandate

Lead

Granular transaction limits

Pegas

Fixed network, asset, payee, amount + deterministic AUTH controls

Lead

Authority cannot expand through an agent chain

Pegas

Effective authority is the intersection of global policy, mandate, identity, seller quote and budget controls

Lead

Revocation / suspension

Pegas

Payment kill switch + mandate lifecycle

Lead

Transaction receipts / auditability

Pegas

Agentic Payment Evidence

Lead

Reconstructable activity

Pegas

Mandate → policy → identity → x402 → settlement → chain evidence → specialist result

KYA-lite is a demo identity registry. The prototype explores selected governance concepts rather than claiming to implement a complete regulatory framework.

Design thesis

The LLM can reason. It cannot expand its own spending authority.

Pegas treats probabilistic reasoning and financial authority as different layers. The model can interpret, route and analyze. Deterministic controls decide whether a financial side effect is allowed at all.

LLM

Reasoning / routing / specialist analysis

Flexible interpretation stays inside clearly defined roles.

Deterministic system

identitymandateamountpayeenetworkassetbudgetskill switchsigning permissionevidence requirements
Seller cannot expand buyer authority.
Exact payment terms are frozen before signing.
Facilitator success alone is not final proof.
Independent chain evidence must match the approved offer.
The mandate is consumed after the authorized payment.
Paid specialist output is delivered only after confirmed evidence.

Live stack

Under the hood

One deterministic orchestration layer separates model reasoning from payment authority, then independently verifies what settled on-chain.

Browser

Vercel / Next.js

public app + server orchestration

Deterministic Pegas orchestration

identity, mandate, limits, authorization, evidence gates

AI path

Reasoning stays probabilistic

Modal

↓

Ollama

↓

qwen3:4b

↓

NVIDIA L4

Payment path

Authority stays deterministic

Bounded authority

↓

x402 V2

↓

Solana Devnet

↓

Alchemy evidence

Upstash Redis

Payment-side idempotency, reservations, budgets/concurrency and receipt state. It is attached to the payment path, not used as a general workflow database.

System boundary

What is real. What is deliberately bounded.

The demo is transparent about where production behavior is real and where the environment is intentionally constrained.

Real system behavior

  • Real Qwen calls on Modal
  • Real x402 402/payment flow
  • Real Solana Devnet settlement
  • Real Alchemy chain evidence
  • Real Upstash payment-side state
  • Real deterministic authority checks
  • Real paid Legal Advisor
  • Real duplicate-payment protection

Demo boundary

  • Fictional company/request
  • Test USDC
  • Solana Devnet
  • Fixed 0.01 payment
  • KYA-lite identity registry
  • Not production identity/compliance infrastructure
  • No mainnet funds
  • No browser wallet

Development story

Read how we built it.

Read how we built it →