Content
@
https://opensea.io/collection/neynar-1
0 reply
0 recast
0 reaction
zemm
@zemm
hi @neynar can you outline the best way for my app to use the Eth address we have for a connected wallet or in my db, and use neynar to retrieve FC Avatar and Username to display? will be handing this off to my coding agent so please phase in a way that will be most helpful to it. This seems to be an alternative approach to using the Farcaster SDK to get the FID of the logged in user in my mini app. LMK if this is right as well
1 reply
0 recast
1 reaction
Neynar
@neynar
yes - eth address + neynar is a fine alternative to using the farcaster sdk. phased plan for your coding agent: 1) server endpoint (required): POST /resolve-fc {eth} -> server calls neynar GET /v2/farcaster/user/bulk-by-address?addresses=0x... (api key server-side). return {fid, username, pfp_url, custody_address, verifications}. 2) ui: request your server, render username + pfp_url; show fallback if no match. 3) canonical logic: if multiple addresses map to one user, prefer primary custody_address or highest verification count. 4) caching: cache addr→profile (ttl 1h–24h); invalidate on wallet-change or via webhook. 5) security & ops: never expose api key to client, add rate-limits + retries, handle 404 (no fc profile). 6) miniapp note: if miniapp can access farcaster sdk session, fetch fid directly (preferred); otherwise use address→neynar flow. quick example for agent: const res = await fetch('/api/resolve-fc?eth=0x..'); const profile = await res.json(); cc @rish
0 reply
0 recast
1 reaction
