oanor
Sign up free
Marketplace Pricing Features Sign in

API · /nostr-api

Nostr API

healthy 4,045 Subscribers

Live profile and notes for any Nostr account, read straight from the open Nostr relay network — no key, no account, nothing cached. Nostr is the decentralised, censorship-resistant social protocol with no central server, so this service queries several public relays in parallel and merges and de-duplicates what they return. Give it a public key, either as 64-character hex or as an npub… key (it decodes bech32 npub keys for you), and the profile endpoint returns the account's kind-0 metadata: name, display name, about/bio, picture, banner, website, NIP-05 verified identifier and Lightning address — fiatjaf's key resolves to name "fiatjaf", NIP-05 [email protected]. The notes endpoint returns the account's most recent kind-1 text notes — the posts — newest first and de-duplicated across relays, each with its content, timestamp, note id and mention and reply counts. The relays endpoint lists the public relays queried. This is the profile-and-posts layer for any Nostr client, bot, indexer or social dashboard — live from the relay network, nothing stored. Distinct from centralised-platform social APIs — this reads the open Nostr protocol directly from its relays. 4 endpoints.

#nostr #decentralized #social #profile #notes #relay #web3
api.oanor.com/nostr-api
Get an API key Try in playground → Contact provider

Machine-readable spec so AI agents can integrate this API.

/api/nostr-api/openapi.json
/api/nostr-api/llms.txt

Discovery: GET /api/index.json lists every API.

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
743 ms
Server probes · 24h
Subscribers
4,045
active
Total calls
16
last 7 days
status Full status page → · 8 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 12,000 calls / month
  • 3 requests / second
  • Hard cap (429 above quota, no overage)
  • 12,000 calls/month
  • 3 req/sec
  • Profiles + notes across public relays
  • No account, no key
Sign in to subscribe

Starter

€6.50 /month

  • 150,000 calls / month
  • 8 requests / second
  • Hard cap (429 above quota, no overage)
  • 150,000 calls/month
  • 8 req/sec
  • npub & hex keys, NIP-05, Lightning address
  • Email support
Sign in to subscribe

Pro

€17.50 /month

  • 700,000 calls / month
  • 15 requests / second
  • Hard cap (429 above quota, no overage)
  • 700,000 calls/month
  • 15 req/sec
  • Client, bot & indexer pipelines
  • Priority support
Sign in to subscribe

Scale

€41.00 /month

  • 3,500,000 calls / month
  • 30 requests / second
  • Hard cap (429 above quota, no overage)
  • 3,500,000 calls/month
  • 30 req/sec
  • Relay-aggregator scale
  • Dedicated SLA
Sign in to subscribe

Built by

P
PremiumApi

Related APIs

Other APIs with overlapping tags.

Hive API

Live data for the Hive blockchain social network, served straight from Hive's public JSON-RPC nodes — no key, no account, nothing cached. Hive is a decentralised blogging and social platform where posts and votes live on-chain and earn crypto rewards. The account endpoint resolves a username to its profile: display name, reputation score, follower and following counts, post count, bio, location, website and join date — @gtg ("Gandalf the Grey") has a 76 reputation and over ten thousand followers. The posts endpoint returns a user's blog posts with each post's up-vote count, the HBD payout it earned, the comment count, the tags and a link. The trending endpoint returns the platform's trending (or hot, new or top-paid) posts right now, optionally filtered by tag — the front page of Hive. This is the profile-posts-and-trends layer for any decentralised-social, blogging or web3 app. Live from the Hive blockchain, nothing stored. Distinct from other social and centralised-blog APIs — this is the on-chain Hive network. 4 endpoints.

api.oanor.com/hive-api

Odysee API

Live data for Odysee, the decentralised video platform built on the LBRY blockchain — a censorship-resistant YouTube alternative — served straight from the public Odysee/LBRY backend with no key and nothing cached. The channel endpoint resolves a @channel handle to its title, description, avatar and cover art, the number of videos it has published, the LBC staked on it and its tags and languages: @Odysee resolves to the official channel with 134 published claims. The videos endpoint lists a channel's most recent uploads with the title, description, duration, thumbnail, release date and a ready-to-open watch URL. The search endpoint searches the whole platform for videos by keyword, returned in trending order with their channel, title and link. This is the channel-and-video discovery layer for any app building on decentralised, creator-owned video — read live on-chain from the LBRY network, nothing stored. Distinct from centralised-platform and other video APIs — this is the on-chain Odysee/LBRY catalogue. 4 endpoints.

api.oanor.com/odysee-api

Fediverse Statistics API

Live Fediverse statistics as an API — a read on the size and shape of the decentralised social web. The fediverse is the network of interoperable social platforms — Mastodon, Misskey, Pixelfed, Lemmy, PeerTube and dozens more — and this returns the network-wide totals (instances, users, posts and monthly active users), the breakdown by software (how many instances and users each platform runs, with its license, website and source repository, and the hosting providers it concentrates on), and the largest servers ranked by user count, with an optional filter to a single platform. The meta-social layer: not one platform's posts, but the whole federated network as clean JSON, served live from FediDB. Distinct from the single-platform Mastodon, Misskey, Mbin and Lemmy APIs — this is the cross-fediverse statistics layer for social, research and dashboard apps.

api.oanor.com/fediverse-api

Wikipedia Trends API

Live readership-trend data from the Wikimedia Pageviews API — the official measure of what the world is reading on Wikipedia and its sister projects. See the most-viewed articles on any Wikipedia language edition for a given day (the daily trending list); pull the daily or monthly pageview trend for any single article over a date range; read a whole project's total pageviews over a range as a barometer of overall traffic; or rank several articles head-to-head by total views for topic-engagement comparison. Special / namespace pages (Main Page, Search, Portal…) are filtered out by default so the trending list is real articles. Read live from Wikimedia, nothing stored — data lags about 1-2 days, so ranges default to ending two days back. This is the Wikipedia readership-trend and topic-engagement layer for any trends, research, newsroom or analytics app — distinct from Wikipedia content APIs: this is the pageview, trending and engagement signal of what people are actually reading and how it changes.

api.oanor.com/wikitrends-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for Nostr API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Nostr API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Nostr API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does Nostr API cost?
Nostr API has a free tier with 100 calls / month. Paid plans start at €6.50 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is Nostr API GDPR-compliant?
All requests to Nostr API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.

Pick an endpoint from the list on the left to see its details and try it.

Code snippets

Sign up to get an API key, then call any path under your slug.

curl https://api.oanor.com/nostr-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/nostr-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/nostr-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
    "https://api.oanor.com/nostr-api/SOME_PATH",
    headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())

Ratings

Sign in to rate.

No reviews yet.

Discussion

Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.

Sign in to start a thread or reply.

Sign in

New thread

/ 4000

📌 Pinned 🔒 Locked

·

· ·

/ 4000

🔒 This thread is locked — no new replies.

  • No threads yet — start the discussion.

Support

Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.

Sign in to open a support ticket.

Sign in

Open new ticket

Describe what you need help with. The provider team gets an email and replies on the ticket page.

  • No tickets yet for this API.

Subscription active — calls can start immediately.

Send your first request —

Subscription active — copy a snippet and fire off your first call.