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

# Fun Translations APIs

Fun Translations offers a family of text transformation APIs that turn English input into novelty, fictional, dialect, Morse, and Braille output. Across its three APIs an agent can translate a sentence into 36 styles such as Yoda, Sith, Klingon, Pirate, and Minion, generate Morse code as text or audio, decode Morse back to English, and render Braille in five formats spanning display characters, dot patterns, Unicode glyphs, HTML entities, and image markup. Every endpoint is a single GET that takes one text query parameter and returns a consistent JSON envelope, and all APIs share one X-Funtranslations-API-Secret key and one subscription quota. The APIs suit novelty apps, fan and themed marketing content, accessibility utilities, and educational tools that need rapid text transformation without hosting their own language models.

## For AI agents

An agent can translate English text into dozens of novelty, fictional, and dialect styles, generate and decode Morse code including audio, and convert text into five Braille output formats, all through single-parameter GET calls that share one authentication key.

## Scope

Use for: Transforming English text into novelty, fictional, dialect, Morse, and Braille output through single-parameter GET endpoints

Not supported:
- human language translation
- speech recognition
- voice synthesis
- content moderation
- reverse Braille decoding

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| FunTranslations API | ai-ml | 36 | 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. |
| Starwars Translations API | ai-ml | 6 | Translate English text into six Star Wars languages - Yoda, Sith, Cheunh, Huttese, Mandalorian, and Gungan - through dedicated GET endpoints with a single text parameter. |
| FunTranslations Braille API | ai-ml | 5 | Convert English text into five different Braille output formats including raw display characters, dot patterns, Unicode glyphs, HTML entities, and image markup for accessibility and educational tools. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Any translation style, including Morse, dialects, character speak, plus Star Wars and Braille in one workflow | index | The index API is the umbrella surface exposing all 36 translators, so use it when a workflow mixes styles or needs a translator not covered by the narrower APIs. |
| Only Star Wars language output such as Yoda, Sith, Huttese, or Mandalorian | starwars | The starwars API exposes just the six Star Wars languages, giving an agent a narrower tool surface than the full index API. |
| Only Braille output for accessibility or education | braile | The braile API covers just the five Braille formats, so pick it when the task is accessibility rather than novelty translation. |

## Cross-API use cases

### Themed fan experience with accessible captions

Build a Star Wars fan page that restyles user quotes into Yoda or Sith speak and also renders those quotes as Braille so the experience stays accessible. The agent routes themed text through the Star Wars endpoints and passes the same source text to a Braille format for an accessible caption, using one shared key for both.

Example prompt: Call GET /translate/yoda on the starwars API with the user quote, then call GET /translate/braille/unicode on the braile API with the same text and return both outputs.

### Multi-style novelty translator with accessibility fallback

Power a novelty translator app that offers dozens of styles from the umbrella API and an accessibility mode that outputs Braille. The agent uses the index API for style variety and switches to the dedicated Braille API when the user requests an accessible rendering.

Example prompt: Call GET /translate/pirate on the index API for the styled string, then call GET /translate/braille/dots on the braile API with the original text for the accessibility view.

### Roleplay agent spanning many character voices

Run an interactive roleplay agent that gives Star Wars characters authentic voices and can also reach for wider styles such as Klingon or Pirate when a scene calls for it. The agent uses the Star Wars API for canonical Star Wars languages and falls back to the umbrella API for any other requested style.

Example prompt: Call GET /translate/huttese on the starwars API for a Hutt character line, then call GET /translate/klingon on the index API when the scene switches to a Klingon character.

## Why Jentic

- **Setup:** Wiring the Fun Translations APIs by hand means configuring the secret-key request header against api.funtranslations.com and mapping the novelty, Morse, Star Wars, and Braille endpoints across three APIs yourself. With Jentic you install Jentic One once, add any of these APIs from the Jentic API Directory, store the key once, and your agent calls them.
- **Permission scoping:** The text to transform travels as a request parameter rather than a path resource, so scope access by operation: your own rules in Jentic One decide which translators the agent may call, such as a Yoda or a Braille endpoint, and leave every other style outside the allowed set. Every operation the agent can run is one you chose to include.
- **Credential handling:** Your Fun Translations API secret is stored encrypted by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context, and the single key covers all three APIs.
- **Discovery method:** Agents search the Jentic directory by intent such as 'translate text to Yoda speak' or 'convert English to Braille', and Jentic returns the matching Fun Translations operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related vendors

- **DeepL** — Provides real human language machine translation for teams that need genuine cross-language translation rather than novelty output.
- **API Ninjas** — Offers a broad set of small utility APIs including text and novelty transforms in a similar single-call style.
- **Wit.ai** — Handles natural language understanding and speech, complementing text-transformation use cases with intent and voice processing.

## FAQ

### Does one API key work across all three Fun Translations APIs?

Yes. Every operation on the index, Star Wars, and Braille APIs authenticates with the same X-Funtranslations-API-Secret header and shares a single tier-based subscription quota, so one key and one subscription cover the whole portfolio.

### Which Fun Translations API should an agent choose?

Use the index API when a workflow mixes styles or needs a translator such as Morse or a dialect that the narrower APIs do not cover. Use the Star Wars API when only Star Wars languages are needed and a smaller tool surface is preferred, and use the Braille API when the task is accessibility or education.

### Do these APIs translate real human languages?

No. Fun Translations transforms English text into novelty, fictional, dialect, Morse, and Braille output. It does not translate between major world languages and is not a substitute for a general machine translation service.

### Can text be translated back from these outputs to English?

Reverse translation is available only for Morse code through the morse2english operation on the index API. The dialect, character, Star Wars, and Braille outputs are one-way English-to-output transformations.

### What input do these APIs accept?

Each endpoint is a single GET that takes one text query parameter and returns the result inside a consistent JSON envelope alongside the source text. The uniform shape means a client can swap between styles by changing one path segment.

### Can these APIs produce audio or image output as well as text?

Yes, in specific cases. The Morse endpoint on the index API can return a base64 WAV audio response with configurable speed and tone, and the Braille API can return image markup with img tags pointing to per-character Braille glyphs. Most other translators return plain text.

### What are these APIs suited for?

They fit novelty apps, fan communities, themed marketing copy, character chatbot voices, accessibility utilities, and educational tools that need fast text transformation without hosting their own language models.