Agents Propose. Policy Decides. The Ledger Proves.
AgentPay sits between an autonomous shopping agent and PayPal. Proposals from the agent hit a policy gate before any money moves, a deterministic engine scores each one, and every decision lands in an approval queue and a hash chained ledger. Checkout is simulated end to end, so no live funds ever move.
- Surface
- Policy And Audit Console
- Engine
- Deterministic, Offline
- Data
- Synthetic And Seeded
- Checkout
- Simulated, No Live Funds
- Tests
- Run With Node
Scoring the sample proposal.
Scored on page load by the same engine the console below runs. Same inputs, same verdict, every time.
- Pending Review
- 0
- Approved This Session
- 0
- Blocked This Session
- 0
- Approved Volume
- $0.00
Policy Studio
The gate is yours to configure. Each policy carries a merchant scope, a category scope, an amount ceiling, a velocity window with transaction and spend caps, an allowed UTC hour range, and a minimum trust tier. Toggling or removing a policy appends to the audit trail, and changes apply to the next agent run.
Run The Agent
Atlas is a scripted shopping agent, not a live model. Each run proposes purchases from a seeded synthetic catalog of ten merchants, and every proposal is scored by the gate before it can reach the queue.
The Approval Queue
Nothing spends on its own. Proposals wait here until a human decides. Approving runs the simulated checkout stub and writes an approved row to the ledger. Rejecting writes a blocked row. Both append audit entries with before and after states.
How The Engine Reasons
The score starts from a base of 62 and moves with the evidence. Trust tier adjusts it, amount and velocity apply bounded penalties, and each rule hit subtracts weight by the severity of its policy. A policy verdict always wins over the arithmetic.
Score Waterfall, Sample Proposal
Computing the sample score.
The hero proposal, decomposed. Deterministic on every machine.
- ceiling
- The amount exceeds the policy ceiling.
- velocity.count
- Prior transactions for the merchant in the window reach the cap.
- velocity.spend
- Window spend plus this amount crosses the spend cap.
- hours
- The proposal hour in UTC falls outside the allowed window.
- tier
- The trust tier sits below the policy minimum.
- no.match
- No enabled policy matches, so the proposal is held for review instead of passing silently.
Hit weight follows the policy action: block 22, review 10, allow 4, unmatched 10. Penalties cap at 40 for hits, 20 for amount, and 24 for velocity.
The Transaction Ledger
Every seed and session transaction in one table. Sort columns and filter by text and number in AG Grid Community, loaded from a CDN. Switch to the built in table to group rows by merchant, category, agent, status and more, with counts and subtotals. If the CDN fails, that table takes over on its own.
Audit Integrity
Append only and hash chained. Each entry records the actor, the action, the entity, and the before and after states. The chain is reverified on every render. The hash is FNV 1a, chosen for determinism in a demo, not for cryptographic strength.
Chain Verified