Install Jentic One Beta

Connect the ClawFetch to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ClawFetch, 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%2Fclawfetch.ai%2Fclawfetch" | 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%2Fclawfetch.ai%2Fclawfetch" | 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 ClawFetch API.

Fetch any URL with stealth page fetching, or render a JavaScript-heavy page in a headless browser

Extract typed, structured JSON from specialized site extractors

Run multi-source web research across a topic or company

Check bulk domain name availability and brainstorm available names with live WHOIS

Parse a document and list the available extractors

GET STARTED

Start building with ClawFetch API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use ClawFetch API for, with concrete tasks.

★ Agent-Ready Web Fetching

Give an agent clean data from pages that normally block or require JavaScript. The agent fetches a URL with stealth fetching, renders a single-page app in a headless browser when needed, and pulls typed JSON from a specialized extractor instead of raw HTML. This hands the model structured fields rather than a page it must parse.

Render a JavaScript-heavy page, then extract structured JSON from it

Research and Domain Screening

Gather intelligence and check names in one place. The agent runs multi-source research on a company or topic, parses a supporting document, and screens candidate domain names for availability with live WHOIS. The research and domain operations return structured results an agent can rank.

Run research on a company, then check availability for a list of candidate domains

AI Agent Integration via Jentic

An AI agent discovers and calls ClawFetch through Jentic. The agent searches by intent, receives the matching operation and its input schema, and fetches or extracts a page. Because ClawFetch is keyless and paid per request, the agent calls it directly through your own instance with nothing to configure first.

Search Jentic for 'fetch a web page', load the operation schema, and fetch the URL

Key Endpoints

9 endpoints — the clawfetch api turns the open web into agent-ready data.

METHOD

PATH

DESCRIPTION

POST

/fetch

Fetch a URL with stealth page fetching

POST

/render

Render a JavaScript-heavy page in a headless browser

POST

/extract

Extract typed JSON from a specialized site extractor

POST

/research

Run multi-source web research

POST

/domains/check

Check bulk domain availability via WHOIS

GET

/extractors

List the available structured-data extractors

POST

/fetch

Fetch a URL with stealth page fetching

POST

/render

Render a JavaScript-heavy page in a headless browser

POST

/extract

Extract typed JSON from a specialized site extractor

POST

/research

Run multi-source web research

POST

/domains/check

Check bulk domain availability via WHOIS

GET

/extractors

List the available structured-data extractors

Why Jentic?

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

Setup

Wiring ClawFetch by hand means handling x402 USDC micropayments on Base and the stealth-fetch and extraction request shapes yourself. Through Jentic you install once, import ClawFetch from the API Directory, and your agent calls it directly, with no key to create.

Permission scoping

ClawFetch needs no key, and through Jentic you still choose which of its operations your agent may call, such as fetching and extracting pages, while leaving the domain availability lookups out of the set.

Credential isolation

ClawFetch needs no API key, account, or subscription: it charges per request in USDC through the x402 protocol, so there is no secret for Jentic to hold. Your agent calls it directly through your own Jentic One instance.

Intent-based discovery

Agents search Jentic by intent such as 'fetch a web page' or 'extract structured data', and Jentic returns the matching ClawFetch operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using ClawFetch API through Jentic.

What authentication does the ClawFetch API use?

The ClawFetch API requires no API key, account, or subscription, per its OpenAPI spec. Calls are paid per request in USDC through the x402 protocol instead. Through Jentic your agent calls it directly from your own instance, with nothing to register first.

Is there a ClawFetch MCP server?

You do not need a separate MCP server to give your agent ClawFetch. Jentic connects it directly from the API Directory: import it, and your agent calls its fetch, render, and extract operations on demand. Operations are discovered as needed, so no extra server's tool definitions load into the agent's context.

Can I extract structured data from a page with the ClawFetch API?

Yes. Call the extract operation to get typed JSON from a specialized site extractor, or render a JavaScript-heavy page first and then extract from it. The extractors operation lists which specialized sites are supported.

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

Yes. ClawFetch needs no key, and because you run Jentic One yourself your rules still decide which operations the agent may call. You can allow fetching and extracting pages while withholding the domain availability lookups, and every call is logged.

What are the rate limits for the ClawFetch API?

The OpenAPI spec does not specify rate limits; ClawFetch is pay-per-request in USDC through the x402 protocol, with no account tier to exceed. See the ClawFetch documentation at https://clawfetch.ai for current terms.

How do I fetch a web page with the ClawFetch API through Jentic?

Search Jentic for 'fetch a web page' to get the matching ClawFetch operation and its input schema, then your agent passes the URL and reads the returned content. To run it on your own infrastructure, install Jentic One from its GitHub repo.

ClawFetch

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentData Transformationnone9 EndpointsREST

For Agents

Fetch and render web pages, extract typed JSON from specialized site extractors, run web research, and screen domains, across 9 keyless endpoints paid per request.

Use for: Fetch the HTML of a web page, I need to render a JavaScript-heavy page, Extract structured data from a GitHub repository page, Run multi-source research on a company

Not supported: Does not store crawled data long term, run scheduled crawl jobs, or manage proxy pools. Use for on-demand web fetching, rendering, extraction, research, and domain screening only.

The ClawFetch API turns the open web into agent-ready data. It fetches any URL with stealth page fetching, renders JavaScript-heavy pages in a headless browser, and extracts typed JSON from specialized site extractors such as GitHub, YouTube, and Wikipedia. It also runs multi-source web research across a topic or company, parses documents, and screens domain name availability with live WHOIS. There is no account or API key: calls are paid per request in USDC through the x402 protocol.

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

14%

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: C-Signals: 4

16%

Example Density

How richly the API is illustrated with examples.

44%

Example Validity

Percentage of examples that conform to their schemas.

47%

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

54%

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.

53%

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.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

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: A+Signals: 1

92%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the ClawFetch to your agent

Capabilities

Start building with ClawFetch API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

ClawFetch

Jentic AI Readiness Score

ClawFetch

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