create_multi_channel_verification
Challenges one phone number across multiple channels at once, issuing a proof token from the first channel the user verifies and canceling the rest.
Instructions
Create a multi-channel phone verification: one phone number challenged over several channels at once (OR / first-wins). The first channel the user completes wins, yields a single proof token, and cancels the losing siblings. Quota is charged per channel.
Agent usage: the response includes a group_id (format vg_) and a channels array — each block carries a deep_link (WhatsApp/Telegram) or an sms_message to present to the user — pass the deep_link to render_auth_link. A block's qr_text is that same link already rendered as QR art, not an alternative address: print it verbatim inside a fenced code block or leave it out. Poll get_multi_channel_verification_status with the group_id to track completion and retrieve the proof token when a channel verifies.
ACCESS: needs a Proof account. Set PROOF_API_KEY and restart this server, then call this tool again. start_login does NOT open this tool.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | Asset type — only "phone" is supported | |
| channels | Yes | 1-4 unique channels attempted in parallel (first to complete wins) | |
| identifier | Yes | Phone number in E.164 format | |
| client_metadata | No | Custom key-value metadata | |
| external_user_id | No | Your application user ID for grouping verifications | |
| proof_expiry_days | No | Per-request proof expiry override in days (1-365) |