NetBird
trust_gates_verification_create
Starts the verification for one requirement, and what comes back decides who finishes it. A provider-hosted requirement answers with `hosted_url`: give that link to the person whose identity is being checked and stop, because only they can complete it. A one-time-code requirement answers with the channel and a masked destination instead, and you continue with `trust_gates_verification_check` once they tell you the code. Send no body for the hosted kind; a code requirement takes the email or phone number to send to.
Remote bird/mcp
Remote (network-hosted)
Other tools also called trust_gates_verification_create?
See providers with this name
Input Schema
{
"type": "object",
"properties": {
"slug": {
"type": "string",
"description": "The requirement to verify, as its slug from trust_gates_list."
},
"email": {
"type": "string",
"description": "Where to send the one-time code, for a requirement verified that way. Omit for a provider-hosted requirement, which sends nothing and returns a link instead. Send this or phone_number, never both."
},
"phone_number": {
"type": "string",
"description": "Where to send the one-time code, in E.164. Omit for a provider-hosted requirement. Send this or email, never both."
},
"idempotency_key": {
"type": "string",
"description": "Deduplication key; a retry with the same key will not start a second verification."
}
}
}