Fungenerators Shakespeare API
Browse all Fungenerators APIsOfficial vendor OpenAPI document · agent-readyData EnrichmentData TransformationapiKey5 EndpointsREST
For Agents
Generate Shakespearean names, insults, lorem ipsum, and quotes, and translate English text into Shakespearean style.
Use for: Generate a Shakespearean character name, Translate this paragraph into Shakespearean English, Get a Shakespeare insult for the chatbot, Retrieve a Shakespeare quote for the daily widget
Not supported: Does not produce audio, modern paraphrases, or full play scripts - use for Shakespeare-themed text generation, quotes, and translation only.
The Shakespeare API generates Elizabethan-flavoured content on demand. Five endpoints cover random Shakespeare-style names, insults, lorem ipsum filler text, quotes from the canonical works, and translation of plain English into Shakespearean English. The API powers literary novelty sites, classroom warmups, themed marketing campaigns, and chat experiences that benefit from a period voice. Responses are short JSON strings ready to render in any UI or agent tool output.
Install Jentic One Beta
Connect the Shakespeare API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Shakespeare API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffungenerators.com%2Ffungenerators-shakespeare" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffungenerators.com%2Ffungenerators-shakespeare" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Shakespeare API.
Generate a Shakespearean character name for stories or themed apps
Produce a Shakespeare-style insult for chat replies and game taunts
Generate Shakespearean lorem ipsum filler for design mockups
Retrieve a quote from Shakespeare's works for daily widgets
Translate plain English into Shakespearean English
Use Cases
Patterns agents use Shakespeare API for, with concrete tasks.
★ Literary and Classroom Apps
Educational sites, English literature apps, and theatre programmes use the Shakespeare API to surface daily quotes and themed names. Teachers can run a 'translate this sentence' warmup using the translation endpoint, or theatre teams can populate prop lists with Shakespearean names. Integration is two or three small calls per session.
Each morning call GET /shakespeare/quote and pin the result on the class portal as the quote of the day.
Themed Marketing and Novelty Sites
Marketing teams run Shakespeare-themed campaigns by translating taglines into Shakespearean English and decorating landing pages with period names and insults. The API handles the language transformation so designers can focus on layout and copy direction.
Translate the campaign tagline by calling GET /shakespeare/translate with the text query parameter, then schedule the result on social channels.
Chatbot Period Persona
A chatbot can adopt a Shakespearean persona by generating its own Shakespearean name on signup, translating user prompts into period English for replies, and dropping in a quote when the user asks for inspiration. The five endpoints cover the persona's main needs without external content.
On user prompt, call GET /shakespeare/translate with the message and reply with the translated version.
AI Agent Period Translation Tool
Wire the Shakespeare API into Jentic so any agent can produce Elizabethan-styled content on request. Through Jentic the agent searches by intent, the API key remains vaulted, and the agent receives the translation, quote, name, or insult as structured JSON.
Use Jentic to search 'translate text to shakespearean english', load GET /shakespeare/translate, and execute it with the user's input text.
Key Endpoints
5 endpoints — the shakespeare api generates elizabethan-flavoured content on demand.
METHOD
PATH
DESCRIPTION
GET
/shakespeare/quote
Retrieve a Shakespeare quote
GET
/shakespeare/translate
Translate English to Shakespearean English
GET
/shakespeare/generate/name
Generate a Shakespearean name
GET
/shakespeare/generate/insult
Generate a Shakespeare insult
GET
/shakespeare/generate/lorem-ipsum
Generate Shakespearean lorem ipsum
GET
/shakespeare/quote
Retrieve a Shakespeare quote
GET
/shakespeare/translate
Translate English to Shakespearean English
GET
/shakespeare/generate/name
Generate a Shakespearean name
GET
/shakespeare/generate/insult
Generate a Shakespeare insult
GET
/shakespeare/generate/lorem-ipsum
Generate Shakespearean lorem ipsum
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Fungenerators Shakespeare API by hand means sending an secret-key request header on every call, choosing the http or https api.fungenerators.com host, and mapping the quote, translate, and generate routes yourself. Through Jentic you install once, import the Shakespeare API from the API Directory, store the key once, and your agent calls it.
Permission scoping
The Shakespeare API takes its input in query parameters rather than a resource path, so you limit the agent to the operations it needs, such as getting a quote or translating text to Shakespearean English. You choose which operations it may call, and nothing outside that set runs.
Credential isolation
Your Fungenerators API key is stored once, encrypted, by your own Jentic One instance and injected into the secret-key request header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'translate text to Shakespearean English' or 'get a Shakespeare quote', and Jentic returns the matching GET /shakespeare/translate or GET /shakespeare/quote operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Shakespeare API through Jentic.
What authentication does the Shakespeare API use?
It uses an API key supplied in the X-Fungenerators-API-Secret request header. Through Jentic the key is held encrypted in the vault and attached at runtime, so agents never see the raw secret.
Can I translate text into Shakespearean English with this API?
Yes. Call GET /shakespeare/translate and pass the text as a query parameter. The response contains the Shakespearean translation as a string.
What are the rate limits for the Shakespeare API?
The OpenAPI spec does not declare explicit rate limits. Fungenerators applies plan-based quotas listed on the subscription page at fungenerators.com, so consult the plan you subscribed to for the per-minute and per-day caps.
How do I get a daily Shakespeare quote through Jentic?
Search 'get a Shakespeare quote' via the Jentic SDK or MCP server, load GET /shakespeare/quote, and execute it once per day. Install with pip install jentic and authenticate using your ak_* key.
Are Shakespeare quotes attributed to a specific play?
The quote endpoint returns text from Shakespeare's works. Attribution metadata depends on the response payload returned by the live API; consult the Fungenerators documentation for the latest field shape.
Does the API generate audio readings of quotes?
No. Responses are text only. To produce a spoken version, pass the returned text through a separate text-to-speech provider in your client.
Can I limit what my agent is allowed to do with the Shakespeare API?
Yes. Because you run Jentic One yourself, your own rules decide which of the Shakespeare API operations the agent may call, so you can allow only GET /shakespeare/translate and GET /shakespeare/quote while blocking the name, insult, and lorem ipsum endpoints if they are not needed. Since this API takes its input in query parameters rather than a resource path, scoping is done at the operation level and nothing outside the set you approve runs. Your Fungenerators API key is held by your own instance and attached at execution time, so the agent uses it only for the operations you permit.
GET STARTED