canonical: https://jentic.com/apis/oxforddictionaries.com/oxforddictionaries

# oxforddictionaries.com/main version 1.11.0

oxforddictionaries.com/main version 1.11.0. The API exposes 26 endpoints.

## For AI agents

Programmatically lists available domains in a bilingual dataset, lists available domains in a monolingual dataset. Covers 26 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'lists available domains in a bilingual dataset', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| 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 |

## Key resources

- **Domains** — Operations for domains
- **Entries** — Operations for entries
- **Filters** — Operations for filters
- **Grammaticalfeatures** — Operations for grammaticalFeatures
- **Inflections** — Operations for inflections

## Why Jentic

- **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 handling:** This spec defines no authentication scheme, so there is no credential to store, and nothing sensitive enters the agent's prompt, logs, or context.
- **Discovery method:** 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

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### 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.