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

# Wordnik api.wordnik.com

wordnik.com/main version 4.0. The API exposes 16 endpoints secured with apiKey authentication.

## For AI agents

Programmatically fetches audio metadata for a word., return definitions for a word. Covers 16 operations with apiKey authentication.

## Scope

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

## Capabilities

- Fetches audio metadata for a word.
- Return definitions for a word
- Integrate api.wordnik.com into automated workflows
- Query and filter api.wordnik.com records by parameters
- Monitor api.wordnik.com operational status and events

## Use cases

### Developer Tools Operations

Use the api.wordnik.com to perform developer tools operations programmatically. The API provides 16 endpoints covering core functionality including fetches audio metadata for a word., return definitions for a word, fetches etymology data.

Example prompt: Call GET /word.json/{word}/audio to fetches audio metadata for a word.

### Automated word Management

Automate word operations by combining multiple api.wordnik.com endpoints. Agents can return definitions for a word and then fetches etymology data in a single workflow.

Example prompt: Call GET /word.json/{word}/definitions to return definitions for a word, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call api.wordnik.com 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 apiKey tokens manually.

Example prompt: Search Jentic for 'fetches audio metadata for a word.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /word.json/{word}/audio | Fetches audio metadata for a word. |
| GET | /word.json/{word}/definitions | Return definitions for a word |
| GET | /word.json/{word}/etymologies | Fetches etymology data |
| GET | /word.json/{word}/examples | Returns examples for a word |
| GET | /word.json/{word}/frequency | Returns word usage over time |
| GET | /word.json/{word}/hyphenation | Returns syllable information for a word |
| GET | /word.json/{word}/phrases | Fetches bi-gram phrases for a word |
| GET | /word.json/{word}/pronunciations | Returns text pronunciations for a given word |

## Key resources

- **word** — Operations related to word
- **words** — Operations related to words

## Why Jentic

- **Setup:** Wiring the Wordnik API by hand means obtaining an API key, sending it as api_key on api.wordnik.com, and composing the per-word definition, example, and pronunciation calls yourself. Through Jentic you install once, import the Wordnik API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Wordnik puts the word in the URL path (/word.json/{word}/definitions), so a rule can pin your agent to reading data for a given word. You choose the operations it may call, so anything beyond the word lookups you allow is not included unless you add it.
- **Credential handling:** Your Wordnik API 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.
- **Discovery method:** Agents search Jentic by intent such as 'get definitions for a word' or 'fetch example sentences', and Jentic returns the matching Wordnik 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 api.wordnik.com use?

The api.wordnik.com uses an API key passed in the `api_key` query. 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 fetches audio metadata for a word. with the api.wordnik.com?

Yes. Use the GET /word.json/{word}/audio endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the api.wordnik.com?

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 fetches audio metadata for a word. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'fetches audio metadata for a word.'. Jentic returns the matching api.wordnik.com operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the api.wordnik.com have?

The api.wordnik.com exposes 16 endpoints covering word, words operations.

### Can I limit what my agent is allowed to do with the Wordnik API?

Yes. Because you run Jentic One yourself, your own rules decide which Wordnik operations and credentials your agent can use. Wordnik puts the word in the URL path, such as GET /word.json/{word}/definitions, so you can allow only the read lookups you want (definitions, examples, or pronunciations) and leave out anything you have not permitted. The agent can call only the operations you enable, and your API key is injected at execution time rather than exposed to the agent.