chucknorris.io
Free JSON REST API for hand-curated Chuck Norris jokes (facts) maintained by @matchilling. Supports random retrieval, category filtering, full-text search, and direct lookup by joke identifier. Hosted at api.chucknorris.io with an open-source Spring Boot service (chuck-api), official Node.js and Java client SDKs, a Chrome extension, a Storybook addon, and Messenger / Alexa companion apps published under the chucknorris-io GitHub organization.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles chucknorris.io the way a machine reads it — 40 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 — chucknorris.io scores 40.5/100 (thin), with a separate agent-readiness read of 32/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 chucknorris.io
Each block below is one kind of artifact we hold for chucknorris.io. 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.
chucknorris.io Categories API
Joke category metadata.
chucknorris.io Jokes API
Chuck Norris jokes (facts) endpoints.
chucknorris.io Search API
Full-text search across the joke corpus.
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).
Chuck Norris Jokes API
OPEN COLLECTIONFeatures 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Random Joke
GET /jokes/random returns a single random Chuck Norris fact.
Random Joke By Category
GET /jokes/random?category={category} constrains random selection.
List Categories
GET /jokes/categories returns the 16 supported category identifiers.
Free-Text Search
GET /jokes/search?query={query} returns matching jokes with a total count.
Lookup By Id
GET /jokes/{id} retrieves a single joke by its identifier.
Plain-Text Variant
All endpoints honor Accept text/plain for shell-friendly output.
Semantic 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.
Chucknorris Io 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.
chucknorris.io API Rules
SPECTRALchucknorris.io API Rules
SPECTRALJSON Schema 4
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.
JSON Structure 4
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.
Chucknorris Io Category List Structure
JSON STRUCTUREChucknorris Io Error Structure
JSON STRUCTUREChucknorris Io Joke Structure
JSON STRUCTUREChucknorris Io Search Result Structure
JSON STRUCTUREExamples 8
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.
Chucknorris Io Error Example
EXAMPLEChucknorris Io Joke Example
EXAMPLEScroll within the panel for all 8 ·
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.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Demo Data Source
Tutorial-friendly free public API for learning HTTP clients, SDKs, and AI tool patterns.
Chat & Bot Surfaces
Slack, Messenger, and Alexa surfaces inject random facts on demand.
Developer Toy
Storybook addon and Chrome extension use the API to entertain developers.
Load & Reliability Testing
Lightweight, no-auth endpoints are useful targets for HTTP client smoke tests.
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Slack
Slack slash command integration referenced in the public docs.
Facebook Messenger
Companion Messenger bot (chucknorris-io/app-facebook-messenger).
Alexa
Companion Alexa skill (chucknorris-io/app-alexa-skill).
Google Chrome
Official Chrome extension surfacing facts in the browser.
Storybook
Storybook addon injecting Chuck Norris facts into dev workflows.
Resources
Every other property we hold for chucknorris.io — 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.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/chucknorris-io · machine-readable index on apis.io