Docs/APIs/Random Facts

Random Facts

Get random facts

OperationalCredits 2 per callp50 286msEntertainmentStar

Overview

Send a GET request to receive an entry from the collection, returned as a JSON object with a single fact string. Every call produces an individual item, requiring no configuration or query arguments.

Live Test Random Facts API →

Endpoint

One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.

GEThttps://api.apiverve.com/v1/randomfacts
curl "https://api.apiverve.com/v1/randomfacts" \
  -H "x-api-key: your_api_key_here"

Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.

Authentication

Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Response

Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.

Sample response
{
  "status": "ok",
  "error": null,
  "data": {
    "fact": "Rhinoceros have 3 toes on each foot"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

FieldTypeExampleDescription
factstring"Rhinoceros have 3 toes on each foot"A random interesting fact from curated collection

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.

StatusMeaningWhat to do
400Input was rejectedRead error; it names the parameter.
401Key missing or invalidCheck the header name and the key value.
403Key valid, but not permittedA key restriction or IP allow-list; see key scoping.
429Rate limited, or out of creditsRead error to tell them apart; see rate limits.

Use cases

Daily Newsletter Snippets
Email marketers inject a fresh trivia sentence into morning roundups to give subscribers a quick educational takeaway before the main articles.
Chatbot Icebreakers
When community Discord bots receive an idle prompt, they pull an unexpected fact to stimulate conversation among chat members.
Loading Screen Entertainment
Keep players entertained between game rounds by showing a single interesting trivia snippet while assets load in the background.
Digital Dashboard Widgets
To keep breakroom display boards engaging, internal IT teams rotate a new general knowledge statement every few minutes.

Other ways to use Random Facts

Set up Random Facts on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →
Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →

More in Entertainment:

Was this page helpful?