Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the EyeLevel GroundX 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%2Feyelevel.ai%2Feyelevel" | 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%2Feyelevel.ai%2Feyelevel" | 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 EyeLevel GroundX API.
Ingest local and remote documents into a searchable bucket
Crawl a website and ingest its pages for retrieval
Run semantic search over ingested content and over documents
Organize content into buckets and combine buckets into groups
Track ingestion processing status and retry a failed stage
GET STARTED
Inspect a document's parsed X-Ray and its extracted content
Patterns agents use EyeLevel GroundX API for, with concrete tasks.
★ RAG Knowledge Base Ingestion
A team builds a retrieval knowledge base from mixed sources. The EyeLevel GroundX API ingests local uploads and remote documents, crawls a website for its pages, and stores everything in buckets, tracking processing status so an agent can wait for ingestion to finish and retry any failed stage before querying.
Ingest a remote document into a bucket, poll its processing status until complete, then confirm the document appears in the bucket
Semantic Search for Retrieval
An assistant answers questions from a private corpus. The EyeLevel GroundX API runs semantic search over a bucket's content and across documents, returning relevant passages with their source so a model can ground its answer, and groups let one query span several buckets at once.
Run a content search over a bucket for a user's question and return the top passages with their source documents
AI Agent Retrieval via Jentic
An AI agent grounds its answers through Jentic without holding the GroundX key itself. It searches by intent, receives the matching operation and its input schema, and runs ingestion and retrieval with the credential injected at run time, so a retrieval step slots into a larger agent workflow.
Search Jentic for 'search my ingested documents', load the search operation schema, and run a query with Jentic-managed credentials
52 endpoints — the eyelevel groundx api ingests documents and runs semantic search over them for retrieval-augmented generation.
METHOD
PATH
DESCRIPTION
/v1/ingest/documents/local
Ingest local documents
/v1/ingest/documents/remote
Ingest remote documents
/v1/search/documents
Search across documents
/v1/search/{id}
Search content within a bucket or group
/v1/ingest/{processId}
Get ingestion processing status
/v1/bucket
Create a bucket
/v1/ingest/document/{documentId}
Get an ingested document
/v1/ingest/documents/local
Ingest local documents
/v1/ingest/documents/remote
Ingest remote documents
/v1/search/documents
Search across documents
/v1/search/{id}
Search content within a bucket or group
/v1/ingest/{processId}
Get ingestion processing status
/v1/bucket
Create a bucket
/v1/ingest/document/{documentId}
Get an ingested document
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the EyeLevel GroundX API by hand means carrying its X-API-Key header, sequencing ingestion across local, remote, and crawl sources, and polling processing status yourself. Through Jentic you install once, import GroundX from the API Directory, store the key once, and your agent calls it.
Permission scoping
GroundX puts the bucket, group, and document ids in the URL path, so a rule can pin your agent to one bucket and the operations you pick, such as ingest and search. You choose which operations it may call, so bucket deletion and API-key management are not included unless you add them.
Credential isolation
Your GroundX 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 'ingest a document' or 'search my documents', and Jentic returns the matching GroundX 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 EyeLevel GroundX API through Jentic.
What authentication does the EyeLevel GroundX API use?
The EyeLevel GroundX API authenticates with an API key sent in the X-API-Key header per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent.
Can I crawl a website into a searchable index with the EyeLevel GroundX API?
Yes. The crawl-website ingestion operation pulls a site's pages into a bucket, alongside local and remote document ingestion. You can track the processing status of each ingestion and retry a failed stage, then search the bucket once ingestion completes.
What are the rate limits for the EyeLevel GroundX API?
The OpenAPI spec does not specify rate limits for the EyeLevel GroundX API. Check the EyeLevel developer documentation for current limits, and use the customer usage operation to read your account's consumption by metric over a time range.
How do I search my documents with the EyeLevel GroundX API through Jentic?
Search Jentic for 'search my ingested documents' and it returns the GroundX search operation with its input schema. Load the schema, pass the bucket and query, and the key is injected at run time. 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 EyeLevel GroundX API?
Yes. GroundX puts the bucket, group, and document ids in the URL path, so a rule can pin your agent to one bucket and the operations you pick. Allow ingestion and search while leaving bucket deletion, API-key management, and workflow changes out unless you add them.
Is there an EyeLevel GroundX API MCP server?
You don't need an MCP server to give your agent the EyeLevel GroundX API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the ingestion and search operations it needs without a separate server to install.
For Agents
Ingest local, remote, and crawled documents into buckets, then run semantic search over them for retrieval. Track ingestion status and read parsed document content. Authenticated with an X-API-Key header.
Use for: Ingest a document into a GroundX bucket, Search my ingested content for a question, Crawl a website and index its pages, Create a new bucket for a document set
Not supported: Does not handle model training, chat completion, or payment. Use for ingesting documents and running semantic search for retrieval only.
The EyeLevel GroundX API ingests documents and runs semantic search over them for retrieval-augmented generation. It takes local and remote documents, crawls websites, and organizes content into buckets that can be combined into groups for a single search. It tracks ingestion processing status, retries failed stages, and exposes a parsed X-Ray and extracted content per document, so an agent can build and query a knowledge base.
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>