Install Jentic One Beta

Connect the Taunt as a service to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Taunt as a service, 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.

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-taunt" | sh

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-taunt" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Taunt as a service API.

Generate a random taunt within a chosen themed category

List all supported taunt categories for selection menus

Produce comedic wrong-answer feedback for puzzle and quiz apps

Supply playful roast lines for chatbots and Discord bots

Populate themed game NPCs with signature taunts

GET STARTED

Start building with Taunt as a service API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Taunt as a service API for, with concrete tasks.

★ Wrong-Answer Feedback in Quiz Apps

Quiz and puzzle apps use a themed taunt as the response when a user answers incorrectly. Selecting a category that matches the quiz topic keeps the comedy on-brand. The integration is two calls: list categories once, then generate a taunt on each wrong answer.

On a wrong quiz answer, call GET /taunt/generate with category=sports and display the returned taunt to the user.

Chatbot Roast Mode

Chatbots and Discord bots add a 'roast me' command that calls the taunt endpoint and replies with a playful insult. Bot operators choose categories that match their server's tone, from gentle ribbing to harder-edged humour.

On the 'roast me' intent, call GET /taunt/generate with category=general and reply with the taunt.

Game NPCs with Signature Taunts

Game studios attach a taunt to each NPC profile to give them voice. The API supplies on-demand themed lines, so studios do not have to maintain a custom taunt corpus. NPCs can also speak a fresh line each encounter rather than the same scripted insult.

When the player engages an NPC, call GET /taunt/generate with the NPC's category to produce its line.

AI Agent Roast Tool

Wire the Taunt API into Jentic so any agent can produce a themed taunt on request. Through Jentic the agent searches by intent, the API key remains vaulted, and the agent receives the taunt JSON to use in its reply or in a downstream content workflow.

Use Jentic to search 'generate a themed taunt', load GET /taunt/generate, and execute it with the user's chosen category.

Key Endpoints

2 endpoints — the taunt as a service api generates random taunts and insults across many themed categories.

METHOD

PATH

DESCRIPTION

GET

/taunt/generate

Generate a random taunt in a chosen category

GET

/taunt/categories

List supported taunt categories

GET

/taunt/generate

Generate a random taunt in a chosen category

GET

/taunt/categories

List supported taunt categories

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Fungenerators Taunt as a service API by hand means sending an secret-key request header on every call to api.fungenerators.com and reading the categories route to know which themes are valid. Through Jentic you install once, import Taunt as a service from the API Directory, store the key once, and your agent calls it.

Permission scoping

The Taunt API takes its input in query parameters rather than a resource path, so you limit the agent to the operations it needs, such as generating a themed taunt or listing categories. 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 'generate a themed taunt' or 'list taunt categories', and Jentic returns the matching GET /taunt/generate or GET /taunt/categories operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Taunt as a service API through Jentic.

What authentication does the Taunt as a service API use?

It uses an API key supplied in the X-Fungenerators-API-Secret request header. Through Jentic the key is stored encrypted and attached at execution time, never in the agent's prompt.

Can I generate a category-specific taunt with this API?

Yes. Call GET /taunt/categories to list the supported categories, then GET /taunt/generate with your chosen category to receive a taunt in that style.

What are the rate limits for the Taunt API?

The OpenAPI spec does not declare explicit rate limits. Fungenerators applies plan-based quotas published on the subscription page at fungenerators.com, so consult the plan you signed up for.

How do I generate a taunt through Jentic?

Search 'generate a themed taunt' via the Jentic SDK or MCP server, load GET /taunt/generate, and execute it with the desired category. Install with pip install jentic and authenticate using your ak_* key.

Can I generate taunts in bulk?

The generate endpoint returns a single taunt per call. To get a batch, loop GET /taunt/generate N times in your client and de-duplicate as results arrive.

Are taunt categories user-configurable?

No. Categories are fixed by Fungenerators and only modifiable by them. Call GET /taunt/categories at any time to see the current set.

Can I limit what my agent is allowed to do with the Taunt as a service API?

Yes. Because you run Jentic One yourself, your own rules decide which of this API's operations the agent may call, so you can allow only GET /taunt/generate for producing a themed taunt, only GET /taunt/categories for listing the supported categories, or both. This API passes its input through query parameters rather than a resource path, so scoping the agent to just the operations it needs is enough to keep anything outside that set from running. You also hold the Fungenerators API key in your own instance and attach it only when a permitted operation executes, so the agent never sees the credential directly.

Fungenerators Taunt as a service

Name: Taunt as a service API
Brand: Taunt as a service
Availability: InStock

Browse all Fungenerators APIs

Official vendor OpenAPI document · agent-readyData EnrichmentData TransformationapiKey2 EndpointsREST

For Agents

Generate themed random taunts and insults from many categories, with a separate endpoint to list the available categories.

Use for: Generate a taunt in the sports category, List all supported taunt categories, Find a roast line for a chatbot reply, Produce a wrong-answer taunt for a quiz app

Not supported: Does not moderate or filter content for safety, generate audio, or score user responses - use for retrieving themed taunts and category lists only.

The Taunt as a service API generates random taunts and insults across many themed categories. Two endpoints cover listing the supported categories and generating a taunt within a chosen category. The API powers playful roast features in chatbots, wrong-answer feedback in puzzle apps, and themed comedic content in social tools and games. Responses are short JSON strings ready to render in any UI without further processing.

Jentic One on Github View OpenAPI Document