Slide 1

Slide 1 text

Opey Agentic API Discovery and Action

Slide 2

Slide 2 text

Tell Me, Give Me, Show Me! Interacting with APIs in a conversation. Painting arbitrary interfaces in real time.

Slide 3

Slide 3 text

Growing Complexity - The Wild West Well over 200 million APIs worldwide

Slide 4

Slide 4 text

The Open Bank Project API Explorer ➔ 500+ API endpoints (open banking and beyond) ➔ API First ➔ Automated Documentation ➔ Consistent

Slide 5

Slide 5 text

Introducing Opey’s mission is to simplify discovery, action and interface creation via APIs through natural language conversation. Using GPT-4o, working with OBP API v5.1.0. The Intelligent API Assistant Agent

Slide 6

Slide 6 text

Opey v2.0 6 From informing to executing. Opey 2 moves from guidance to action. With delegated permissions via open banking consents, Opey becomes an agent that can directly execute API calls.

Slide 7

Slide 7 text

How Why Opey Works ➔ API-Driven ➔ Machine-readable ➔ Focus on authentication ➔ Respects the OBP role and consent framework

Slide 8

Slide 8 text

Behind the scenes ➔ Parse: Opey ingests Swagger-defined API endpoints, organising them into structured, retrievable documents. ➔ Identify: Using vector similarity search, Opey interprets queries and identifies the most relevant API endpoints. ➔ Execute: Opey uses tools to call the relevant APIs.

Slide 9

Slide 9 text

Creating the database

Slide 10

Slide 10 text

AI Agent

Slide 11

Slide 11 text

(OBP) Consents ● Application Access ● User Consent Flow ○ Initiation ○ Authentication & Authorisation ○ Confirmation ○ Strong Customer Authentication ○ Status / Validity ○ Revocation ● Exemptions

Slide 12

Slide 12 text

Trends for the Future ● The Age of AI is powered by APIs: An agent will need access to an array of “AI-friendly” APIs to perform complex tasks. ● Arbitrary interfaces: We are used to providing the same GUI to all users—what could we do with the degree of UI fluidity promised by agents? ● Agentic Payments Everything: With a more sophisticated consent framework, we will be able to securely delegate payments and other sensitive yet tedious tasks to agents.

Slide 13

Slide 13 text

Lessons So Far ● Get ready for (pleasant) surprises. ● We’re still writing code. ● We’re improving our documentation, now for Opey!

Slide 14

Slide 14 text

What might Opey do next? ● Integrate into new API catalogs or data frameworks to unlock and reveal use cases across different industries. ● Improve interoperability with legacy systems - REST APIs are not the only interfaces. SQL is also an interface.. ● Evolve user-tailored interaction frameworks to align Opey’s functionality with specific requirements and user personas

Slide 15

Slide 15 text

Opey www.openbankproject.com