2 languages served
2 languages served
3 surfaces live
3 surfaces live
5 SDK platforms covered
5 SDK platforms covered
CUSTOMER STORY / SEMICONDUCTORS
CUSTOMER STORY / SEMICONDUCTORS

How Realtek answers Ameba developer questions in two languages, from the docs to the IDE

Challenge

Ameba developers work across dozens of SoCs, five SDK platforms, and thousands of pages of datasheets and specs, and they ask in both Chinese and English. On a pin definition or an electrical characteristic, a confident wrong answer is worse than no answer at all.

Solution

Index the Ameba documentation, datasheets, and the ameba-rtos code in one Kapa knowledge base, then deploy it as a chatbot on the AIoT documentation site and as a public MCP server that developers point Cursor, Claude Code, or Codex at.

Results

  • Chinese and English answered from one knowledge base

  • Every answer cited back to a datasheet, SDK page, or code example

  • Documentation query MCP live at ameba-aiot.mcp.kapa.ai

  • Answer quality rated 9 out of 10 during evaluation

Documentation Agent

Ameba answers with citations, in Chinese or English

A chat agent embedded on your documentation site that answers natural-language questions with citations back to source. On aiot.realmcu.com it reads chip specifications, datasheets, and the ameba-rtos SDK documentation, and replies in the language the developer asked in.

Play video

Website Agent

Chip selection questions answered on the AIoT site

The same agent embedded on your site with one script tag, answering from the documentation wherever visitors ask. Realtek runs it behind the AI icon on aiot.realmcu.com, so an engineer comparing RTL8720 and RTL8730 parts confirms protocol and feature support without leaving the page.

Play video

MCP Server

Ameba context via ameba-aiot.mcp.kapa.ai

A hosted MCP server connected to your knowledge base, shareable as a single link for Cursor, Claude Code, or ChatGPT. Realtek documents it as the knowledge layer next to its own local SDK server, so a coding agent looks up the datasheet and then builds and flashes the firmware in one loop.

Play video

Why Kapa

One corpus, several surfaces. The chatbot in the Ameba documentation, the assistant on the AIoT site, and the MCP server a developer wires into Cursor or Claude Code all read the same indexed sources, so the same question gets the same cited answer wherever it is asked.

That matters most across languages. Realtek’s community asks in Chinese and in English, and Kapa answers from the same English-language datasheets and SDK documentation in whichever language the question arrives, so a lean documentation team maintains one knowledge base instead of two.

Everything you need to give your agents accurate retrieval, ready in minutes.

Get started for free. Connect your sources and get an API key or hosted MCP server to give your agents the context they need to do reliable work at scale.