Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ProWebLook API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fproweblook.com%2Fproweblook" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fproweblook.com%2Fproweblook" | 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.
What an agent can do with ProWebLook API.
Check whether a phone number is registered on WhatsApp, one at a time or as a polled batch
Validate a phone number with an optional country_code and look up its caller ID
Verify that an email address is deliverable
Geolocate an IP address and check an IP, domain, or URL against blacklists with target_type
Search Reddit, X, or LinkedIn and fetch individual posts and X comments
GET STARTED
Fetch Google SERP results for a query by country, language, and device
Scrape a URL to markdown, HTML, links, metadata, or a screenshot, and score email content for spam
Patterns agents use ProWebLook API for, with concrete tasks.
★ Agent-Driven Contact Validation
An AI agent connected through Jentic cleans a contact before outreach: it verifies the email address, validates the phone number with its country_code, and checks whether the number is on WhatsApp so the user knows which channel will reach the person. For a long list it submits a WhatsApp batch and polls it by batch_id instead of checking each number in turn.
Verify the email jane@example.com, validate phone_number 7700900123 with country_code 44, and check whether that number is on WhatsApp
Sender Reputation Check
Before a campaign, a deliverability workflow checks the sending domain and IP against blacklists with target_type set to domain or ip, and scores the draft's subject and content with the spam checker. Problems surface before the send instead of after bounces start.
Check target example.com with target_type domain against blacklists, then run the spam checker on the campaign subject and content
Social and Search Monitoring
A marketing agent tracks how a brand shows up online. It searches Reddit, X, or LinkedIn for mentions, fetches the posts and X comments worth reading, pulls Google SERP results for target queries by country and device, and runs an AI visibility audit with brand_name, brand_url, and competitors to see how the brand appears in AI answers.
Search Reddit for 'acme analytics', fetch the Google SERP for 'acme analytics review' in the US, and run an audit with brand_name Acme and brand_url acme.com
Page Capture for Research
Research agents need a page's content in a form they can read. The scrape operation takes a URL and returns the formats requested, such as markdown for reading, links for crawling, or a screenshot for a visual record.
Scrape https://example.com with formats markdown and links and summarize the page
28 endpoints — the proweblook api validates phone numbers, whatsapp numbers, and email addresses, and runs a set of lookups and scrapers around them.
METHOD
PATH
DESCRIPTION
/checkemail
Verify an email address
/phonevalidation
Validate a phone number
/wavalidation
Check whether a number is on WhatsApp
/wavalidation/batch
Submit a WhatsApp validation batch
/calleridvalidation
Look up caller ID
/blacklistchecker
Check an IP, domain, or URL against blacklists
/google_serp
Get Google SERP results
/scrape
Scrape a URL or take a screenshot
/checkemail
Verify an email address
/phonevalidation
Validate a phone number
/wavalidation
Check whether a number is on WhatsApp
/wavalidation/batch
Submit a WhatsApp validation batch
/calleridvalidation
Look up caller ID
/blacklistchecker
Check an IP, domain, or URL against blacklists
/google_serp
Get Google SERP results
/scrape
Scrape a URL or take a screenshot
What agents get from Jentic-routed access to this vendor.
Setup
Wiring ProWebLook by hand means routing calls to three hosts (proweblook.com, lookup.proweblook.com, and ipapi.proweblook.com) and putting the api_key in the query string for some operations and in the request body for others. Through Jentic you install once, import ProWebLook from the API Directory, store the key once, and your agent calls it.
Permission scoping
ProWebLook carries lookup targets such as phone numbers, emails, and URLs in query parameters or the request body, so a rule bounds which operations your agent may call, not which number or domain. You choose the operations it may call, so the send WhatsApp message operation is not included unless you add it.
Credential isolation
Your ProWebLook API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'verify an email address' or 'check if a number is on WhatsApp', and Jentic returns the matching ProWebLook operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using ProWebLook API through Jentic.
What authentication does the ProWebLook API use?
The ProWebLook API authenticates with an API key, which its OpenAPI spec declares as the api_key query parameter (scheme apiKey). Placement varies by operation: some POST operations, such as WhatsApp validation, the spam checker, and URL scraping, accept api_key in the request body instead, and the status check needs no key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.
What are the rate limits for the ProWebLook API?
The OpenAPI spec does not give fixed numeric limits, but it documents response headers for the calls remaining in the current rate-limit window and the seconds until it resets. Check https://proweblook.com for the limits on your plan, and use the check balance operation to read your account balance.
Can I check many numbers for WhatsApp at once with the ProWebLook API?
Yes. Submit numbers through the WhatsApp batch operation and poll the batch by its batch_id for results. Single numbers can be checked with the WhatsApp validation operation, by GET with phone_number and an optional country_code or by POST.
Is there a ProWebLook MCP server?
You don't need an MCP server to give your agent ProWebLook. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, with operations found on demand across all three ProWebLook hosts.
Can I limit what my agent is allowed to do with the ProWebLook API?
Yes. For example, write a rule that allows only the email verification, phone validation, and WhatsApp validation operations, so the agent can check contacts while the send WhatsApp message operation and the scrapers stay out of reach. Every call it makes is logged.
How do I verify an email address with the ProWebLook API through Jentic?
Import the ProWebLook API from the Jentic API Directory, store your API key once, and have your agent search Jentic for 'verify an email address'. Jentic returns the verify email operation with its input schema, where email is the required query parameter, and injects the api_key at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Validate phone, WhatsApp, and email contacts, identify callers, geolocate and blacklist-check IPs and domains, scrape social posts and Google SERPs, and run AI visibility audits with ProWebLook.
Use for: Check whether +447700900123 has a WhatsApp account, Verify this email address before I add it to my list, Find out who owns this calling number, Check whether my sending domain is on any blacklists
Not supported: Does not send email campaigns, store contacts, or provide company firmographics. Use for validating phones, WhatsApp numbers, and emails, plus IP, blacklist, social, and SERP lookups only.
The ProWebLook API validates phone numbers, WhatsApp numbers, and email addresses, and runs a set of lookups and scrapers around them. It checks whether a number is on WhatsApp, singly or in batches, identifies callers, verifies email addresses, geolocates IPs, and checks IPs, domains, and URLs against blacklists. It also scrapes Reddit, X, and LinkedIn searches and posts, returns Google SERP results, scrapes a URL to markdown, HTML, links, or a screenshot, scores email content for spam, and runs AI visibility audits that compare a brand against competitors. Operations are spread across the proweblook.com, lookup.proweblook.com, and ipapi.proweblook.com hosts.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>