canonical: https://jentic.com/apis/funtranslations.com/funtranslations-index

# FunTranslations API

The FunTranslations API is the umbrella service that exposes every translator on funtranslations.com through a single OpenAPI surface, covering Morse code, Braille, regional dialects, fictional character speak, and Star Wars and Star Trek alien tongues. Each of the 36 GET endpoints under /translate accepts a text query parameter and returns the translated result as JSON, with consistent success and 401 error envelopes. All operations authenticate with the X-Funtranslations-API-Secret header and share a single tier-based subscription quota. The API is designed for novelty apps, accessibility utilities, fan content, and educational tools that need rapid text transformation without hosting language models.

## For AI agents

Translate English text into 36 different output styles spanning Morse, Braille, dialects, character speak, and Star Wars and Star Trek languages from a single authenticated endpoint family.

## Scope

Does not handle real human language translation between major world languages, speech recognition, or content moderation - use for novelty, fictional, dialect, Morse, and Braille text transformation only.

## Capabilities

- Translate English into 36 distinct outputs including Yoda, Sith, Klingon, Pirate, Cockney, Minion, and Morse from one endpoint family
- Convert text to Morse code as text or as a downloadable WAV audio response with configurable speed and tone
- Render Braille across five formats including display characters, dot patterns, Unicode glyphs, HTML entities, and image markup
- Decode Morse code back to English using the dedicated `/translate/morse2english` operation
- Apply regional dialect transformations such as Brooklyn, Cockney, Jive, and Valspeak to user-supplied text
- Generate fictional language translations for Dothraki, Klingon, Huttese, Mandalorian, Cheunh, and Gungan from one consistent contract

## Use cases

### Multi-Style Novelty Translator App

Power a single web or mobile novelty app that lets users pick from dozens of translation styles by routing each request to the matching `/translate/{style}` endpoint. The shared authentication header and consistent response envelope mean a thin client can handle Yoda, Pirate, Minion, and Klingon outputs without per-endpoint adapters. Total integration is typically a single afternoon.

Example prompt: Call GET `/translate/yoda` with text='I am hungry' then GET `/translate/pirate` with the same text and return both translated strings.

### Morse Code Learning Aid

Build a Morse practice tool that uses GET `/translate/morse` to convert sentences to dits and dahs, GET `/translate/morse/audio` to play them back at a chosen WPM and tone frequency, and GET `/translate/morse2english` to grade what the learner thinks they heard. The audio endpoint returns a base64 WAV that can be played directly in the browser.

Example prompt: Call GET `/translate/morse/audio` with text='SOS', speed=15, tone=700 and return the base64 audio for playback.

### Accessibility Utility for Braille Rendering

Use the five `/translate/braille` endpoints to display Braille in different surfaces - Unicode glyphs in a terminal, HTML entities in a web page, image tags for visual reference, dot numbers for tactile hardware, or raw display characters for refreshable Braille hardware. One subscription unlocks every output format.

Example prompt: Call GET `/translate/braille/unicode` with text='Hello' and return the Unicode Braille glyphs.

### Agent Style Transformer via Jentic

An AI agent receives a request such as 'rewrite this announcement in Pirate speak' and uses Jentic to discover the matching `/translate/pirate` operation, load its single text parameter, and return the styled string. Because all 36 styles share the same shape, the agent can handle any future style request without updating its tool list.

Example prompt: Search Jentic for 'translate to pirate speak', load `/translate/pirate`, and execute it with the user's input text.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/translate/yoda` | Translate English to Yoda speak |
| GET | `/translate/morse` | Translate English to Morse code |
| GET | `/translate/morse/audio` | Generate Morse code audio at chosen speed and tone |
| GET | `/translate/braille/unicode` | Translate English to Braille Unicode glyphs |
| GET | `/translate/klingon` | Translate English to Klingon |
| GET | `/translate/pirate` | Translate English to Pirate speak |

## Key resources

- **Morse** — English-to-Morse, Morse-to-English, and Morse audio generation endpoints with configurable speed and tone.
- **Braille** — Five output formats - display characters, dot patterns, Unicode, HTML entities, and image markup - under `/translate/braille`/*.
- **Starwars** — Yoda, Sith, Cheunh, Huttese, Mandalorian, and Gungan translators under `/translate/{language}.`
- **Characters** — Character-speak translators including Minion, Chef, Fudd, Ferb Latin, and Dolan.
- **Dialect** — Regional dialect transformations such as Brooklyn, Cockney, Jive, and Valspeak.

## Why Jentic

- **Setup:** Wiring the FunTranslations API by hand means configuring its secret-key request header auth against api.funtranslations.com and mapping the many novelty, Morse, and Braille translation endpoints yourself. Through Jentic you install once, import the FunTranslations API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The source text travels as a request parameter rather than a URL path resource, so scope this by operation: limit the agent to the operations it needs, such as a Yoda or pirate translation, and leave the transforms you do not want it calling out of the allowed set. Every operation the agent can run is one you chose to include.
- **Credential handling:** Your FunTranslations API secret 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 'translate text to Yoda speak' or 'convert a message to Morse code', and Jentic returns the matching FunTranslations API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Starwars Translations API** — Subset of FunTranslations focused only on Star Wars languages (Yoda, Sith, Huttese, Mandalorian, Cheunh, Gungan).
- **FunTranslations Braille API** — Subset of FunTranslations dedicated to Braille output formats only.

## FAQ

### What authentication does the FunTranslations API use?

Every operation requires the X-Funtranslations-API-Secret header carrying your subscription key. Jentic stores that key encrypted and attaches it at execution so the agent context never sees the raw secret.

### Can I generate Morse code audio with the FunTranslations API?

Yes. GET `/translate/morse/audio` accepts text, speed (words per minute), and tone (Hz) parameters and returns a base64-encoded WAV inside the JSON response that you can decode and play directly.

### What are the rate limits for the FunTranslations API?

FunTranslations applies tier-based hourly and daily request caps that vary by subscription level published at funtranslations.com/api; free keys are capped at a few requests per hour while paid tiers permit thousands. The spec does not embed numeric limits, so the subscription page is the authoritative source.

### How do I generate Yoda-speak text through Jentic?

Run a Jentic search for 'translate to yoda speak', load the GET `/translate/yoda` operation, then execute it with your input text. Get started with Jentic One, the self-hosted execution layer.

### Does the API support reverse translation back to English?

Reverse translation is supported only for Morse code via GET `/translate/morse2english`; the dialect, character, Star Wars, Star Trek, and Braille endpoints are one-way English-to-output translators.

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

Yes. Because you run Jentic One yourself, your own rules decide exactly which of the 36 translation operations the agent may call, so you can allow just the ones it needs, such as GET `/translate/yoda` or GET `/translate/pirate`, and leave every other transform out of the allowed set. The source text passes as a request parameter rather than a URL path, so scoping is done per operation: any endpoint the agent can reach is one you deliberately included. Your FunTranslations subscription secret is held by your own instance and attached at execution, so the agent never sees the raw credential.