Communication · wired today
What can agents actually do with Plivo?
Messages and calls are where work actually gets decided. The Plivo connector is one of 205 executable connectors and gives agents 3 read-only tools, with the credential held in the vault and every call receipted.
The Plivo tool list, exactly as agents see it
account_details— Get the Plivo account this credential belongs to (name, type, billing mode, cash credits)list_messages— List recent Plivo SMS/MMS messages, optionally filtered by direction or state. Message text is not returnedlist_numbers— List the phone numbers rented on this Plivo account, optionally filtered by type or prefix
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Plivo connector needs
You provide auth ID, auth token from your Plivo account; Quox sends it as HTTP basic credentials. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: Plivo's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real Plivo API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.
Plivo integration FAQ
What can Quox agents do with Plivo?
Agents can run 3 read-only tools against Plivo: account details, list messages, list numbers. Every call is receipted in the evidence trail.
What does the Plivo integration need?
You provide auth ID, auth token from your Plivo account; Quox sends it as HTTP basic credentials. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my Plivo credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the Plivo connector?
This connector was blind shape-proven against the real Plivo API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.