Install Jentic One Beta

Connect the CrawlBrulee API to your agent

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

Scrape a single URL synchronously and return its extracted content

Submit an asynchronous scrape job and collect the result by job id

Build a site link map from sitemap discovery and homepage links

Render JavaScript-heavy pages before extracting their content

Route a scrape through a proxy pinned to a chosen location

GET STARTED

Start building with CrawlBrulee API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use CrawlBrulee API for, with concrete tasks.

★ Agent-Driven Web Extraction

An AI agent that needs the content of a web page can call CrawlBrulee through Jentic to scrape a URL on demand and read back clean, structured content instead of raw HTML. The agent passes the URL to the synchronous scrape operation, optionally asking it to render JavaScript first, without the developer wiring the bearer auth or proxy options by hand. Jentic returns the matching operation and its input schema so the agent scrapes inline.

Scrape https://example.com/pricing with JavaScript rendering enabled and return the extracted pricing text

Site Mapping and Asynchronous Crawling

A pipeline that needs many pages from a site can first build a link map and then scrape each URL as an asynchronous job to avoid blocking on slow pages. CrawlBrulee builds the map from sitemap discovery plus homepage links, accepts async scrape jobs with a webhook, and holds each job's status and result for retrieval by job id.

Build a link map for a site, then submit an async scrape job for each URL and poll for the results

Rendering Dynamic Pages

Content behind client-side rendering is invisible to a plain HTTP fetch, so a scraper has to run the page's JavaScript first. CrawlBrulee renders the page before extraction and can route the request through a proxy pinned to a location, so an agent retrieves the same content a browser in that region would see.

Scrape a single-page app URL with rendering on and the request routed through a proxy in a chosen location

Key Endpoints

7 endpoints — the crawlbrulee api extracts structured content from web pages, scraping a single url synchronously or submitting it as an asynchronous job you collect later by job id.

METHOD

PATH

DESCRIPTION

POST

/api/scrape

Scrape a URL synchronously

POST

/api/scrape/async

Submit an asynchronous scrape job

GET

/api/scrape/status/{job_id}

Check an async scrape job's status

GET

/api/scrape/result/{job_id}

Retrieve a completed scrape job's result

POST

/api/map

Build a site link map

GET

/api/usage

Report billing-cycle usage and credits

GET

/api/whoami

Return the token's organization identity

POST

/api/scrape

Scrape a URL synchronously

POST

/api/scrape/async

Submit an asynchronous scrape job

GET

/api/scrape/status/{job_id}

Check an async scrape job's status

GET

/api/scrape/result/{job_id}

Retrieve a completed scrape job's result

POST

/api/map

Build a site link map

GET

/api/usage

Report billing-cycle usage and credits

GET

/api/whoami

Return the token's organization identity

Why Jentic?

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

Setup

Wiring CrawlBrulee by hand means handling its bearer token auth, polling the status and result operations for async scrapes, and setting proxy and location options per request. Through Jentic you install once, import CrawlBrulee from the API Directory, store the token once, and your agent calls it.

Permission scoping

CrawlBrulee carries the target URL in the request body, so rules bound which operations your agent may call, not which site. Limit it to the scrape and map operations it needs, and leave async job submission or the account identity lookup out unless you add them.

Credential isolation

Your CrawlBrulee 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 'scrape a URL' or 'map a website', and Jentic returns the matching CrawlBrulee operation with its input schema so the agent calls the right endpoint directly.

FAQs

Specific to using CrawlBrulee API through Jentic.

What authentication does the CrawlBrulee API use?

The CrawlBrulee API authenticates with a bearer token on every operation, per its OpenAPI spec. Through Jentic the token is stored once, encrypted, by your own Jentic One instance and injected at call time, so it never reaches the agent's prompt or logs.

Is there a CrawlBrulee MCP server?

You don't need an MCP server to give your agent the CrawlBrulee API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent can scrape pages and map sites straight away.

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

Yes. CrawlBrulee carries the target URL in the request body, so a rule bounds which operations your agent may call rather than which site. Allow just the scrape and map operations it needs, and leave the account identity and usage lookups out unless you add them, and every call it makes is logged.

Can I scrape JavaScript-heavy pages with the CrawlBrulee API?

Yes. The scrape operations can render a page's JavaScript before extracting its content, so client-side-rendered pages return the same content a browser would see rather than an empty shell. You can also route the request through a proxy pinned to a location.

What are the rate limits for the CrawlBrulee API?

The spec exposes a usage operation that reports your total, used, and available credits for the billing cycle, but it does not publish a fixed requests-per-second ceiling. Check the CrawlBrulee documentation for the current limits on your plan.

How do I scrape a page with the CrawlBrulee API through Jentic?

Search Jentic for an intent like 'scrape a URL and return its content' and it returns the CrawlBrulee scrape operation with its input schema, so your agent sends the URL and reads back the extracted content. To run it on your own infrastructure, install Jentic One from its GitHub repo.

CrawlBrulee API

AI ReadinessFoundational (D-)41/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentData Transformationbearer7 EndpointsREST

For Agents

Scrape a URL synchronously or as an async job, map a site's links, and collect results by job id, returning extracted page content as structured data. Authenticates with a bearer token and supports JavaScript rendering and proxy routing.

Use for: Scrape this URL and return the main content, Submit an async scrape job and collect the result later, Map all the links on a website, Get the result of a completed scrape job

Not supported: Does not handle data warehousing, scheduled recurring crawls, or browser automation. Use for on-demand web scraping and site mapping only.

The CrawlBrulee API extracts structured content from web pages, scraping a single URL synchronously or submitting it as an asynchronous job you collect later by job id. It builds a site link map from sitemap discovery and homepage links, renders JavaScript-heavy pages before extraction, and routes requests through a proxy pinned to a location. Supporting operations report billing-cycle credit usage and the identity of the token making the call. Responses are JSON and authentication is a bearer token.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

96%

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

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.

75%

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: FSignals: 4

69%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

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

68%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the CrawlBrulee API to your agent

Capabilities

Start building with CrawlBrulee API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

CrawlBrulee API

Jentic AI Readiness Score

CrawlBrulee 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