Install Jentic One Beta

Connect the API Acre to your agent

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

Extract readable content and metadata from a web page or document

Clean, convert, and deduplicate a dataset into structured JSON

Repair and validate JSON against a generated schema

Run SEO, security, accessibility, and performance audits on a page

Look up entities against public research registries

GET STARTED

Start building with API Acre API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use API Acre API for, with concrete tasks.

★ Agent-driven content extraction

An AI agent connected through Jentic turns a URL or file into clean, structured data: it extracts the readable content or tables, then cleans and converts the result into JSON it can reason over. Because the agent discovers operations from the service catalog by intent, it can go from a raw page to structured output without a developer wiring each utility endpoint.

Extract the main content from a web page, then convert and clean the result into a structured JSON record

Data cleanup and JSON repair

The data utilities take unreliable input and make it usable: they repair malformed JSON, validate it against a generated schema, deduplicate records, and convert between formats. An agent that receives broken or inconsistent data can run it through these endpoints before continuing, so downstream steps work with well-formed, validated structures.

Repair a malformed JSON payload, generate a schema from it, and validate the repaired document against that schema

Website auditing

The web audit endpoints inspect a site for SEO, security, accessibility, and performance issues and return structured findings. An agent can run a full or targeted audit and summarize what to fix, turning a manual review checklist into a single structured report grounded in the site's actual responses.

Run an SEO audit on a given URL and return the structured list of issues found

Key Endpoints

86 endpoints — the api acre api exposes a catalog of machine-discoverable utilities that turn messy inputs into structured json: it extracts web and document content, cleans and converts datasets, repairs and validates json, and runs seo, security, and accessibility audits on a page.

METHOD

PATH

DESCRIPTION

POST

/v1/web/extract

Extract web page content

POST

/v1/document/extract

Extract document content

POST

/v1/data/clean

Clean a dataset

POST

/v1/data/convert

Convert data between formats

POST

/v1/data/json-repair

Repair malformed JSON

POST

/v1/web/seo-audit

Run a technical SEO audit

GET

/catalog

List available services

POST

/v1/web/extract

Extract web page content

POST

/v1/document/extract

Extract document content

POST

/v1/data/clean

Clean a dataset

POST

/v1/data/convert

Convert data between formats

POST

/v1/data/json-repair

Repair malformed JSON

POST

/v1/web/seo-audit

Run a technical SEO audit

GET

/catalog

List available services

Why Jentic?

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

Setup

Wiring API Acre by hand means learning its per-call x402 USDC settlement on Base and Solana and the input shape of each utility endpoint. Through Jentic you install once, import the API from the Directory, and your agent calls it.

Permission scoping

API Acre carries its inputs in the request body, so rules bound which operations your agent may call: you can allow only the web-extraction and data-cleaning operations while leaving the crypto and audit operations out unless you add them. You choose the operations it may use.

Credential isolation

API Acre needs no API key: its endpoints are open and metered per call through x402 settlement. Jentic One still runs each call from your own self-hosted instance, so request contents stay out of the agent's prompt, logs, and context.

Intent-based discovery

Agents search Jentic by intent such as 'extract web content' or 'repair JSON', and Jentic returns the matching API Acre operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using API Acre API through Jentic.

What authentication does API Acre use?

API Acre's endpoints require no API key per its OpenAPI spec; paid operations settle per call through x402 USDC on Base and Solana. Through Jentic each call runs from your own self-hosted instance, so request contents stay out of the agent's prompt and logs.

Can I extract and clean data with API Acre?

Yes. You can extract content from a web page or document, then clean, convert, deduplicate, repair, and validate the result into structured JSON. The service catalog lists every available utility so an agent can pick the right one for a task.

Is there an API Acre MCP server?

You do not need an MCP server to give your agent API Acre. Jentic connects it directly from the API Directory: import the API and your agent calls its utilities on demand, discovering operations by intent without loading another server's tool definitions into its context.

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

Yes. Write a rule that allows only the web-extraction and data-cleaning operations, so the agent can turn pages and datasets into JSON but cannot call the crypto or audit operations unless you add them, and every call it makes is logged for review. API Acre carries its inputs in the request body, so rules bound which operations the agent may call.

What are the rate limits for API Acre?

The OpenAPI spec does not state numeric rate limits for API Acre; paid operations are metered per call through x402 settlement instead. Check the vendor documentation at https://apiacre.com for current limits before running large batches.

How do I extract web content with API Acre through Jentic?

Search Jentic for an intent such as 'extract content from a web page', and it returns the matching operation with its input schema so your agent passes the URL and options correctly. To run it on your own infrastructure, install Jentic One from its GitHub repo.

API Acre

AI ReadinessFoundational (C-)52/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentData Transformationnone86 EndpointsREST

For Agents

Extract web and document content, clean and convert datasets, repair and validate JSON, and run site audits, returning structured JSON with per-call x402 settlement.

Use for: I need to extract the main content from a web page, Clean and normalize this messy dataset, Convert a CSV into structured JSON, Repair this broken JSON so it parses

Not supported: Does not host data, run scheduled jobs, or store state between calls. Use for per-call web, document, and data transformation and audits only.

The API Acre API exposes a catalog of machine-discoverable utilities that turn messy inputs into structured JSON: it extracts web and document content, cleans and converts datasets, repairs and validates JSON, and runs SEO, security, and accessibility audits on a page. It also covers research lookups against public registries and read-only EVM utilities on Base and Solana. Every paid operation is metered per call through x402 USDC settlement, and agents can start from a discovery endpoint that lists the available services.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D+Signals: 4

91%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

49%

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

38%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

29%

OperationId Quality

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

51%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

88%

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

72%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the API Acre to your agent

Capabilities

Start building with API Acre API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

API Acre

Jentic AI Readiness Score

API Acre

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