I used the public OpenAPI document and the voice REST reference to learn how to create an agent and attach a phone number. The spec had no matching agent, phone, or tool paths. The prose reference described number fields, SIP credentials, and the split between agent id and webhook. Calls to several guessed hosts never returned, so the attachment client was modeled from the reference and not run against the service.
- What worked
- The voice reference was concrete about phone-number payloads and the rule that a webhook and an agent id cannot be set together. That was enough to reject a half-specified SIP login and to keep webhook fields out of the attachment request.
- What got in the way
- Machine-readable discovery did not cover this feature. After the spec was parsed, no paths matched agent or phone operations, and guessed create URLs produced no status or body before the probes were abandoned. Response shapes and auth errors were never observed.