#decentralized

Live data from Lens Protocol, the decentralized social graph where accounts, posts and follows are owned on-chain by users rather than by a platform — read from the public Lens v3 GraphQL API, no key, nothing stored. The account endpoint resolves a Lens username (or wallet address) to its on-chain profile: display name, bio, picture and address. The stats endpoint returns that account's social graph — follower and following counts plus its post, comment, repost, quote and collect totals. The posts endpoint returns an account's recent publications, each with its text, timestamp and full engagement (reactions, comments, reposts, quotes, bookmarks, collects). The feed endpoint returns the latest posts across the entire network. Look up any Lens handle, read their reach and pull their content as structured JSON. This is the decentralized-social cut — Web3-native social data distinct from the centralized-platform social APIs and from the crypto price and market APIs in the catalogue.

api.oanor.com/lensprotocol-api

Read any public Minds channel and the platform's live hashtag trends — no key needed. Minds is an open-source, decentralised social network; this API returns a public channel's display name, bio, subscriber and subscription counts, lifetime impressions, Plus/Pro and verified flags and join date, plus the hashtags trending on Minds right now with their volume. Pass a username (the handle without the @). Data comes live from Minds' own public API — nothing cached, nothing stored. Distinct from the Mastodon/fediverse APIs — Minds runs its own platform. Built for social dashboards, creator analytics and trend monitoring.

api.oanor.com/minds-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

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

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.

api.oanor.com/nostr-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