Give Your Vapi Voice Agent Access to Any Portal (July 2026)
A Vapi agent is only as useful as the systems it can touch mid-call. How to give it real-time access to portals with no API, at voice-grade latency. Updated July 2026.
Vapi made shipping a production voice agent fast. The hard part moved: a caller asks "when is my appointment?" and the answer lives in a practice management portal, a dealer system, or a property platform with no API. The agent either answers from that system mid-call or it takes a message like it's 1995.
TL;DR
Register a Supergood endpoint as a Vapi custom tool. The endpoint hits the portal's own backend and answers in milliseconds, fast enough to use inside a live conversation turn. Browser automation can't do this: a multi-second (often 30-plus-second) browser run is an eternity of dead air on a phone call.
Why voice is the unforgiving case
A voice turn has a latency budget measured in hundreds of milliseconds before the silence gets awkward and callers start repeating themselves. In our measured example, a browser-automation run on a real portal workflow took 47 seconds; the same workflow as two direct API calls took 16 milliseconds. One of those fits inside a conversation. We wrote up the full argument in Why Browser Automation Is Too Slow for Voice Agents.
The setup
- Get the endpoint. The business adds a Supergood service account (real managed email and phone) to their portal; Supergood generates documented REST endpoints for the actions the agent needs (look up appointment, check a balance, create a work order).
- Register it as a tool. Add the endpoint as a Vapi custom tool (function calling with the request schema from the docs), or point an MCP-capable stack at the same integration's MCP server.
- Let the agent use it mid-call. Structured JSON comes back in milliseconds; the agent speaks the answer in the same turn. Errors are real status codes, so the agent can say "I couldn't find that" instead of hallucinating.
FAQ
Which portals can a Vapi agent reach this way? Any web portal a user can log into. We publish docs for hundreds of vertical systems; if the one you need is missing, requests reorder the build queue weekly.
What about MFA on the portal account? Handled by the service account's managed email and phone. No human gets paged to read a code mid-call.
Is this HIPAA-compatible for healthcare voice agents? Supergood supports HIPAA workloads and holds SOC 2 Type II, with full audit logs of every call the agent makes.
Related reading
- Why Browser Automation Is Too Slow for Voice Agents — the latency math in full.
- MCP for Software Without a Public API — the same integrations as agent tools.
Updated July 2026.