Install Jentic One Beta

Connect the Contrie API to your agent

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

Fetch a URL and return structured data or readable markdown with quality scoring

Extract structured data or markdown from raw HTML you already hold

Verify extracted values against the page they claim to come from

Search a curated reference index for a question

GET STARTED

Start building with Contrie API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Contrie API for, with concrete tasks.

★ Agent-grade page reading

An AI agent connected through Jentic calls the scrape operation to turn an arbitrary URL into structured data or markdown it can reason over, instead of loading a full HTML page into its context. Contrie attaches source evidence and a quality score so the agent knows how much to trust each field.

Scrape a given product URL and return the title, price, and availability as structured fields with their evidence

Extraction verification

Teams that already scrape pages elsewhere use the verify operation to confirm that a value genuinely appears on the page it is attributed to, reducing silent drift. Contrie checks the extracted data against the live page and returns a verdict the pipeline can gate on.

Verify that a previously extracted price value still appears on the source page and return the result

Single-page change monitoring

An agent registers a monitor that watches one page for one question, such as whether a job posting is still open, and reads back retained events over time. This keeps a lightweight watch without re-scraping the whole site on every check.

Create a monitor for a careers page that watches whether a named role is still listed

Key Endpoints

16 endpoints — the contrie api fetches a web page and returns either accepted structured data or readable markdown, with source evidence and quality scoring attached.

METHOD

PATH

DESCRIPTION

POST

/api/v1/scrape

Fetch a URL and extract structured data or markdown

POST

/api/v1/extract

Extract structured data or markdown from raw HTML

POST

/api/v1/verify

Check extracted data against the source page

POST

/api/v1/search

Search the curated reference index

POST

/api/v1/monitors

Create a monitor that watches one page for one question

GET

/api/v1/account/status

Check account credits and current restrictions

POST

/api/v1/scrape

Fetch a URL and extract structured data or markdown

POST

/api/v1/extract

Extract structured data or markdown from raw HTML

POST

/api/v1/verify

Check extracted data against the source page

POST

/api/v1/search

Search the curated reference index

POST

/api/v1/monitors

Create a monitor that watches one page for one question

GET

/api/v1/account/status

Check account credits and current restrictions

Why Jentic?

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

Setup

Wiring the Contrie API by hand means issuing a bearer token, learning which endpoints are public versus authenticated, and handling its credit and evidence model yourself. Through Jentic you install once, import Contrie from the API Directory, store the token once, and your agent calls it.

Permission scoping

Contrie's read operations carry their target in the request body, not the URL path, so rules bound which operations your agent may call, not which page. You choose the operations it may call, so it can scrape and extract without being able to create monitors or run the curated search unless you add those.

Credential isolation

Your Contrie 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 'extract data from a page' or 'verify a scraped value', and Jentic returns the matching Contrie operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Contrie API through Jentic.

What authentication does the Contrie API use?

The Contrie API authenticates with a bearer token sent in the Authorization header, per its OpenAPI spec, and a few endpoints such as evidence verification are public. Through Jentic the token is stored once by your own self-hosted instance and injected when a call runs, so it never appears in the agent's prompt or logs.

Can I extract structured data from raw HTML with the Contrie API?

Yes. Send the HTML to the extract operation and Contrie returns structured data or readable markdown without re-fetching the page. If you only have a URL, use the scrape operation instead, which fetches the page first and attaches source evidence.

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

Yes. Write a rule that allows only the scrape and extract operations, so the agent can read pages but cannot create monitors or spend credits on the curated search, and every call it makes is logged. Add more operations only when the agent needs them.

What are the rate limits for the Contrie API?

The spec documents per-plan limits of 10, 30, and 100 requests per minute per account across its keys on the Free, Builder, and Pro plans, along with monthly credit caps. Check the Contrie documentation for the current figures before running high-volume extraction.

Is there a Contrie MCP server?

You don't need an MCP server to give your agent the Contrie API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls operations like scrape and verify on demand without loading another server's tool definitions into its context.

How do I read a web page with the Contrie API through Jentic?

Search Jentic by intent such as 'turn a web page into structured data', and Jentic returns the scrape operation with its input schema so your agent passes the URL and reads back structured fields and evidence. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Contrie API

AI ReadinessFoundational (C)54/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentData Transformationbearer16 EndpointsREST

For Agents

Fetch a URL or raw HTML and get back structured data or readable markdown with source evidence, verify extracted values against the page, and watch a page for a single question.

Use for: Fetch this product page and return its price and availability as structured data, Turn this URL into clean markdown for the model to read, Extract the author and publish date from this raw HTML, Check whether the extracted price still matches the live page

Not supported: Does not handle whole-site crawling, headless browser automation, or proxy rotation. Use for single-page extraction, verification, and monitoring only.

The Contrie API fetches a web page and returns either accepted structured data or readable markdown, with source evidence and quality scoring attached. It can extract the same structured data or markdown from raw HTML you already hold, verify extracted values against the page they claim to come from, and search a curated reference index. Agents can also register a monitor that watches a single page for a single question and keep an eye on account credits. Each extraction carries signed evidence packets so a downstream reader can confirm where a value came from.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D+Signals: 4

94%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

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.

70%

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

34%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

69%

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.

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: D-Signals: 1

41%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Contrie API to your agent

Capabilities

Start building with Contrie API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Contrie API

Jentic AI Readiness Score

Contrie 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