Blague.xyz API

Name: Blague.xyz API API
Brand: Blague.xyz API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaContent Deliverybearer3 EndpointsREST

For Agents

Reference spec for a French jokes API: three endpoints for random joke, joke by id, and joke count. Service is defunct as of 2026.

Quickstart

Get started with Blague.xyz API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"get a random French joke"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Blague.xyz API API.

Pull a random French joke from the Blague.xyz catalogue

Look up a specific French joke by its numeric id

Retrieve the total count of jokes available in the catalogue

Reuse the spec as a template for similar joke or content APIs

Reference the bearer-auth pattern when designing a comparable hobby API

GET STARTED

Start building with Blague.xyz API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Blague.xyz API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Blague.xyz API, keeping it validated and agent-ready. Blague.xyz was a French jokes API offering random joke retrieval, joke lookup by id, and a joke catalogue count. The service appears to be defunct as of 2026 (domain listed for sale), so the spec is best treated as a historical or template reference for similar joke APIs rather than a live integration target. The shape is the standard joke-API pattern: a random endpoint, a by-id endpoint, and a count endpoint.

Use Cases

Patterns agents use Blague.xyz API API for, with concrete tasks.

★ French Joke Retrieval Reference

Reference the Blague.xyz spec when designing a French-language joke or trivia feature. The three endpoints (GET /joke/random, GET /joke/{id}, GET /joke/count) cover the canonical joke-API shape: pick a random item, fetch a specific item, and report the catalogue size. The schema is a useful starting point for a similar feature backed by another data source.

Read the GET /joke/random response schema from the spec and use it to model the response shape of a comparable joke service.

Migration Audit for Former Users

Teams that previously called Blague.xyz can use the spec to inventory their existing call sites, then map each operation to a live alternative joke API. The path-and-method list makes it straightforward to grep a codebase for impacted lines and produce a migration checklist without reading the original integration code in full.

List every operationId in the Blague.xyz spec and propose a corresponding endpoint on a live joke API for each.

Hobby Project Bootstrap

Use the Blague.xyz spec as a tiny, three-endpoint bootstrap example when teaching API design or building a hobby project that mirrors a 'fun content' service. Bearer auth, a random endpoint, an id endpoint, and a count endpoint together form a minimal teaching artefact for OpenAPI structure and bearer-token security schemes.

Use the Blague.xyz paths as a template for a new OpenAPI document that exposes random, by-id, and count endpoints for any small content corpus.

Agent Schema Lookup via Jentic

An AI agent searching for a 'random joke' tool finds Blague.xyz in Jentic and inspects its schema, even though the live service is offline. This is useful in eval and template scenarios where the agent needs an example of a small, well-formed API to reason about. Jentic returns the spec contents without attempting a live call when the upstream is dead.

Use Jentic search for 'get a random French joke', load the GET /joke/random schema, and use the schema to populate a fixture for an agent eval.

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for blague.

METHOD

PATH

DESCRIPTION

GET

/joke/random

Get a random French joke

GET

/joke/{id}

Get a joke by id

GET

/joke/count

Get the total joke count

GET

/joke/random

Get a random French joke

GET

/joke/{id}

Get a joke by id

GET

/joke/count

Get the total joke count

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Blague.xyz used bearer token authentication. Jentic would have stored the token in the encrypted vault and exposed only a scoped Jentic token to the agent. Because the service is defunct, this matters only for historical reference rather than live calls.

Intent-based discovery

Agents search Jentic with intents like 'get a random French joke' and Jentic returns the GET /joke/random operation with its schema. Useful for eval scenarios that need a tiny well-formed spec to reason about.

Time to first call

Direct reading of the spec: under 30 minutes — there are only three endpoints. Through Jentic: a few minutes to search, load the schema, and inspect the shape.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

BizToc

BizToc supplies live business news content while Blague.xyz supplied joke content — both are simple content APIs.

Use BizToc when the agent needs live content; Blague.xyz is reference-only.

Complementary

Bitskout Zapier API

Bitskout processes documents while Blague.xyz returned joke content — both are tiny single-purpose APIs.

Useful as a contrast when teaching minimal API design — Bitskout is live, Blague.xyz is defunct.

Complementary

Blastable

Blastable is an email marketing API, unrelated in domain but similar in being a small focused service.

Reach for Blastable for email blasts; Blague.xyz is purely reference.

FAQs

Specific to using Blague.xyz API API through Jentic.

Why is there no official OpenAPI spec for Blague.xyz API?

Blague.xyz did not publish an OpenAPI specification, and the service appears to be defunct as of 2026 with the domain listed for sale. Jentic generates and maintains this spec so AI agents and developers can reference the historical interface via structured tooling. Get started at https://app.jentic.com/sign-up.

Is the Blague.xyz API still live?

No. The service appears to be defunct as of 2026 — the domain is reportedly for sale. Treat the spec as a historical or template reference rather than a live integration target.

What authentication does the Blague.xyz API use?

The spec declares HTTP bearer authentication (security scheme bearerAuth). When the service was live, callers attached a bearer token in the Authorization header. Through Jentic the token would be stored in the encrypted vault, but live calls are no longer expected to succeed.

Can I get a random joke from the Blague.xyz API?

GET /joke/random was the live endpoint. Calls against the production base URL are unlikely to succeed because the service is defunct, but the schema in the spec describes the response shape if you have an archived dataset.

What are the rate limits for the Blague.xyz API?

The OpenAPI spec does not declare a rate limit. Since the service is no longer live, this is moot — any rate-limit handling would only matter if a successor service adopted the same shape.

How do I use the Blague.xyz spec through Jentic?

Install with pip install jentic, then use Jentic search with 'get a random French joke'. Jentic returns the GET /joke/random operation and its schema, which you can use as a template or in eval scenarios even though the live endpoint is no longer reachable.