Open banking and consented account access
Open banking and finance APIs can provide bank data and payment initiation under authorization, but agent autonomy introduces additional consent and revocation questions.
Executive question
Which agent actions can our existing open finance rails legitimately support?
What to measure
- API access by client and permission scope
- Consent expiration/revocation
- Payment and data access failures
Relevant products and standards
Agent Payments Protocol: signed mandates that prove a customer authorized an agent's purchase. Created by Google (Sep 2025); donated to the FIDO Alliance with v0.2 on 28 Apr 2026.
Model Context Protocol: the standard way an AI agent connects to tools and data. Created by Anthropic (Nov 2024); donated to the Linux Foundation's Agentic AI Foundation on 9 Dec 2025.
Personal Agent Protocol: a draft (v0.1) for a customer's personal agent to identify itself to a business, get consent and open a session. Announced by Sierra and Meta on 6 Oct 2026 with six named partners; the 9 Oct draft lists seven initial partners and 35 design partners.
Relevant examples, not documented integrations, completeness, certification or endorsement. Listed alphabetically.
Evidence and current limits
Existing open banking traffic must not be labeled agentic traffic.
Draft analysis, under editorial review.