Brifing

Grab's AI Agent Platform: Scalable Solutions from Support Bot to Enterprise Framework

The evolution from technical support bot to corporate AI agent infrastructure.

Grab Tech2 min

1Starting point

Grab's AI journey began with a single technical support bot designed to handle repetitive infrastructure questions. With GPT-4 integration, it evolved into a 'Level-0' support layer capable of answering queries directly from documentation before human intervention.

2Initial architecture

The production version consisted of two core components: A reasoning layer processed user queries while a tool layer accessed internal systems like Confluence, Jira and Slack. Though simple JSON configurations worked initially, they created scaling challenges.

3Demo ≠ Production

The prototype bot faced unexpected challenges under real traffic. Dispersed logging systems, difficult model changes, and lack of evaluation revealed the unique demands of production environments.

4Model switching pain

As the AI ecosystem evolved rapidly, switching between providers created significant overhead. Rewriting payload schemas and error handling for each change slowed innovation velocity.

5Observability needs

Diagnosing incorrect answers required searching logs across three separate systems. Fragmented tracing mechanisms complicated troubleshooting and created unacceptable risks for customer-facing agents.

6Production hurdles

The real challenge wasn't the AI agent itself but surrounding infrastructure - authentication, secrets management, and vector database integration needed individual solutions per service.

7Common pain points

Different teams encountering similar issues revealed the need for centralized solutions. Lack of evaluation strategies, difficult model switching, and fragmented monitoring emerged as recurring patterns across AI projects.

8Birth of LLM-Kit

Consolidating shared components led to LLM-Kit. Rather than creating new abstractions, this framework aimed to provide standard solutions for fundamental infrastructure challenges.

9API gateway

A unified LLM gateway managing all model calls reduced provider lock-in. Now teams could switch between models with just a few configuration changes.

10MCP framework

Model Context Protocol servers standardized agents' access to shared contexts. With 50+ registered servers, this system simplified distributed knowledge management.

11Scaling success

Today 500+ services use this framework processing billions of tokens monthly. The infrastructure team's initiative transformed AI capabilities across the entire company.

12Key lessons

Grab's experience proves that productionizing AI agents depends more on surrounding infrastructure than models themselves. Standardized frameworks can significantly accelerate teams' innovation velocity.

Original article: Grab Tech — Grab'ın AI ajan platformu: Ölçeklenebilir çözümler