Sectors
One governed agent layer, for every sector.
Agents already act in banking, payments, commerce, treasury and the public sector. Pick yours to see what an agent may do there, who is in the chain and how each action is checked on AgenticOpenFinance.
All sectors
16 sectors
Retail banking
Customers already point agents at their accounts; banks need to see who is acting and within what limits.
- Permission dashboard
- Bill-payment mandates
- Decoupled approval
Wealth and robo-advice
An agent that proposes a trade is advice; an agent that places it needs authority.
- Rebalancing mandates
- Suitability checkpoints
- Client approval
Insurance underwriting and claims
Pricing and claims decisions made with AI need oversight and a record of what was decided and why.
- Claims agent with limits
- Document gathering under consent
- Human review queue
Lending and credit decisions
Credit decisions made with complex models still need reasons a person can read.
- Data access for applications
- Decision evidence
- Human review for edge cases
Payment service providers
Payment initiation was built for a customer at a screen, not for an agent acting later.
- Mandate-checked initiation
- Decoupled approval
- Rail routing
Card issuing and acquiring
An agent should hold its own limited credential, not the customer's card number.
- Agent tokens under mandate
- Per-agent controls
- Agent recognition at checkout
E-commerce merchants
Agents are arriving at checkout; merchants must tell them from bots and keep the order provable.
- Agent verification
- Agentic checkout
- Order evidence
Subscriptions and utilities
Recurring payments already have mandates; agents make them change more often.
- Parameters per payee
- Switching under mandate
- Change notices
Travel booking
A trip involves many sellers; each booking agent must pay within one traveller's budget.
- Trip mandates
- Seller agent verification
- Agent-to-agent payment
SME accounting and cashflow
Small teams want agents to do the finance admin, without handing over the bank login.
- Supplier payment mandates
- Collections within rules
- Cashflow view
B2B procurement and invoices
Buyer and supplier agents can settle invoices faster, if both sides can prove who agreed to what.
- Supplier agent verification
- Three-way match
- Payment under approval matrix
Corporate treasury
Liquidity moves are routine until one of them is wrong.
- Sweep parameters
- Business-day scheduling
- Dual approval
Payroll and HR
Payroll errors reach people directly; agents must stay well inside the numbers.
- Pay run limits
- Bank detail changes
- Approval before release
Trading and capital markets
Agents that trade must stay inside limits that the firm, not the model, sets.
- Trading mandates
- Pre-trade policy
- Kill switch
Tokenised deposits and stablecoin rails
Programmable money still needs a programmable mandate on top.
- Rail-neutral mandates
- HTTP 402 payment handling
- Purpose limits
Public sector disbursements and benefits
Public money paid by automated systems must be traceable to a rule and a decision.
- Eligibility evidence
- Payment to verified accounts
- Exception approvals