Neynar
Managed Farcaster API that provides a clean REST interface to Farcaster social data without running your own Hub node. Neynar handles the Hub infrastructure and provides endpoints for user lookup, cast feeds, reactions, follows, channel data, Frames interactions, and posting casts (including managed Signer creation). The de facto standard way to build Farcaster applications via API.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
HTTPS enforced. Neynar holds managed Signer private keys — this is a custodial trust model. For non-custodial signing, use raw Farcaster Hub. API key grants full account access with no scope granularity.
⚡ Reliability
Best When
You want to build on Farcaster without running Hub infrastructure — Neynar provides Calendly-level simplicity for Farcaster API access.
Avoid When
You need decentralized infrastructure without API dependencies, or your users are not in the crypto/web3 space.
Use Cases
- • Post casts (Farcaster posts) programmatically on behalf of users with Neynar-managed Signers — simplest way for agents to publish to Farcaster
- • Fetch user timelines, cast threads, and reaction data for building agent-powered Farcaster analytics or content tools
- • Resolve Farcaster usernames and FIDs to ETH/Solana wallet addresses for agent cross-platform identity workflows
- • Monitor specific channels or hashtags on Farcaster for agent-driven content analysis and social listening
- • Build Farcaster Frames (interactive mini-apps in casts) with Neynar's Frames validation and analytics APIs
Not For
- • Teams that need fully decentralized infrastructure with no third-party API dependency — run your own Hub for true decentralization
- • Applications requiring Twitter/X-scale social data — Farcaster has ~300K monthly active users vs Twitter's hundreds of millions
- • Non-crypto social use cases — Farcaster's user base is crypto-native
Interface
Authentication
Single API key passed as api_key header. Signer management for posting casts requires registering a Signer via Neynar's Signer API (involves user approval via wallet signature). Read-only operations need only API key.
Pricing
Free tier is generous for development. Signer creation (for posting) requires credits beyond free tier. Pricing is per-API-call with rate limit tiers. No credit card required for free tier.
Agent Metadata
Known Gotchas
- ⚠ Posting casts requires a registered Signer — Signer creation requires the user to approve via wallet signature; this is a one-time setup but requires user interaction
- ⚠ Neynar Signers are managed signers — Neynar holds the private key; for true key custody, use raw Farcaster Hub with your own Signer keys
- ⚠ Cast creation is not idempotent — network timeouts may result in duplicate casts; implement cast hash tracking to detect duplicates
- ⚠ Farcaster FIDs (user IDs) are on-chain integers — username lookup requires additional API call to resolve FID from username
- ⚠ Frames API is separate from basic Farcaster API — Frame validation and analytics use different endpoints
- ⚠ Rate limits are per API key — agents making requests on behalf of many users should be aware that all traffic shares a single key's rate limit
- ⚠ Webhook events are best-effort delivery — implement idempotency on webhook handlers for reliable processing
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Neynar.
Scores are editorial opinions as of 2026-03-06.