#social-graph

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

Live cryptographic social-identity lookup from Keybase — no key, nothing cached. Keybase links a person's identities together with public-key cryptography, so this answers "who is this account, really, and what else are they?". The user endpoint takes a Keybase username and returns the profile (full name, location, bio, picture), every verified identity proof — the Twitter, GitHub, Reddit, Hacker News, Mastodon, website and DNS accounts that user has cryptographically proven are theirs — plus their on-file cryptocurrency addresses (Bitcoin, Zcash and more) and PGP key fingerprint: Keybase user "chris" resolves to Chris Coyne in Maine, with proven twitter/github/reddit @malgorithms and a Bitcoin address. The lookup endpoint runs the reverse — give it a GitHub, Twitter, Reddit or Hacker News handle, a domain or a PGP fingerprint and it finds the Keybase user who proved it, so a bare GitHub handle resolves to a full verified identity. The proofs endpoint returns just the connected-accounts graph and crypto addresses. This is the identity-verification and social-graph layer for any trust, onboarding, anti-impersonation, social or crypto app — proven links, not claimed ones. Live from Keybase, nothing stored. Distinct from single-platform profile APIs — this is the cross-platform proven-identity graph. 4 endpoints.

api.oanor.com/keybase-api