Jentic publishes the only available OpenAPI specification for Verify API, keeping it validated and agent-ready. The Vonage Verify API runs end-to-end two-factor authentication flows by sending a PIN to a phone number over SMS, falling back to TTS voice if the SMS is not entered, and validating the user-entered code. The 6 endpoints cover request, check, search, control, network unblock, and the PSD2 Strong Customer Authentication variant for payment confirmation. Vonage manages PIN generation, retry workflow, and per-recipient throttling so the application only handles request and check.
6 endpointsJentic publishes the only available OpenAPI specification for Verify API, keeping it validated and agent-ready. The Vonage Verify API runs end-to-end two-factor authentication flows by sending a PIN to a phone number over SMS, falling back to TTS voice if the SMS is not entered, and validating the user-entered code. The 6 endpoints cover request, check, search, control, network unblock, and the PSD2 Strong Customer Authentication variant for payment confirmation. Vonage manages PIN generation, retry workflow, and per-recipient throttling so the application only handles request and check.
6 endpointsStep 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.