Install Jentic One Beta

Connect the Found17 API to your agent

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

Extract a normalized product record from a public product page without inventing missing fields

Evaluate whether supplied public sources establish a claim and return the evidence

Run reproducible HTTP, HTML, SEO, and accessibility checks on a public webpage

Turn deterministic page checks into a ranked, evidence-backed website action list

Compare source-backed product records from multiple pages in one call

GET STARTED

Start building with Found17 API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Found17 API for, with concrete tasks.

★ Agent Web Verification

An AI agent connected through Jentic can extract a product record from a page, verify a claim against supplied sources, and audit the page for SEO and accessibility issues, without a developer wiring the Found17 API by hand. Found17 returns evidence-backed results without fabricating citations, so the agent acts on grounded output.

Extract a product record from a product page and verify a specific claim about it against supplied sources

Product Data Extraction

Catalog and comparison tools pull structured product data from arbitrary product pages. Found17 extracts a normalized product record from one page and compares records from several pages in a single bounded call, returning source-backed fields.

Extract product records from three product pages and compare them in one call

Website Audit

Teams check a page for reproducible HTTP, HTML, SEO, and accessibility issues and want a prioritized list of fixes. Found17 runs the checks and turns them into a ranked, evidence-backed website action list.

Run web QA checks on a webpage and return a ranked action list of issues to fix

Key Endpoints

13 endpoints — the found17 api runs deterministic, source-backed checks on public web pages: it extracts a normalized product record from a product page, evaluates whether supplied sources establish a claim, and runs reproducible http, html, seo, and accessibility checks on a page.

METHOD

PATH

DESCRIPTION

POST

/v1/web-to-product

Extract a normalized product record from a page

POST

/v1/verify-claim

Evaluate whether sources establish a claim

POST

/v1/web-qa

Run HTTP, HTML, SEO, and accessibility checks

POST

/v1/website-audit

Produce a ranked website action list

POST

/v1/compare-products

Compare product records across pages

POST

/v1/source-snapshot

Return a source-hashed page snapshot

GET

/v1/quote

Quote a service's cost

POST

/v1/web-to-product

Extract a normalized product record from a page

POST

/v1/verify-claim

Evaluate whether sources establish a claim

POST

/v1/web-qa

Run HTTP, HTML, SEO, and accessibility checks

POST

/v1/website-audit

Produce a ranked website action list

POST

/v1/compare-products

Compare product records across pages

POST

/v1/source-snapshot

Return a source-hashed page snapshot

GET

/v1/quote

Quote a service's cost

Why Jentic?

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

Setup

Wiring the Found17 API by hand means handling its pay-per-call model, authorizing each call with an x402 payment signature or a Stripe billing account header, and shaping each page request yourself. Through Jentic you install once, import Found17 from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Found17 carries the target page URL in the request body, so a rule bounds which operations your agent may call rather than which page: you can allow the extraction and audit operations and leave source-watch deletion out. You choose the operations it may call, so destructive ones like deleting a source watch are not included unless you add them.

Credential isolation

Your Found17 credential 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 a product record' or 'audit a website', and Jentic returns the matching Found17 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Found17 API through Jentic.

What authentication does the Found17 API use?

Found17 uses a pay-per-call model declared as API key headers in its OpenAPI spec: agents authorize each call with an x402 USDC payment signature on Base mainnet sent in the `PAYMENT-SIGNATURE` header, while human or business usage pairs a Stripe billing account id in the `X-Found17-Account-Id` header with a billing-mode header. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at call time.

Can I extract a product record with the Found17 API?

Yes. The web-to-product operation extracts a normalized product record from a public product page without inventing missing fields, and the compare-products operation evaluates records from several pages in one bounded call.

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

Yes. Found17 carries the target page URL in the request body, so write a rule that allows only the extraction and verification operations, such as extracting a product record and running web QA, letting the agent read and check pages but not delete a source watch. Every call it makes is logged.

Is there a Found17 MCP server?

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

What are the rate limits for the Found17 API?

The OpenAPI spec does not specify numeric rate limits for the Found17 API; usage is metered per call through its pay-per-call model. Check the Found17 documentation at https://found17.com for current limits and pricing.

How do I audit a web page with the Found17 API through Jentic?

Search Jentic for an intent like 'audit a website', and it returns Found17's web QA and website-audit operations with their input schemas so your agent can run the checks and get a ranked action list. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Found17 API

AI ReadinessFoundational (D+)50/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentData TransformationapiKey13 EndpointsREST

For Agents

Extract normalized product records from public pages, verify whether sources establish a claim, and run reproducible SEO, HTML, and accessibility checks on a webpage. Compare product records, snapshot pages with change detection, and manage public-source watches.

Use for: Extract a product record from a public product page, Verify whether these sources support a claim, Run an SEO and accessibility check on a webpage, Audit a website and get a ranked action list

Not supported: Does not host content, crawl private pages, or store a persistent dataset. Use for source-backed extraction, verification, and audits of public web pages only.

The Found17 API runs deterministic, source-backed checks on public web pages: it extracts a normalized product record from a product page, evaluates whether supplied sources establish a claim, and runs reproducible HTTP, HTML, SEO, and accessibility checks on a page. It compares product records across pages, returns a source-hashed snapshot with caller-controlled change checks, and manages time-bounded public-source watches. It also lists available services and quotes their cost before a call runs.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 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).

30%

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.

56%

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

35%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

46%

OperationId Quality

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

27%

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

50%

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: CSignals: 1

56%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Found17 API to your agent

Capabilities

Start building with Found17 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Found17 API

Jentic AI Readiness Score

Found17 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