MeowFacts API
- Status
- Working
- API key
- Not needed
- Browser calls
- Runs in the browser
- Latency
- 683 ms
- Docs
- github.com ↗
Build snapshot, not live. One verifier run on , from the machine that built this site. How we check
Example request
GEThttps://meowfacts.herokuapp.com/
Sent from your browser straight to meowfacts.herokuapp.com. No proxy: this site never sees the request or the answer.
Copy the request
curl -s 'https://meowfacts.herokuapp.com/'const res = await fetch("https://meowfacts.herokuapp.com/");
if (!res.ok) throw new Error(`HTTP ${res.status}`);
const data = await res.json();
console.log(data);import requests
res = requests.get("https://meowfacts.herokuapp.com/", timeout=10)
res.raise_for_status()
print(res.json())Response stored by the verifier
This is what meowfacts.herokuapp.com answered when the verifier sent the request above on : HTTP 200, application/json. Arrays are cut to two items and long strings are shortened. It comes from the build snapshot.
{
"data": [
"When cats grimace, they are usually \"taste-scenting.\" They have an extra organ that, with some breathing control, all..."
]
}Availability
Up 1 of 1 day checked · 30-day window
What counts as up for this API: an answer within five seconds, a 2xx status, and the JSON body must contain the field "data".
Last check: — passed, HTTP 200 in 683 ms.
The check runs from our infrastructure, not from where you are. If you need certainty, send the request yourself above. How the verifier works.
Questions
Does the MeowFacts API need an API key?
No. The sample request on this page was answered without a key, token or account.
Can I call the MeowFacts API from the browser?
Yes. meowfacts.herokuapp.com answered our verifier with an Access-Control-Allow-Origin header on Oct 3, 2026, so a fetch call from a web page can read the response.
Is the MeowFacts API working?
At the check on Oct 3, 2026 it returned HTTP 200 with the expected data in 683 ms. The status at the top of this page shows the most recent result we have.