Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Datacircle 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%2Fdatacircle.dev%2Fdatacircle" | shStep 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%2Fdatacircle.dev%2Fdatacircle" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Datacircle API.
List every benchmarked GTM API with its slug, plan and provider counts, and best plan
Get an API's plans ranked best first by score out of 100, up to 50 at a time
Search plans by provider or plan name and sort by score, provider, or price per 1,000
Look up one provider, such as bright-data, and see its plans and rank on every API it sells
GET STARTED
Compare plan details such as perThousand price, monthlyCap, perSecond limits, latencyMs, and countries
Patterns agents use Datacircle API for, with concrete tasks.
★ Agent vendor shortlist through Jentic
An AI agent asked to pick a data provider for a sales workflow needs current, comparable pricing instead of marketing pages. Through Jentic the agent searches for 'find the best provider for a GTM API', receives the Datacircle getBestPlans operation with its input schema, and calls GET /apis/{slug}/best for the API slug with a limit. It returns a ranked shortlist with each plan's score, price per 1,000, and pricing page link.
Call GET /apis to find the slug for the API the user named, then call GET /apis/{slug}/best with that slug and limit 5, and present each plan's provider, score, and perThousand price
Cheapest plan search
A founder budgeting for data costs wants the lowest unit price for one API. GET /plans takes an `api` parameter, a sort of price to order by dollars per 1,000 lowest first, and limit and offset for paging, and returns total plus the matching plans. Each plan includes fields such as monthlyCap, overagePerThousand, and billing so the true cost at volume can be worked out.
Call GET /plans with `api` set to the chosen API slug, sort 'price', and limit 10, then list provider, plan, perThousand, and monthlyCap for each result
Provider due diligence
Before signing with a provider, a buyer wants to see how it ranks across everything it sells. GET /providers/{slug} returns the provider's plans on each API with its rank on each, using the provider slug such as bright-data. Fields such as freshness, countries, latencyMs, and docs help judge fit beyond price.
Call GET /providers/{slug} with slug 'bright-data' and summarise its rank and best plan on each API it sells
4 endpoints — the datacircle api returns datacircle's benchmark of go-to-market (gtm) data apis: every api on its sheet, the providers that sell each one, and every plan scored out of 100 with the best first.
METHOD
PATH
DESCRIPTION
/apis
List the benchmarked APIs
/apis/{slug}/best
Best plans for an API by score
/plans
Search and sort plans
/providers/{slug}
One provider's plans and ranks
/apis
List the benchmarked APIs
/apis/{slug}/best
Best plans for an API by score
/plans
Search and sort plans
/providers/{slug}
One provider's plans and ranks
What agents get from Jentic-routed access to this vendor.
Setup
The Datacircle API needs no key, so hand-wiring it is mostly learning its four read operations and their sort, limit, and offset rules. Through Jentic you install once, import Datacircle from the API Directory, and your agent calls it without a credential step.
Permission scoping
Datacircle puts the API slug and provider slug in the URL path (/apis/{slug}/best, /providers/{slug}), so a rule can pin your agent to one API's rankings or one provider's page. All operations are reads, so you choose which lookups the agent may run.
Credential isolation
The Datacircle API takes no key or account, so there is nothing secret to hold. Your own Jentic One instance runs the calls and logs them like any other API.
Intent-based discovery
Agents search Jentic by intent such as 'find the best provider for a GTM API' or 'compare plan prices', and Jentic returns the matching Datacircle operation with its input schema so the agent sends the right slug and sort without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Datacircle API through Jentic.
What authentication does the Datacircle API use?
None. The Datacircle API spec declares no security scheme, and its description says no key and no account are needed. Through Jentic there is no credential to set up: the agent calls the four read operations directly.
What are the rate limits for the Datacircle API?
The API description in the OpenAPI spec states at most 60 calls a minute from one address. For bulk use, the description points to a single file at https://datacircle.dev/datacircle.json that holds every plan.
How are plans scored in the Datacircle API?
Each plan carries a score out of 100 from Datacircle's benchmark, and results are ordered best first as on the datacircle.dev sheet. GET /apis/{slug}/best returns one API's plans in that order with a rank, and GET /plans sorts by score by default, with unscored plans last.
Can I sort Datacircle plans by price?
Yes. GET /plans accepts sort set to price, which orders plans by dollars per 1,000 lowest first. You can narrow it with `api` for one API and query for words in the provider or plan name, and page with limit (1 to 50) and offset.
How do I find the best provider for an API through Jentic?
Search Jentic for 'find the best provider for a GTM API', load the getBestPlans operation, and call GET /apis/{slug}/best with the API slug from GET /apis. The agent gets plans ranked by score with their prices and pricing pages. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a Datacircle MCP server?
You don't need an MCP server to give your agent Datacircle. Jentic connects it directly from the API Directory: import it and your agent calls the four read operations on demand, with no extra tool definitions sitting in its context.
Can I limit what my agent is allowed to do with the Datacircle API?
Yes. Every Datacircle operation is a read, so the main choice is which reads to allow. A rule that allows only GET /apis/{slug}/best and GET /providers/{slug} lets the agent pull rankings and provider pages without running open-ended plan searches, and every call it makes is logged.
For Agents
Compare GTM data API providers and plans: list benchmarked APIs, get the best-scored plans for one, search plans by name or price, and see a provider's rank across APIs. No key needed.
Use for: List all the GTM APIs Datacircle benchmarks, Find the best-scored plans for an email finder API, Search for the cheapest plan per 1,000 calls for an API, Get the plans and ranks for the provider bright-data
Not supported: Does not enrich contacts, find emails, or sell data itself. Use for comparing the pricing, scores, and ranks of GTM data API providers only.
The Datacircle API returns Datacircle's benchmark of go-to-market (GTM) data APIs: every API on its sheet, the providers that sell each one, and every plan scored out of 100 with the best first. Each plan record carries pricing and limits such as price per 1,000 calls, monthly cap, throughput, latency, freshness, and countries covered, alongside the provider's website and pricing page. It can list an API's best plans, search plans by provider or plan name and sort by score, provider, or price, and show one provider's plans and rank on every API it sells. It is free to call with no key or account.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>