INAIGAI Integration Intelligence · HyperSwitch (Apache-2.0)
A live demo on the HyperSwitch codebase

Two ways inaigai shows up for a merchant.

Everything here is grounded in a real open-source payments codebase — nothing is scripted for the demo. Pick whichever you want to see first.

01

The dashboard

Every call a merchant made, in one place — with the grounded explanation attached to each one, and an assistant they can ask about any of them.

  • A merchant developer sees their whole integration, not one response at a time
  • They ask questions in their own words and get answers from your code
  • Your team can see exactly where a merchant is stuck — before a ticket arrives
02

Live enrichment

The part that rides on the API response itself: an additive _ai block carrying the grounded explanation, in the response the merchant already receives.

  • Arrives where the developer already is — no new tool to adopt
  • Additive only: your response body, status and headers are untouched
  • Absent if inaigai is unavailable — the call routes straight through
About the playground: to show enrichment we needed somewhere to fire calls from, so we built one. In practice these calls come from a merchant's own code, or from Postman during active development — the playground is not part of the product. Only the enrichment block on the response is. Calls you fire here also flow into the dashboard, the same way real sandbox traffic would.
Prefer the guided version? Walk through the story instead.
Ask inaigai
inaigai MVP · grounded in the HyperSwitch codebase · sandbox-only · nothing in the production path View audit trail →