Install Jentic One Beta

Connect the Jokes One API to your agent

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

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%2Fjokes.one%2Fjokes-one" | 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%2Fjokes.one%2Fjokes-one" | 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 Jokes One API.

Fetch the current Joke of the Day or filter it by category

List jokes from the catalogue with category and keyword filters

Pull a single random joke for chatbot or daily-message use

Search jokes by free-text keyword or by category metadata

Add or remove tags on a joke entry as a subscriber operation

GET STARTED

Start building with Jokes One API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Jokes One API for, with concrete tasks.

★ Daily-joke Slack bot

Workplace bots that post a daily light-hearted message can pull the Joke of the Day each morning and post it into a designated channel. GET /jod returns a single curated joke with category metadata, so the bot can format the message and choose an appropriate channel. The simple GET-only flow makes this a 10-minute integration for any chat bot.

Call GET /jod each weekday at 9:00, format the response title and body, and post it to the #general Slack channel

Chatbot small-talk filler

Conversational agents handling customer support or onboarding can lean on a random-joke endpoint to lighten queues and humanise small-talk moments. GET /joke/random returns a single joke per call with no parameters required. Categorical filters can keep the humour aligned with the product's brand voice.

Call GET /joke/random with category=clean to fetch a random joke and inject it into the chatbot's small-talk response slot

Themed content widget

Editorial sites or apps with topical content (e.g., a coffee blog, a sports site) can run keyword-driven joke widgets that pull a few jokes matching the page topic. GET /joke/search with a keyword returns a list which the front-end can rotate. Combined with category metadata, this surfaces relevant jokes alongside the main content without manual curation.

Call GET /joke/search?query=coffee to list matching jokes, then render the top three in the page's sidebar widget

Agent-driven daily humour via Jentic

An AI assistant configured to brighten user check-ins can call jokes.one through Jentic without requiring its own API key. The agent expresses intent ('tell me a joke'), Jentic resolves to GET /joke/random, injects the X-JokesOne-API-Secret header from the vault, and returns the joke text. This keeps the subscriber key out of agent prompts and lets one credential serve many agent flows.

Use Jentic to search 'get a random joke', load GET /joke/random, and execute it to return a clean joke for the user's check-in

Key Endpoints

12 endpoints — jokes one is a content service that publishes a curated catalogue of jokes, including a daily joke of the day and a searchable archive across multiple categories.

METHOD

PATH

DESCRIPTION

GET

/jod

Get the Joke of the Day

GET

/jod/categories

List Joke of the Day categories

GET

/joke/random

Get a random joke

GET

/joke/search

Search jokes by keyword

GET

/joke/list

List jokes from the catalogue

GET

/joke/categories/search

Search jokes by category

POST

/joke/tags/add

Add tags to a joke (subscriber)

POST

/joke/tags/remove

Remove tags from a joke (subscriber)

GET

/jod

Get the Joke of the Day

GET

/jod/categories

List Joke of the Day categories

GET

/joke/random

Get a random joke

GET

/joke/search

Search jokes by keyword

GET

/joke/list

List jokes from the catalogue

GET

/joke/categories/search

Search jokes by category

POST

/joke/tags/add

Add tags to a joke (subscriber)

POST

/joke/tags/remove

Remove tags from a joke (subscriber)

Why Jentic?

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

Setup

Wiring the Jokes One API by hand means learning its secret-key request header, building query parameters for the joke and category endpoints, and parsing the responses yourself. Through Jentic you install once, import the Jokes One API from the API Directory, store the key once, and your agent calls it.

Permission scoping

This API's read and search endpoints (/joke/random, /joke/search, /jod) address jokes by query rather than by a resource id in the path, so you limit the agent to the operations it needs, such as fetching the daily joke or searching jokes. Tag-editing operations like adding or removing tags are left out unless you include them.

Credential isolation

Your Jokes One 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.

Intent-based discovery

Agents search Jentic by intent such as 'tell a joke' or 'daily joke', and Jentic returns the matching Jokes One operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Jokes One API through Jentic.

What authentication does the Jokes One API use?

The Jokes One API uses an API key passed in the X-JokesOne-API-Secret header. Public endpoints like GET /jod are usable anonymously; the subscriber endpoints (joke management and tag operations) require a valid key. Jentic stores the key encrypted and injects it on each request.

Can I get the Joke of the Day for free?

GET /jod is the public Joke of the Day endpoint and is callable without a subscription. GET /jod/categories returns the available daily categories, so you can request a specific theme if the day's catalogue supports it.

What are the rate limits for the Jokes One API?

Rate limits are tied to subscription tier on jokes.one - the spec does not publish numeric limits. Treat the API as low-volume for free use; check the dashboard at jokes.one/api/joke/ for paid-tier throughput.

How do I get a random joke through Jentic?

Search Jentic for 'get a random joke', load GET /joke/random, and execute it. Jentic returns the joke title and body, and the X-JokesOne-API-Secret header is injected automatically. Get started with Jentic One, the self-hosted execution layer.

Can I add or remove tags on a joke?

Yes, but only for subscribers. POST /joke/tags/add and POST /joke/tags/remove modify the tag set on a joke entry. These endpoints reject unauthenticated requests, so the API key must be present.

How do I search jokes by category?

Use GET /joke/categories/search with a category name to pull jokes filtered by that taxonomy entry. For free-text search across joke bodies, use GET /joke/search with a query parameter instead.

Can I limit what my agent is allowed to do with the Jokes One API?

Yes. Because Jentic One is self-hosted, your own rules decide which Jokes One operations and credentials the agent can use, so you can grant only the read and search calls it needs, such as GET /jod for the Joke of the Day, GET /joke/random, and GET /joke/search. The subscriber tag-editing operations, POST /joke/tags/add and POST /joke/tags/remove, stay unavailable to the agent unless you explicitly include them. Your Jokes One API secret is held by your own instance and injected only on the calls you allow, so it never reaches the agent's prompt.

Jokes One API

AI ReadinessNon-Ready (F)33/100

See full scorecard

Official vendor OpenAPI document · agent-readyMediaContent DeliveryapiKey12 EndpointsREST

For Agents

Fetch the daily Joke of the Day, search and pull random jokes by category or keyword, and (for subscribers) manage joke entries and tags so agents can drop a joke into chat, email, or a UI surface.

Use for: I need a joke to send in our team's morning standup message, Get today's Joke of the Day from jokes.one, Search for a clean dad joke about coffee, List all jokes in the 'puns' category

Not supported: Does not handle text-to-speech delivery, content moderation by user, or licensing for commercial republishing - use for joke retrieval, search, and subscriber-side joke management only.

Jokes One is a content service that publishes a curated catalogue of jokes, including a daily Joke of the Day and a searchable archive across multiple categories. The API exposes endpoints for fetching the joke of the day, searching by keyword or category, retrieving random jokes, and (for subscribers) managing joke entries and tags. It is the right pick for content apps, chatbots, or marketing tools that want a lightweight humour feed without curating their own corpus.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

27%

Example Density

How richly the API is illustrated with examples.

86%

Example Validity

Percentage of examples that conform to their schemas.

44%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

51%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

61%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Jokes One API to your agent

Capabilities

Start building with Jokes One API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Jokes One API

Jentic AI Readiness Score

Jokes One API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness