Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Andi AI Search 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%2Fandiai.com%2Fandiai" | 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%2Fandiai.com%2Fandiai" | 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 Andi AI Search API.
Search the web with query operators and domain and date filtering, via GET or a JSON POST body
Return results in multiple output formats, including a context format of markdown for language models
Fetch and extract the content of a single web page
Pull a curated, ranked news feed for one of 26 fixed topics with no query required
GET STARTED
Ground an agent's answers in current web content through retrieval-ready results
Patterns agents use Andi AI Search API for, with concrete tasks.
★ Grounding an Agent in Live Web Results
An agent answering a question that needs current information can run a search and request the context output format, which returns markdown shaped for language models, then feed those results straight into its prompt. Query operators plus domain and date filtering let the agent narrow to trustworthy, recent sources before grounding. This gives a retrieval-augmented answer without the agent operating its own crawler or index.
Search for a question with a date filter for the last month, request the context format, and pass the returned markdown results to the model as grounding.
Fetching a Specific Page
When an agent already has a URL, the fetch operation retrieves and extracts the single page's content so the agent reads clean text instead of raw HTML. This suits following a citation, reading a documentation page, or extracting an article the agent found through search. One call turns a link into usable content.
Fetch a specific article URL, extract its main content, and summarise it for the user.
Curated Topic News Feeds
The news operation returns a ranked feed for one of 26 fixed topics without requiring a query, so an agent can surface the latest items in a subject area in a single call. Because the topics are fixed and the feed is curated and ranked, the agent gets a stable, low-effort way to monitor a domain. It suits briefings and recurring digests.
Pull the ranked news feed for a chosen fixed topic and compile the top items into a short briefing.
4 endpoints — the andi ai search api searches the web, fetches and extracts single pages, and serves curated news feeds for people and ai agents.
METHOD
PATH
DESCRIPTION
/api/v1/search
Search the web with query operators and filters
/api/v1/search
Search the web with a JSON request body
/api/v1/fetch
Fetch and extract a single web page
/api/v1/news/{topic}
Get a curated, ranked news feed for a fixed topic
/api/v1/search
Search the web with query operators and filters
/api/v1/search
Search the web with a JSON request body
/api/v1/fetch
Fetch and extract a single web page
/api/v1/news/{topic}
Get a curated, ranked news feed for a fixed topic
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Andi AI Search API by hand means creating a key in the API Console and sending it in the x-api-key header on search, fetch, and news calls, and choosing the right output format for each. Through Jentic you install once, import it from the API Directory, store the key once, and your agent searches, fetches, and reads news.
Permission scoping
A rule can allow your agent only the operations it needs, such as search and page fetch, so it can read the web while you leave out whatever you do not want. The news feed takes the topic in the URL path (/api/v1/news/{topic}), so you can allow that read as its own operation, and rules bound which operations run.
Credential isolation
Your Andi API key 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 'search the web' or 'fetch a page as markdown', and Jentic returns the matching Andi operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Andi AI Search API through Jentic.
What authentication does the Andi AI Search API use?
Per its OpenAPI spec the Andi AI Search API uses an API key sent in the x-api-key header, which you create in the API Console. The key applies to the search, fetch, and news operations alike, so every call carries it in that header.
Can I get search results formatted for a language model with the Andi AI Search API?
Yes. The search and fetch operations support a context output format that returns markdown suited to language models, so you can pass results straight into a prompt. Search also supports query operators and domain and date filtering to narrow to the sources you want before grounding.
What are the rate limits for the Andi AI Search API?
The OpenAPI spec does not publish numeric rate limits for the Andi AI Search API. For current limits check the API Console and vendor documentation at https://console.andiai.com.
How do I run a web search with the Andi AI Search API through Jentic?
Import the Andi AI Search API from the Jentic API Directory, then have your agent search by intent such as 'search the web for recent results' and Jentic returns the search operation with its input schema. The agent runs the query, requests the context format, and grounds its answer in the results. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the Andi AI Search API?
Yes. Write a rule that allows only the operations the agent needs, such as search and page fetch, so it can read the web but you leave out the news feed if it is not wanted. The news feed takes the topic in the URL path, so you can allow that read as its own operation, and every call the agent makes is logged.
Is there an Andi AI Search MCP server?
You don't need an MCP server to give your agent the Andi AI Search API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the search, fetch, and news operations on demand without loading another server's tool definitions into its context.
What topics does the news feed cover in the Andi AI Search API?
The news operation returns a curated, ranked feed for one of 26 fixed topics, selected by naming the topic in the path, and it requires no search query. The feed is returned as JSON rather than the context markdown format offered by search and fetch.
For Agents
Search the web with query operators and domain and date filters, fetch and extract a single page, and pull a ranked news feed for one of 26 fixed topics. A context output format returns markdown suited to grounding language models.
Use for: Search the web for recent coverage of a topic, Get search results as markdown I can feed to a language model, Fetch and extract the main content of a specific page, Filter search results to a single domain and date range
Not supported: Does not crawl entire sites, store a persistent index, or generate answers itself. Use for web search, single-page fetch, and curated topic news only.
The Andi AI Search API searches the web, fetches and extracts single pages, and serves curated news feeds for people and AI agents. Its search operation returns structured results with query operators, domain and date filtering, and multiple output formats, including a context format that returns markdown suited to language models. The fetch operation retrieves and extracts one page, and the news operation returns a ranked feed for one of 26 fixed topics with no query required. Results are built for retrieval, so an agent can ground its answers in current web content.
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>