Live in production
DisplAI and the TransFi MCP server
Client engineers and their AI agents explore, call and integrate TransFi APIs from their own tools.
- Organisation
- TransFi
- When
- 2024 - now
- Areas
- GenAI, MCP, Developer experience
Problem
Client engineering teams need to understand, try and integrate TransFi's APIs.
TODO(shubham): What integration looked like before, and what support load it created.
Constraints
- Guardrails across both scope responses to TransFi topics only and enforce data isolation, so no secrets, credentials or other customers' data are exposed.
TODO(shubham): Other constraints: auth, which environments it can reach, model choice.
What I built
Two production GenAI products for client engineers.
- Client engineer or AI agent
- DisplAI or the TransFi MCP server
- TransFi APIs
- DisplAI: an AI developer platform that shortens client integrations. It answers support queries, executes TransFi API calls on the developer's behalf, and generates integration code in each client's preferred language.
- The TransFi MCP server: lets client teams and their AI agents integrate with TransFi from their own systems.
TODO(shubham): Architecture, and how the guardrails work.
Outcome
- Both are live in production.
TODO(shubham): Adoption or support numbers, if you can share them.
What I'd do differently
TODO(shubham): What you'd change with hindsight.