For Agents
Look up website trustworthiness, child safety scores, blacklist status, and category data for any domain to keep agents and users away from malicious or unsafe sites.
Use for: Check whether a domain is safe before an agent visits the URL, Look up the WOT reputation score for example.com, Find all domains in a list that have a child-safety warning, Verify that a redirect target is not flagged as a phishing site
Not supported: Does not handle malware sandboxing, IP threat scoring, or SSL certificate validation — use for domain reputation and child safety lookups only.
Jentic publishes the only available OpenAPI specification for Web of Trust (WOT) Reputation API, keeping it validated and agent-ready. Web of Trust scores websites by trustworthiness and child safety using community feedback combined with machine-learning signals. The API exposes a single GET /targets endpoint that accepts one or more domains and returns reputation, child safety, blacklist, and category data so agents can decide whether to follow a link, allow a redirect, or warn the user.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Web of Trust (WOT) Reputation 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://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.
What an agent can do with Web of Trust (WOT) Reputation API.
Look up reputation scores for one or more domains in a single request
Retrieve child safety ratings for filtering kid-friendly browsing flows
Check whether a domain appears on a security blacklist or phishing feed
Read community-driven trust categories such as malware, scam, or adult content
Score URLs at link-resolution time before the agent fetches the page
Patterns agents use Web of Trust (WOT) Reputation API for, with concrete tasks.
★ Pre-Browse Safety Screening for Agents
Before an AI agent or browser-automation tool fetches a URL, call GET /targets with the domain to read its reputation, child safety, and blacklist status. If the score is below threshold or the domain appears on a malware list, the agent refuses or warns the user. Adds a low-latency safety net to web-fetching agents that would otherwise follow any URL the user pastes.
Call GET /targets?targets=example.com and refuse to fetch the page if the reputation score is below 60 or the malware category fires.
Family-Safe Content Filtering
Parental-control products and family-mode browsers query the child-safety dimension of WOT reputation to allow or block a domain for under-18 users. The single /targets endpoint returns child-safety scores alongside the trust score, making per-domain policy decisions simple. Useful for school-issued devices, kids' tablets, and family-mode AI assistants.
For each domain in a teenager's bookmark list, call /targets and remove any domain whose child safety score is below 70.
Bulk Domain Reputation Monitoring
Marketing, security, and partnership teams monitor large lists of partner or competitor domains for new reputation drops or blacklist appearances. Send batched domains in a single /targets call and store the response for delta detection. Cheaper and faster than running multiple single-domain queries against typical reputation services.
Pull WOT scores for 200 partner domains via a single /targets call and alert if any score has dropped more than 15 points week-on-week.
AI Agent URL Safety Tool
Expose WOT reputation as a Jentic tool so agents can automatically vet any URL they consider clicking. Through Jentic the agent searches for 'check website reputation', loads the schema for /targets, and executes the call with the API key held server-side. Adds defence-in-depth on top of model-level safety policies for agents that browse the open web.
When a user pastes a URL, search Jentic for 'WOT reputation', execute /targets, and surface the score and category labels in the agent's reply before following the link.
1 endpoints — jentic publishes the only available openapi specification for web of trust (wot) reputation api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/targets
Look up reputation, child safety, blacklist, and category data for one or more domains
/targets
Look up reputation, child safety, blacklist, and category data for one or more domains
Three things that make agents converge on Jentic-routed access.
Credential isolation
WOT x-user-token API keys are stored encrypted in the Jentic vault. Agents call /targets via Jentic's execution layer, which injects the header server-side, so the raw token never enters the agent's prompt or chat logs.
Intent-based discovery
Agents search by intent (e.g., 'check whether a domain is safe') and Jentic returns the WOT /targets operation with its parameter schema, so the agent can build the request without reading the spec.
Time to first call
Direct WOT integration: half a day for auth wiring and response parsing. Through Jentic: under 15 minutes for the first reputation lookup.
Alternatives and complements available in the Jentic catalogue.
AbuseIPDB API
IP-based abuse and threat reputation rather than domain trust scoring
Choose AbuseIPDB when the agent needs to vet outbound IP connections instead of full URLs.
Specific to using Web of Trust (WOT) Reputation API through Jentic.
Why is there no official OpenAPI spec for Web of Trust (WOT) Reputation API?
WOT does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Web of Trust (WOT) Reputation API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Web of Trust API use?
The API uses an API key passed in the x-user-token header (defined as ApiKeyAuth in the spec). Through Jentic, the x-user-token is stored encrypted in the vault and injected at execution time, so the raw key never reaches the agent's context.
Can I look up multiple domains in a single Web of Trust API call?
Yes. GET /targets accepts a comma-separated list of domains in the targets query parameter and returns scores for each in one response, which is the cheapest way to bulk-check a list.
What data does the Web of Trust API return for a domain?
The /targets response includes a trust score, child safety score, blacklist indicators, and community-assigned category labels (such as malware, scam, or adult content). Use the trust and child safety scores together for safe-browsing decisions.
What rate limits apply to the Web of Trust API?
WOT does not document rate limits in the OpenAPI spec. Plan client-side throttling and exponential backoff on HTTP 429 responses; contact WOT for committed throughput before running large batch jobs over many tens of thousands of domains.
How do I add Web of Trust as a safety tool for an AI agent through Jentic?
Install the Jentic SDK with pip install jentic, then use SearchRequest with 'check website reputation' to find GET /targets, LoadRequest to load its schema, and ExecutionRequest to call it before browsing. Get an agent API key at https://app.jentic.com/sign-up.
GET STARTED