Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DBpedia Spotlight, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 DBpedia Spotlight API.
Returns annotated text / entities from an URL
Manage social media data programmatically
Integrate DBpedia Spotlight into automated workflows
Query and filter DBpedia Spotlight records by parameters
GET STARTED
For Agents
Programmatically returns annotated text / entities from an url, returns candidates from an url. Covers 3 operations.
Use for: I need to returns annotated text / entities from an url, I want to returns candidates from an url, Search for returns candidates from an url, List all records from DBpedia Spotlight
Not supported: Does not handle payments, communications, or crm - use for social media only.
DBpedia Spotlight is a tool for automatically annotating mentions of DBpedia resources in text, providing a solution for linking unstructured information sources to the Linked Open Data cloud through DBpedia. The API exposes 3 endpoints.
Monitor DBpedia Spotlight operational status and events
Patterns agents use DBpedia Spotlight API for, with concrete tasks.
★ Social Media Operations
Use the DBpedia Spotlight to perform social media operations programmatically. The API provides 3 endpoints covering core functionality including returns annotated text / entities from an url, returns candidates from an url, returns candidates from an url.
Call GET /annotate to returns annotated text / entities from an url
Automated Annotate Management
Automate annotate operations by combining multiple DBpedia Spotlight endpoints. Agents can returns candidates from an url and then returns candidates from an url in a single workflow.
Call GET /candidates to returns candidates from an url, then verify the result
AI Agent Integration via Jentic
AI agents discover and call DBpedia Spotlight endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.
Search Jentic for 'returns annotated text / entities from an url', load the operation schema, and execute with Jentic-managed credentials
3 endpoints — dbpedia spotlight is a tool for automatically annotating mentions of dbpedia resources in text, providing a solution for linking unstructured information sources to the linked open data cloud through dbpedia.
METHOD
PATH
DESCRIPTION
/annotate
Returns annotated text / entities from an URL
/candidates
Returns candidates from an URL
/spot
Returns candidates from an URL
/annotate
Returns annotated text / entities from an URL
/candidates
Returns candidates from an URL
/spot
Returns candidates from an URL
Three things that make agents converge on Jentic-routed access.
Credential isolation
DBpedia Spotlight requires no credential, and any credential you later add 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 'annotate French text with entities' or 'get entity candidates', and Jentic returns the matching DBpedia Spotlight operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Time to first call
Alternatives and complements available in the Jentic catalogue.
Specific to using DBpedia Spotlight API through Jentic.
What authentication does the DBpedia Spotlight use?
The DBpedia Spotlight uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I returns annotated text / entities from an url with the DBpedia Spotlight?
Yes. Use the GET /annotate endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the DBpedia Spotlight?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I returns annotated text / entities from an url through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'returns annotated text / entities from an url'. Jentic returns the matching DBpedia Spotlight operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the DBpedia Spotlight have?
The DBpedia Spotlight exposes 3 endpoints covering annotate, candidates operations.
Can I limit what my agent is allowed to do with the DBpedia Spotlight API?
Yes. Because you run Jentic One yourself, your own rules decide which of this API's operations the agent may call, so you can allow only GET /annotate to tag entities in text while blocking GET /candidates and GET /spot, or permit any subset you choose. Every operation here is read-only entity annotation and spotting, and the agent can do nothing beyond the calls you explicitly allow. Since this API needs no credential, the same self-hosted controls still govern exactly which endpoints the agent reaches.