/v1/meta
Spec
Try it live
10 free calls per day — no sign-up, no API key. Goes through the oanor gateway.
It works. Grab an API key and use it in your project.
Get an API keyCode snippets
curl "https://api.oanor.com/nostr-api/v1/meta" \ -H "x-oanor-key: oanor_test_..."
await fetch("https://api.oanor.com/nostr-api/v1/meta", {
headers: { "x-oanor-key": "oanor_test_..." }
});
$ch = curl_init("https://api.oanor.com/nostr-api/v1/meta");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$out = curl_exec($ch);
import requests
requests.get(
"https://api.oanor.com/nostr-api/v1/meta",
headers={"x-oanor-key": "oanor_test_..."}
)
Example response
A real response from this endpoint, captured by the latest health check.
{
"data": {
"source": "Public Nostr relays over WebSocket (NIP-01, live)",
"service": "nostr-api",
"endpoints": {
"GET /v1/meta": "This document.",
"GET /v1/notes": "An account's recent text notes (pubkey=…, limit up to 50).",
"GET /v1/relays": "The public relays queried.",
"GET /v1/profile": "An account's profile metadata (pubkey=64-hex or npub1…)."
},
"description": "Live profile and notes for any Nostr account, read directly from the open Nostr relay network: kind-0 profile metadata (name, display name, about, picture, banner, website, NIP-05, Lightning address) and recent kind-1 text notes (content, timestamp, id, mention and reply counts), merged across several public relays and de-duplicated. Accepts 64-hex or npub1… keys. Live, no key, nothing stored. Distinct from centralised-platform social APIs — this reads the decentralised Nostr protocol straight from its relays.",
"upstream_status": "ok"
},
"meta": {
"timestamp": "2026-06-09T11:40:03.115Z",
"request_id": "9dea45c9-dff8-4261-8ade-f4bd0463ef67"
},
"status": "ok",
"message": "Meta",
"success": true
}