oxforddictionaries.com/main version 1.11.0
Developer ToolsSource Controlnone26 EndpointsREST
For Agents
Programmatically lists available domains in a bilingual dataset, lists available domains in a monolingual dataset. Covers 26 operations.
Use for: I need to lists available domains in a bilingual dataset, I want to lists available domains in a monolingual dataset, Search for corpus sentences for a given word, Find all dictionary information for a given word
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
oxforddictionaries.com/main version 1.11.0. The API exposes 26 endpoints.
Install Jentic One Beta
Connect the oxforddictionaries.com/main version 1.11.0 to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the oxforddictionaries.com/main version 1.11.0, 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.
1
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%2Foxforddictionaries.com%2Foxforddictionaries" | sh2
Step 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%2Foxforddictionaries.com%2Foxforddictionaries" | 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.
Capabilities
What an agent can do with oxforddictionaries.com/main version 1.11.0 API.
Lists available domains in a bilingual dataset
Retrieve corpus sentences for a given word
Specify GB or US dictionary for English entry search
Use Cases
Patterns agents use oxforddictionaries.com/main version 1.11.0 API for, with concrete tasks.
★ Developer Tools Operations
Use the oxforddictionaries.com/main version 1.11.0 to perform developer tools operations programmatically. The API provides 26 endpoints covering core functionality including lists available domains in a bilingual dataset, lists available domains in a monolingual dataset, retrieve corpus sentences for a given word.
Call GET /domains/{source_domains_language}/{target_domains_language} to lists available domains in a bilingual dataset
Automated Domains Management
Automate domains operations by combining multiple oxforddictionaries.com/main version 1.11.0 endpoints. Agents can lists available domains in a monolingual dataset and then retrieve corpus sentences for a given word in a single workflow.
Call GET /domains/{source_language} to lists available domains in a monolingual dataset, then verify the result
AI Agent Integration via Jentic
AI agents discover and call oxforddictionaries.com/main version 1.11.0 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 'lists available domains in a bilingual dataset', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
26 endpoints — oxforddictionaries.
METHOD
PATH
DESCRIPTION
GET
/domains/{source_domains_language}/{target_domains_language}
Lists available domains in a bilingual dataset
GET
/domains/{source_language}
Lists available domains in a monolingual dataset
GET
/entries/{source_language}/{word_id}/sentences
Retrieve corpus sentences for a given word
GET
/entries/{source_lang}/{word_id}
Retrieve dictionary information for a given word
GET
/entries/{source_lang}/{word_id}/antonyms
Retrieve words that mean the opposite
GET
/entries/{source_lang}/{word_id}/regions={region}
Specify GB or US dictionary for English entry search
GET
/entries/{source_lang}/{word_id}/synonyms
Retrieve words that are similar
GET
/entries/{source_lang}/{word_id}/synonyms;antonyms
Retrieve synonyms and antonyms for a given word
GET
/domains/{source_domains_language}/{target_domains_language}
Lists available domains in a bilingual dataset
GET
/domains/{source_language}
Lists available domains in a monolingual dataset
GET
/entries/{source_language}/{word_id}/sentences
Retrieve corpus sentences for a given word
GET
/entries/{source_lang}/{word_id}
Retrieve dictionary information for a given word
GET
/entries/{source_lang}/{word_id}/antonyms
Retrieve words that mean the opposite
GET
/entries/{source_lang}/{word_id}/regions={region}
Specify GB or US dictionary for English entry search
GET
/entries/{source_lang}/{word_id}/synonyms
Retrieve words that are similar
GET
/entries/{source_lang}/{word_id}/synonyms;antonyms
Retrieve synonyms and antonyms for a given word
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Oxford Dictionaries API by hand means targeting its demo host on port 443 and assembling its language-and-word path segments for every entry, synonym, and domain lookup. Through Jentic you install once, import the Oxford Dictionaries API from the API Directory, and your agent calls it.
Permission scoping
This API is read-only and takes the source language and word id in the URL path (/entries/{source_lang}/{word_id}), so scope the agent to the lookup operations it needs, such as entries, synonyms, antonyms, and domains. Because you choose the allowed operations, the agent only reads dictionary data and changes nothing.
Credential isolation
This spec defines no authentication scheme, so there is no credential to store, and nothing sensitive enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get the definition of a word' or 'list domains in a bilingual dataset', and Jentic returns the matching Oxford Dictionaries operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using oxforddictionaries.com/main version 1.11.0 API through Jentic.
What authentication does the oxforddictionaries.com/main version 1.11.0 use?
The oxforddictionaries.com/main version 1.11.0 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 lists available domains in a bilingual dataset with the oxforddictionaries.com/main version 1.11.0?
Yes. Use the GET /domains/{source_domains_language}/{target_domains_language} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the oxforddictionaries.com/main version 1.11.0?
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 lists available domains in a bilingual dataset through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'lists available domains in a bilingual dataset'. Jentic returns the matching oxforddictionaries.com/main version 1.11.0 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the oxforddictionaries.com/main version 1.11.0 have?
The oxforddictionaries.com/main version 1.11.0 exposes 26 endpoints covering domains, entries, filters operations.
Can I limit what my agent is allowed to do with the Oxford Dictionaries API?
Yes. Because you run Jentic One yourself, you decide which of this read-only API's operations the agent may call, so you can allow only the lookups it needs, such as retrieving a word's dictionary entry, synonyms, antonyms, corpus sentences, or available domains. Each call takes just a source language and word id in the URL path, and since every endpoint only reads data, a scoped agent changes nothing. Grant just the operations required for the task and the agent cannot reach anything else.
GET STARTED