Install Jentic One Beta

Connect the JokeAPI to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the JokeAPI, 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%2Fjokeapi.dev%2Fjokeapi" | 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%2Fjokeapi.dev%2Fjokeapi" | 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 JokeAPI API.

Fetch a single joke or several at once from chosen categories

Filter jokes by category, language, and content flags

Get one-line jokes or two-part setup-and-delivery jokes

List available categories, languages, flags, and formats

Submit a new joke for review

GET STARTED

Start building with JokeAPI API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use JokeAPI API for, with concrete tasks.

★ Agent Joke Retrieval via Jentic

AI agents pull jokes from JokeAPI through Jentic as one discoverable integration. An agent searches by intent, receives the joke operation schema, and fetches a joke filtered by category and content flags end to end. Because the API needs no credential, Jentic simply formats the request and runs it from your own instance, so the agent gets clean content without a manual integration.

Search Jentic for 'get a joke from JokeAPI', load the GET /joke/{categories} schema, and fetch a joke filtered by category

Safe-for-Work Content Filtering

An agent that posts lighthearted content to a workplace channel fetches jokes while excluding categories and content flags that are not appropriate. JokeAPI exposes explicit category and blacklist-flag controls, so the agent can request only clean, on-brand jokes rather than filtering results after the fact.

Call GET /joke/{categories} with blacklist flags set, and read GET /flags to see which flags are available

Community Joke Submission

An agent that collects jokes from users forwards them to JokeAPI's review queue so approved ones join the public catalog. The submit operation lets the agent contribute content back to the community catalog it reads from, closing the loop between gathering and publishing.

Call POST /submit with the joke payload to add a new joke to the review queue

Key Endpoints

10 endpoints — jentic publishes the only available openapi specification for jokeapi, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/joke/{categories}

Get one or more jokes from the specified categories

GET

/categories

Get all available joke categories

GET

/languages

Get all supported languages

GET

/info

Get API information including version and joke count

GET

/flags

Get all available blacklist flags

POST

/submit

Submit a new joke for review

GET

/joke/{categories}

Get one or more jokes from the specified categories

GET

/categories

Get all available joke categories

GET

/languages

Get all supported languages

GET

/info

Get API information including version and joke count

GET

/flags

Get all available blacklist flags

POST

/submit

Submit a new joke for review

Why Jentic?

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

Setup

JokeAPI needs no setup: there is no key to obtain and no account to create. Through Jentic you install once, import JokeAPI from the API Directory, and your agent calls it, with Jentic handling request formatting and category filters.

Permission scoping

Even without a credential, you choose which JokeAPI operations your agent may call, so a rule can allow joke retrieval while withholding the submit-a-joke operation. Submissions or other operations stay out unless you grant them.

Credential isolation

JokeAPI needs no credential, so there is nothing to store or inject. Your agent calls it directly through Jentic with no key to manage.

Intent-based discovery

Agents search Jentic by intent such as 'get a programming joke' or 'list joke categories', and Jentic returns the matching JokeAPI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using JokeAPI API through Jentic.

Why is there no official OpenAPI spec for JokeAPI?

JokeAPI does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call JokeAPI via structured tooling. It is validated against the live API and kept up to date. To run it on your own infrastructure, install Jentic One from its GitHub repo.

What authentication does the JokeAPI use?

None. JokeAPI is a free, open API that needs no key or token, so your agent calls it without any credential. Through Jentic, it runs from your own instance like any other integration.

Can I fetch a joke by category with the JokeAPI?

Yes. Fetch one or more jokes from chosen categories with GET /joke/{categories}, and list the available categories with GET /categories.

How do I get a joke with the JokeAPI through Jentic?

Search Jentic for 'get a joke from JokeAPI', load the returned GET /joke/{categories} operation with its input schema, and your agent fetches the joke, filtering by category and content flags as needed.

Is there a JokeAPI MCP server?

You don't need an MCP server to give your agent the JokeAPI. Jentic connects it directly from the API Directory: import it and your agent calls it, discovering operations on demand instead of loading a separate server's tool definitions into its context.

Can I limit what my agent is allowed to do with the JokeAPI?

Yes. Even though JokeAPI needs no credential, you still choose which operations your agent may call, so you can allow joke retrieval while withholding the submit-a-joke operation. Scoping is by operation, so the agent reaches only the endpoints you approve.

JokeAPI

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticMediaContent Deliverynone10 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Fetch and filter jokes by category, language, and content flags, and submit new jokes, from a free open catalog. No authentication is required.

Use for: I want a random programming joke, Get a joke that is safe for work, Fetch several jokes from the pun category, List the joke categories available

Not supported: Does not generate original jokes or moderate submissions automatically. Use for fetching and submitting catalog jokes only.

Jentic publishes the only available OpenAPI specification for JokeAPI, keeping it validated and agent-ready. The JokeAPI serves jokes to AI agents from a free, open catalog across categories such as programming, pun, and spooky. Agents fetch a single joke or several at once, filter by category, language, and content flags, and receive either a single-line joke or a two-part setup and delivery. They can also submit a new joke for review and read the supported categories, languages, flags, and formats. No authentication is required.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 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).

42%

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: C+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

30%

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

14%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

90%

OperationId Quality

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

50%

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.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

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: CSignals: 1

54%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the JokeAPI to your agent

Capabilities

Start building with JokeAPI API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

JokeAPI

Jentic AI Readiness Score

JokeAPI

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