Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the OwlBot Dictionary 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%2Fowlbot.info%2Fowlbot" | 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%2Fowlbot.info%2Fowlbot" | 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 OwlBot Dictionary API.
Look up dictionary definitions for English words
Retrieve part of speech classification (noun, verb, adjective, etc.)
Get multiple definitions for words with different senses or meanings
Access example sentences demonstrating word usage in context
Retrieve pronunciation guides for words
GET STARTED
Handle word not found scenarios with clear error responses
Patterns agents use OwlBot Dictionary API for, with concrete tasks.
★ Writing Assistant and Editor Integration
Enhance writing tools with inline dictionary definitions. When a user hovers over or selects a word, GET /dictionary/{word} retrieves the definition, part of speech, and examples. Display this in a tooltip or sidebar to help writers choose precise vocabulary, understand unfamiliar terms, or verify word usage without leaving the editor. Integrate with Grammarly-style assistants, markdown editors, or document processors to provide contextual language support.
GET /dictionary/{word} when user hovers over or selects text. Parse response for definition, type, and examples, then display in editor UI.
Language Learning and Vocabulary Building
Build vocabulary flashcard apps, language learning platforms, or quiz systems using OwlBot definitions. Retrieve word definitions, parts of speech, and example sentences to create study materials. Generate quizzes where users match words to definitions or parts of speech. Track learning progress by testing comprehension of words retrieved from the API. This powers spaced repetition systems, vocabulary trainers, and educational content generation.
GET /dictionary/{word} for each vocabulary item, then generate flashcards with definition on one side and word on the other. Include part of speech and example sentences for context.
Content Moderation and Text Analysis
Validate words in user-generated content against a dictionary to detect misspellings, gibberish, or non-words. GET /dictionary/{word} returns 404 for non-existent words, allowing moderation systems to flag potential spam, bot-generated content, or offensive masked terms. Combine with profanity filters or NLP pipelines to improve content quality and safety in forums, comments, or social platforms.
For each word in user content, GET /dictionary/{word}. Flag 404 responses as potential misspellings or non-words for moderation review or auto-correction.
Chatbot and Conversational AI Enhancement
Enable chatbots to define words on demand when users ask 'What does X mean?' or 'Define X'. GET /dictionary/{word} retrieves the definition, part of speech, and examples, which the bot formats into a natural language response. This adds educational value to conversational agents, customer support bots, or voice assistants, making them more helpful for users encountering unfamiliar terminology.
When user asks 'What does {word} mean?', GET /dictionary/{word}, then format the response as 'The word {word} is a {type} meaning: {definition}. Example: {example}'.
AI Agent for Dictionary Lookups
Let an AI agent handle dictionary queries - looking up word definitions, parts of speech, and examples. Through Jentic, the agent searches by intent ('define a word') and loads the OwlBot endpoint. API keys are injected at execution time, keeping credentials out of agent context.
Use the Jentic search query 'look up the definition of a word' to find GET /dictionary/{word}, load its schema, and execute with the word provided by the user.
1 endpoints — owlbot is a simple english dictionary api that provides word definitions, parts of speech, example sentences, and pronunciation information.
METHOD
PATH
DESCRIPTION
/dictionary/{word}
Retrieve dictionary entry for a word
/dictionary/{word}
Retrieve dictionary entry for a word
What agents get from Jentic-routed access to this vendor.
Setup
Wiring OwlBot by hand means setting the Authorization header in its exact 'Token your-api-key' format and building the single lookup call yourself. Through Jentic you install once, import the OwlBot Dictionary API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
OwlBot exposes one read-only lookup where the word travels in the URL path (/dictionary/{word}), so scope the agent to that single definition-lookup operation. Because you choose the allowed operations, the agent can only read definitions and never changes any data.
Credential isolation
Your OwlBot API key is stored once, encrypted, by your own Jentic One instance and injected in the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'look up the definition of a word' or 'get the part of speech for a word', and Jentic returns the /dictionary/{word} 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 OwlBot Dictionary API through Jentic.
What authentication does the OwlBot Dictionary API use?
The API uses API key authentication passed in the Authorization header as 'Token your-api-key'. A free tier is available. Through Jentic, API keys are stored encrypted and injected at execution time, keeping them out of agent prompts and transcripts.
Can I look up words with multiple meanings?
Yes. GET /dictionary/{word} returns an array of definitions, each with its own part of speech, definition text, and examples. Words with multiple senses (e.g., 'bank' as a financial institution vs. riverbank) will have multiple definition objects.
What happens if a word is not found?
The API returns a 404 status with an error message. This allows applications to detect misspellings, non-words, or gibberish in text validation workflows.
Is the OwlBot API free?
OwlBot offers a free tier with limited requests. Paid plans provide higher rate limits and additional features. Check the vendor's pricing page for details.
Does the API support languages other than English?
No. The OwlBot Dictionary API currently supports English words only.
Can I get audio pronunciation files?
The API returns phonetic pronunciation guides as text, not audio files. For audio pronunciation, consider integrating with text-to-speech services.
Can I limit what my agent is allowed to do with the OwlBot Dictionary API?
Yes. Because Jentic One is self-hosted and runs under your own rules, you decide which operations the agent may call, and the OwlBot Dictionary API exposes only a single read-only lookup, GET /dictionary/{word}. Scope the agent to that one definition-lookup operation so it can only read word definitions, parts of speech, examples, and pronunciation. It can never write or change any data, and your API key is injected at execution time rather than exposed to the agent.
For Agents
Retrieve English word definitions, parts of speech, examples, and pronunciation for language tools and content applications.
Use for: I need to look up the definition of a word, Get the part of speech for a specific word, Find example sentences using a word, Retrieve pronunciation information for a word
Not supported: English-only dictionary lookups - does not provide translations, thesaurus data, or etymology. Returns definitions, parts of speech, examples, and pronunciation only.
OwlBot is a simple English dictionary API that provides word definitions, parts of speech, example sentences, and pronunciation information. The API returns comprehensive dictionary entries including multiple definitions for different word senses, grammatical type classification (noun, verb, adjective, etc.), contextual usage examples, and phonetic pronunciation guides. Use it to power dictionary features in writing tools, language learning apps, chatbots, content moderation systems, or any application requiring word definitions and linguistic metadata.
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>