Neynar

• Name: Neynar
• URL: https://neynar.com/
• Category: Farcaster developer platform / Farcaster protocol-and-client operator / social-graph and identity middleware company
• Summary: Neynar belongs as an entity note, not a protocol note. The useful cut is the named company operating Farcaster’s most important middleware surfaces — APIs, indexing and query abstractions, onboarding, mini-app tooling, notifications, and profile/social-graph portability — and, after the January 2026 acquisition from Merkle, also maintaining the Farcaster protocol, running the main client, and operating Clanker. The practical leverage is not just a Farcaster API; it is that one company now sits across both ecosystem middleware and major default operating surfaces.
• What it does:
  • Provides APIs, SDKs, indexing, and query layers that abstract direct interaction with Farcaster hubs for user, cast, feed, and social-graph data
  • Offers developer tooling for mini apps, notifications, onboarding, sign-in, profile enrichment, account registration, and app-host workflows layered on top of Farcaster identity
  • Supports agent and automation flows, including autonomous Farcaster account creation and x402-linked request/payment patterns in the docs surface
  • Operates a developer portal and API-key-gated application platform that becomes the easiest integration path for many Farcaster builders
  • Says it now maintains the Farcaster protocol, runs the Farcaster client, and operates Clanker after acquiring Farcaster from Merkle in January 2026
• Key claims:
  • Neynar’s homepage markets it as the software platform for the Farcaster ecosystem, says builders can reach a network of 2.6M+ accounts and $500M+ in connected wallets, and explicitly links the company to games, commerce, agents, and social apps
  • The Quickstart docs say Neynar provides APIs to interact with Farcaster while abstracting the complexity of querying hubs directly, which is the clearest primary-source statement of the company’s middleware role
  • The docs show Neynar doing more than read APIs: mini-app hosting, notifications, sign-in/onboarding, developer tooling, and even autonomous agent account creation all sit inside the same company-run surface
  • The Sign In / onboarding docs show Neynar turning Farcaster identity and social-graph data into reusable onboarding and profile infrastructure for outside apps across EVM and Solana contexts
  • Neynar’s acquisition post says a significant portion of Farcaster products already ran on Neynar infrastructure and that Neynar will now maintain the protocol, run the Farcaster client, and operate Clanker, which materially changes the operator map of the ecosystem
• Whitepaper: No classic whitepaper or litepaper is the key artifact here. The strongest primary materials are Neynar’s homepage, docs index and quickstart, Sign In / onboarding docs, acquisition post, and public GitHub organization; see ../whitepapers/neynar-primary-sources-2026-04-25.md for the earlier source capture and treat the January 2026 acquisition post as the important later operator-boundary update.
• Sources:
  • https://neynar.com/
  • https://docs.neynar.com/
  • https://docs.neynar.com/llms.txt
  • https://docs.neynar.com/reference/quickstart
  • https://docs.neynar.com/docs/supercharge-your-sign-in-with-ethereum-onboarding-with-farcaster
  • https://docs.neynar.com/docs/autonomous-farcaster-agent.md
  • https://neynar.com/blog/neynar-is-acquiring-farcaster
  • https://github.com/neynarxyz

Internal linkages

• Project-layer alias: neynar.
• Strongest protocol-layer counterpart: farcaster.
• Useful comparison lens: a company can start as developer middleware and then become part of the protocol’s practical operating shell when it also runs the dominant client and adjacent ecosystem services.

Protocol / company boundary

• Farcaster itself still belongs in projects/ because the contracts, hubs, account model, storage rules, recovery model, and app-key design remain a real protocol surface.
• Neynar belongs in companies/ because the named organization now controls major middleware and distribution surfaces around that protocol: API access, indexing defaults, onboarding flows, notifications, developer tooling, and, after the acquisition, the main client and direct protocol maintenance path.
• That split matters because how Farcaster works and who now operates the easiest path into Farcaster are no longer the same question.

Control surface

• Practical authority sits in API-key issuance, data indexing and query defaults, notification and mini-app host workflows, onboarding / sign-in packaging, account-registration helpers, and the company-run abstractions developers choose instead of raw hub interaction.

• Additional leverage now sits in protocol maintenance, main-client operation, and Clanker operation, because those surfaces can shape what users and builders treat as canonical even when the underlying protocol remains more open than a normal social app.

• Read Neynar as the company-run middleware and default-experience boundary around Farcaster, not as a neutral protocol primitive.

• Last reviewed: 2026-08-06 UTC