Update to Phonic

{
  "description": "Create and configure Phonic agents and phone calls using MCP, SDKs, or REST. Use for saved agents, inbound numbers, outbound calls, prompting, and project operations.",
  "included_files": [],
  "name": "phonic-agents",
  "skill_md_contents": "---\nname: phonic-agents\ndescription: Create and configure Phonic agents and phone calls using MCP, SDKs, or REST. Use for saved agents, inbound numbers, outbound calls, prompting, and project operations.\nlicense: MIT\n---\n\n# Configure Phonic agents and calls\n\nSDKs: `npm install phonic` / `pip install phonic`. Entry points: `new PhonicClient({ apiKey })` (Node), `Phonic(api_key=...)` / `AsyncPhonic(...)` (Python). REST base: `https://api.phonic.ai/v1` with `Authorization: Bearer $PHONIC_API_KEY`. Always use the `.ai` domain for API and docs URLs — `phonic.co` addresses still resolve for backward compatibility, but all new code should use `phonic.ai`.\n\nFetch live docs rather than from memory: use the index at [llms.txt](https://docs.phonic.ai/llms.txt). For the REST API, see [openapi.json](https://docs.phonic.ai/openapi.json). For the WebSocket protocol, see [asyncapi.json](https://docs.phonic.ai/asyncapi.json). If an endpoint does not appear in these docs, it doesn't exist, do not invent one.\n\n## SDK surface\n\n- Agents: `client.agents.create/get/list/update/upsert/delete`. `upsert` is create-or-update by name (idempotent). Agents are identified by name.\n- Outbound calls: `client.conversations.outboundCall(...)` — greeting goes in `config.welcome_message`.\n\n## MCP calls and saved configuration\n\nRegular outbound calls remain available through `create_outbound_call`. Direct SIP outbound calls and custom SIP phone-number registration are excluded from MCP while saved SIP connections are unsupported; do not invent a connection-ID tool or request SIP credentials in chat.\n\nFor external storage, direct the user to [Phonic](https://phonic.ai), select the intended workspace/project, and create or rotate credentials in **Project settings → External storage policies**. Then list saved policies through MCP and reference the policy name or ID supported by the operation. Configure authenticated configuration endpoints on the website; MCP cannot submit their headers.\n\nDo not collect these credentials through chat or an SDK/REST/shell workaround for an excluded MCP operation. When implementing an SDK application, use existing environment variables or a secrets manager without displaying secret values.\n\n## Prompting voice agents\n\nVoice prompts differ from chat prompts (speech formatting, silence handling, naturalness) — use [the prompting guide](https://docs.phonic.ai/docs/build/agents/prompting_guide.md).\n\n## Operations\n\n- **Projects** organize agents/tools/numbers within a workspace; use one project per tenant/product line rather than a new workspace. API keys are workspace-level.\n- **Rate limits**: see [the rate limits page](https://docs.phonic.ai/docs/platform/rate_limits.md); high-volume outbound campaigns need client-side concurrency caps.\n- **Observability**: per-call outcomes via the webhook events above; live read-only monitoring via the live WebSocket; [audit logs](https://docs.phonic.ai/docs/platform/audit-logs.md).\n\n## Campaign and batch dialers\n\n- **Campaign/batch dialers**: claim each number (durable in-progress state) before dialing and design the claim so a second runner instance can't grab it too — per-run completion state alone doesn't prevent two processes from double-dialing.\n"
}