Integration
Connect Browse AI to Byteplant Phone Validator
When something happens in Browse AI, your agent does the next thing in Byteplant Phone Validator. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Browse AI and Byteplant Phone Validator to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Browse AI and Byteplant Phone Validator
Triggers and actions 1 trigger ยท 5 actions
Trigger
New TaskTriggers when a task is run and finished.
- Get Bulk Run
Retrieve a robot's bulk run by ID. Endpoint: GET /robots/{robotId}/bulk-runs/{bulkRunId}
- Get Robot
Retrieve a single robot by ID. Endpoint: GET /robots/{robotId}
- List Tasks
Get all tasks run by a robot. Endpoint: GET /robots/{robotId}/tasks
Action
Bulk Validate Phone NumbersUpload a CSV file (up to 100K phone numbers) for asynchronous bulk validation. POST https://api.phone-validator.net/api/v2/bulk-verify with Content-Type: text/csv and the CSV as the raw request body. Params: APIKey (required), TaskName, CountryCode, Locale, Mode (express|extensive), NotifyEmail, NotifyURL (optional). Response: {status: SUCC|FAIL, info: <task id if SUCC>}. Completion is announced via email and/or an HTTP GET to NotifyURL with a taskid query param; the vendor docs do not expose a separate poll/result-fetch endpoint.
- Validate Phone Number
Validate a phone number.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews