Install Jentic One Beta

Connect the PublicWWW Search API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PublicWWW Search 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%2Fpublicwww.com%2Fpublicwww" | sh

Step 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%2Fpublicwww.com%2Fpublicwww" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with PublicWWW Search API.

Search the page source of indexed websites for an exact code fragment, with site: and depth:all filters and -word exclusions

Return matches with domain, url, rank, and optional source snippets in json, csv, tsv, xml, ndjson, or txt

Save a search result or your own list of domains as a named cluster in your account

Combine two or more clusters with and, or, or diff to build a target list of sites

GET STARTED

Start building with PublicWWW Search API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use PublicWWW Search API for, with concrete tasks.

★ Agent-run technology prospecting

A sales or research agent can search the PublicWWW index for a code fragment that marks a technology, such as a vendor's script URL, save the matching sites as a cluster, then pull contact emails and phone numbers from those sites with the email and phone extraction presets. The agent checks the account endpoint first so the search fits inside today's quota.

Search for the fragment "cdn.shopify.com" with site:de, create a cluster from the query, then extract with presets email,phone and limit 1000

Tracking id and ownership research

Investigators link websites that share an analytics or ad account by searching for the same tracking id across the index. The search returns each matching domain with its rank, and the snippets option shows up to 5 fragments of page source around the match per row, which confirms the id appears in a live tag rather than in unrelated text.

Search for "UA-12345678" with snippets enabled and per_page 50, and list each domain with its rank and the first snippet

Market share comparisons with cluster sets

Analysts compare technology adoption by saving one cluster per technology and combining them. The combine operation takes cluster ids and an operation of and, or, or diff, so diff on two clusters returns the sites that use one product but not a competitor, ready to export as csv for a report.

Combine clusters 101 and 102 with operation diff and name the result 'uses A not B', then read the first page of its domains

Key Endpoints

12 endpoints — the publicwww search api searches the html, javascript, and css source of hundreds of millions of websites and returns the sites whose code contains a given fragment, such as a tracking id, script tag, or framework signature.

METHOD

PATH

DESCRIPTION

GET

/v1/search

Find websites whose source contains a code fragment

POST

/v1/clusters

Create a cluster from a search or domain list

POST

/v1/clusters/combine

Combine clusters with and, or, or diff

GET

/v1/clusters/{id}

Get a cluster and a page of its domains

GET

/v1/clusters/{id}/extract

Extract values from a cluster's sites

GET

/v1/account

Get plan, quota used today, and limits

GET

/v1/search

Find websites whose source contains a code fragment

POST

/v1/clusters

Create a cluster from a search or domain list

POST

/v1/clusters/combine

Combine clusters with and, or, or diff

GET

/v1/clusters/{id}

Get a cluster and a page of its domains

GET

/v1/clusters/{id}/extract

Extract values from a cluster's sites

GET

/v1/account

Get plan, quota used today, and limits

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring PublicWWW by hand means obtaining a Bearer token or running its OAuth 2.1 PKCE flow, staying inside a rate limit shared with its other clients, and paging extraction with next_offset. Through Jentic you install once, import PublicWWW from the API Directory, store the token once, and your agent calls it.

Permission scoping

PublicWWW puts the cluster id in the URL path (/v1/clusters/{id}/...), so a rule can pin your agent to one saved cluster and the operations you pick, while search parameters ride in the query or body. You choose the operations it may call, so destructive ones like cluster delete or rename are not included unless you add them.

Credential isolation

Your PublicWWW token 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 'find websites using a script' or 'extract emails from a list of sites', and Jentic returns the matching PublicWWW operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using PublicWWW Search API through Jentic.

What authentication does the PublicWWW Search API use?

The PublicWWW Search API authenticates with a Bearer token in the Authorization header, per its OpenAPI spec. Tokens come from your PublicWWW API profile page or through OAuth 2.1, need a paid plan, and are not accepted in the query string. Through Jentic the token is stored once and injected at call time, so it never appears in your agent's prompt or logs.

What are the rate limits for the PublicWWW Search API?

The OpenAPI spec states at most 10 requests per minute per account, and a request over that limit gets a 429 response with Retry-After. Searches also count against your plan's daily quota, which resets at UTC midnight, and GET /v1/account reports how much you have used today.

Can I extract emails from the sites my search finds?

Yes. Save the search as a cluster with POST /v1/clusters, then call GET /v1/clusters/{id}/extract with presets such as email,phone or your own PCRE regex. Extraction runs up to 1000 domains per call and returns next_offset to continue, and it spends extraction points from your daily allowance.

How do I search website source code with the PublicWWW Search API through Jentic?

Search Jentic for 'find websites using a code fragment', which returns GET /v1/search with its input schema, then pass your query in PublicWWW syntax, for example a quoted script URL with site:de. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a PublicWWW MCP server?

You don't need an MCP server to give your agent the PublicWWW Search API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, with operations found on demand so no extra server's tool definitions sit in its context.

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

Yes. Write a rule that allows only the search operations and GET /v1/account, so the agent can run searches and watch its quota but cannot rename, combine, or permanently delete your saved clusters, and every call it makes is logged.

PublicWWW Search API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentCompany Databearer12 EndpointsREST

For Agents

Find websites whose page source contains a code fragment such as an analytics id or script URL, save the matches as a cluster, combine clusters, and extract emails, phones, or regex matches from those sites. Requires a paid PublicWWW plan.

Use for: Find all websites that load the Shopify checkout script, Search for sites whose source contains the Google Analytics id UA-12345, Create a cluster of German sites that use a specific WordPress plugin, Combine two clusters to keep only sites that use both technologies

Not supported: Does not handle live website crawling on demand, uptime monitoring, or email verification. Use for searching indexed website source code and working with saved site clusters only.

The PublicWWW Search API searches the HTML, JavaScript, and CSS source of hundreds of millions of websites and returns the sites whose code contains a given fragment, such as a tracking id, script tag, or framework signature. It saves result sets as clusters in your account, combines clusters with and, or, and diff, and extracts values like emails and phone numbers from the page source of every site in a cluster. Results come back as json, ndjson, xml, csv, tsv, or txt, and searches count against your plan's daily quota.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

47%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

59%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B+Signals: 1

69%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the PublicWWW Search API to your agent

Capabilities

Start building with PublicWWW Search API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

PublicWWW Search API

Jentic AI Readiness Score

PublicWWW Search API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness