Can I check WhatsApp registration with the MobileValidate API?

Yes. Pass whatsapp in the checks list of a lookup or bulk job, alongside other service codes such as telegram, viber, carrier, or spam; the services operation lists every code and its price. The registered field is false only for a conclusive negative and null when the answer is unknown, and inconclusive answers are never charged.

Can I limit what my agent is allowed to do with the MobileValidate API?

Yes. For example, write a rule that allows only the lookup, estimate, and services operations, so the agent can run real-time checks and price a bulk job but cannot start a 50,000-row job, purge results, or change webhook endpoints, and every call it makes is logged.

What are the rate limits for the MobileValidate API?

The OpenAPI spec states that the public sandbox key is limited per IP address to 30 requests per minute and 1,000 per day. For your own keys, call the limits operation, which returns your limits and remaining allowances, and see https://mobilevalidate.com/docs for current account limits.

How do I validate a phone number with MobileValidate through Jentic?

Search Jentic for the intent 'check if a phone number is on WhatsApp', which returns the MobileValidate lookup operation on /lookup with its input schema; the agent sends numbers in E.164 format and the checks to run, and reads registered from each result row. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a MobileValidate MCP server?

You don't need an MCP server to give your agent the MobileValidate API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the lookup, job, and webhook operations. Operations are discovered on demand, so no extra tool definitions are loaded into the agent's context.