apidays Paris 2024 - Opey, the AI for API Discovery and Future of Fintech, Simon Redfern and Nemo Godebski-Pedersen, TESOBE GmbH

Opey, the AI for API Discovery and Future of Fintech
Simon Redfern, Founder of the Open Bank Project and CEO of TESOBE GmbH
Nemo Godebski-Pedersen, AI Lead Developer at TESOBE GmbH / Open Bank Project

apidays Paris 2024 - The Future API Stack for Mass Innovation
December 3 - 5, 2024

------

Check out our conferences at https://www.apidays.global/

Do you want to sponsor or talk at one of our conferences?
https://apidays.typeform.com/to/ILJeAaV8

Learn more on APIscene, the global media made by the community for the community:
https://www.apiscene.io

Explore the API ecosystem with the API Landscape:
https://apilandscape.apiscene.io/

Transcript

1. Opey Agentic API Discovery and Action
2. Tell Me, Give Me, Show Me! Interacting with APIs in a conversation. Painting arbitrary interfaces in real time.
3. Growing Complexity - The Wild West Well over 200 million APIs worldwide
4. The Open Bank Project API Explorer ➔ 500+ API endpoints (open banking and beyond) ➔ API First ➔ Automated Documentation ➔ Consistent
5. 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
6. 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.
7. How Why Opey Works ➔ API-Driven ➔ Machine-readable ➔ Focus on authentication ➔ Respects the OBP role and consent framework
8. 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.
9. Creating the database
10. AI Agent
11. (OBP) Consents • Application Access • User Consent Flow ◦ Initiation ◦ Authentication & Authorisation ◦ Confirmation ◦ Strong Customer Authentication ◦ Status / Validity ◦ Revocation • Exemptions
12. 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.
13. Lessons So Far • Get ready for (pleasant) surprises. • We’re still writing code. • We’re improving our documentation, now for Opey!
14. 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
15. Opey www.openbankproject.com