The dictionary agents call.
immit's English and Japanese dictionary over one REST API, with a free tier and a key in a minute.
- Start free, no card
- Burst and quota headers on every response
- Additive changes only under /v1
- x-ratelimit-remaining: 59
- x-quota-remaining: 999
- cache-control: private, max-age=3600
One entry, two ways
What a learner sees in immit, and what your client receives. Same row, same fields.
- 喰べるrare kanji
- 1to eat, to have (a meal)
- 毎日野菜を食べるようにしている。I try to eat vegetables every day.
- 昼ご飯はもう食べましたか。Have you had lunch yet?
- 子供のころは魚が食べられなかった。When I was a child, I couldn't eat fish.
- 2to make a living, to live on, to get by
- 彼は音楽で食べている。He makes a living from music.
- この給料では家族四人が食べていけない。A family of four can't get by on this salary.
- 小説を書くだけで食べるのは難しい。It's hard to make a living from writing novels alone.
Show word forms・verbHide word forms・verb
One shape, two languages
Every entry carries the same fields whether the headword is English or Japanese, so a client renders both with one component.
Every form resolves
Look up the form a reader met and get the base form and the whole table back, so a client never deinflects.
Audio, pitch accent, frequency
Pronunciation audio, Japanese pitch accent, parallel example sentences and a frequency rank on every entry.
What an entry carries
The same fields for both languages. What a language does not have is null or empty, never missing.
| What it holds | eng | jpn |
|---|---|---|
headwordlang | Yes | Yes |
senses[] | Yes | Yes |
inflections[] | Yes | Yes |
pronunciations[]sounds[] that carry a playable mp3_url. | Yes | Yes |
spellings[] | rare | Yes |
relations[] | Yes | Yes |
frequency_rank | Yes | Yes |
Three endpoints
- GET/v1/dictionary/{lang}/entries
Search by headword prefix, inflected surface form or reading, ranked the way immit ranks.
- GET/v1/dictionary/{lang}/entries/{headword}
One entry with every sense, inflection, pronunciation and relation.
- GET/v1/me
The calling key, its account's tier and quota, and today's usage.
Built for agents too
llms.txt and llms-full.txt
The whole reference in one fetch, generated from the same source as these pages, so an agent can write a working client from it alone.
openapi.yaml
The v1 spec with the bearer scheme and the production server. Generate a typed client in any language.
MCP serverPlanned
The same two lookups as tools, so an agent builder adds the dictionary with one line of config and one key.
Pricing
Free
Free
- Requests a day
- 1,000
- Requests a minute
- 60
Developer
$29/ month
- Requests a day
- 50,000
- Requests a minute
- 300
Business
$199/ month
- Requests a day
- 500,000
- Requests a minute
- 1,000