JokeAPI
JokeAPI is a free, open source REST API that delivers consistently formatted jokes in JSON, XML, YAML, or plain text. It exposes seven joke categories (Any, Misc, Programming, Dark, Pun, Spooky, Christmas), six blacklist content flags (nsfw, religious, political, racist, sexist, explicit), and filters for language, joke type, ID range, contains-text search, amount, and safe-mode. No sign-up is required and CORS is enabled. The service is rate-limited at 120 requests per minute per IP (5 per minute on submissions) and is maintained by Sv443 under the MIT license. The canonical source lives on Sv443's own Git server, with this GitHub repo kept open for issues and the community wrapper-library index.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles JokeAPI the way a machine reads it — 53 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — JokeAPI scores 47.6/100 (developing), with a separate agent-readiness read of 39/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile JokeAPI
Each block below is one kind of artifact we hold for JokeAPI. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 3
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
JokeAPI Jokes API
Operations for retrieving and submitting jokes.
JokeAPI Metadata API
Operations describing the API surface — categories, flags, formats, languages.
JokeAPI System API
Health and discovery endpoints.
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
JokeAPI
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Jokeapi Rate Limits
RATE LIMITSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Jokeapi Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JokeAPI API Rules
SPECTRALJokeAPI API Rules
SPECTRALJSON Schema 14
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
CategoriesResponse
JSON SCHEMAEndpointsResponse
JSON SCHEMAFlagsResponse
JSON SCHEMAFormatsResponse
JSON SCHEMAInfoResponse
JSON SCHEMAJokeBatch
JSON SCHEMAJokeFlags
JSON SCHEMAJokeSubmission
JSON SCHEMALangcodeResponse
JSON SCHEMALanguagesResponse
JSON SCHEMAPingResponse
JSON SCHEMASingleJoke
JSON SCHEMASubmissionResponse
JSON SCHEMATwopartJoke
JSON SCHEMAScroll within the panel for all 14 ·
JSON Structure 14
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Jokeapi Categories Response Structure
JSON STRUCTUREJokeapi Endpoints Response Structure
JSON STRUCTUREJokeapi Flags Response Structure
JSON STRUCTUREJokeapi Formats Response Structure
JSON STRUCTUREJokeapi Info Response Structure
JSON STRUCTUREJokeapi Joke Batch Structure
JSON STRUCTUREJokeapi Joke Flags Structure
JSON STRUCTUREJokeapi Joke Submission Structure
JSON STRUCTUREJokeapi Langcode Response Structure
JSON STRUCTUREJokeapi Languages Response Structure
JSON STRUCTUREJokeapi Ping Response Structure
JSON STRUCTUREJokeapi Single Joke Structure
JSON STRUCTUREJokeapi Submission Response Structure
JSON STRUCTUREJokeapi Twopart Joke Structure
JSON STRUCTUREScroll within the panel for all 14 ·
Examples 14
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Jokeapi Joke Batch Example
EXAMPLEJokeapi Joke Flags Example
EXAMPLEJokeapi Single Joke Example
EXAMPLEJokeapi Twopart Joke Example
EXAMPLEScroll within the panel for all 14 ·
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for JokeAPI — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/jokeapi · machine-readable index on apis.io