Answering-machine detection (WebSocket)

curl --request GET \
  --url https://api.pyai.com/v1/amd/stream \
  --header 'Authorization: Bearer <token>'

{
  "error": {
    "message": "<string>",
    "type": "<string>",
    "param": "<string>"
  }
}

AMD

Answering-machine detection (WebSocket)

Realtime answering-machine detection over a WebSocket. This surface speaks Twilio’s Media Streams protocol natively (start / media / stop frames, G.711 μ-law 8 kHz base64, ~20 ms), so migrating from Twilio AMD is a one-line-TwiML change, point the call’s media at PyAI, keep your carrier and your code.

<Response><Connect>
  <Stream url="wss://api.pyai.com/v1/amd/stream">
    <Parameter name="aggressiveness" value="0.25"/>
    <Parameter name="webhook" value="https://you/amd-events"/>
  </Stream>
</Connect></Response>

Authenticate with the Sec-WebSocket-Protocol: pyai-key.<API_KEY> subprotocol (or ?api_key= server-side). Requires the amd:detect scope. Mid-call, PyAI pushes an amd decision event on the socket (and to your webhook): answered_by (PyAI’s richer vocabulary), answered_by_twilio (Twilio’s exact AnsweredBy enum for drop-in routing parity), confidence, decision_ms, and a human-readable reason. The per-call aggressiveness <Parameter> overrides the account default from POST /v1/amd/config.

Billed per answered call (amd.calls), the first 5,000 answered calls/month are free, then $0.004/answered call; AMD bundled with PyAI telephony/Omni is included.

GET

amd

stream

Answering-machine detection (WebSocket)

curl --request GET \
  --url https://api.pyai.com/v1/amd/stream \
  --header 'Authorization: Bearer <token>'

{
  "error": {
    "message": "<string>",
    "type": "<string>",
    "param": "<string>"
  }
}

Authorizations

Authorization

string

header

required

Use Authorization: Bearer pyai_live_... (or pyai_test_...).

Response

WebSocket upgrade, Twilio Media Streams protocol; PyAI emits amd decision events.

Manually trigger recap for a call Get AMD config