x402 List

x402 Protocol Service Directory

Neynar

Data PAYMENT-READY

payment-ready until 2026-09-09

Farcaster protocol data API (users, casts, feeds, reactions). x402 pay-per-request in USDC on Base.

Pay from $0.01 per request in USDC on Base, settled onchain via the x402 protocol, no signup, no API key needed.

measured since 2026-01-16 (start of our harvest window) · $179.26 all-time · last settled 2026-07-17

BASE URL https://api.neynar.com WEBSITE https://neynar.com ENDPOINTS 3 NETWORK Base ASSET USDC MEMBER SINCE 2026-02-09 MONITORED SINCE 2026-04-15

VERDICT

ranking generation 3

solid 83/100 #211 of 257 in Data by measured score

What the score read on this service: status online, 100% uptime 30d, 680ms response p95, x402 compliance 13 of 14, $0.01 price against the category, on-chain traction measured. Each of those is measured, and each is published in full below.

The score comes from our own monitoring, never from reviews, operator claims, or a language model: reliability, x402 compliance, price against the category, a deterministic risk flag, and a small on-chain traction term, weighted by ranking generation 3. It is not placement anyone can buy: the paid verify tier is reported beside it and is not one of its inputs. Every component below stays published and read-only.

It is a score inside Data, and only there: price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, which here means 257 listings, this one among them. That set is wider than the 257 the position above is counted against, because a listing we have measured too little of to rank still sits in the field the price and the speed are normalized over. The same service in a different field would read differently. The same engine answers GET /api/v1/best, and asked for a different pool (the whole directory, or another filter) it returns a different number for this service under this same ranking generation. Neither is more correct: they answer different questions, and the methodology states which is which.

Bands on the 0 to 100 measured score: strong at 93 and above, solid from 75, mixed from 55, weak below 55. Price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, so the score places a service in its own field.

ALTERNATIVES IN DATA

Other Data services in this directory, ordered by the same measured score. The figures are ours: 30-day uptime from our own probes, 30-day settlement volume read on-chain (a conservative undercount, and null where we cannot measure it, never a zero).

Ranked alternative x402 services in the same category, with band, measured score, 30-day uptime and 30-day on-chain settlement volume
SERVICE BAND SCORE UPTIME 30D VOL 30D
ThirdMade Shelf strong 99 100% ---
API Acre strong 99 99.7% ---
IPIntel.ai x402 Tools strong 99 100% ---
WebberSites x402 Data API strong 99 100% ---
glim.sh strong 99 100% ---
5 of 256 other ranked services in Data · see the whole category

ASSESSMENT

updated 6h ago

The parts the verdict above is computed from, each with its proof. Click any chip. Measured values stay read-only; unknown is honest, and an unknown is never counted as a zero.

reliability 100%
uptime 24h
100%
uptime 7d
100%
uptime 30d
100%
uptime 90d
99.7%
response p95
680ms
avg response
292ms
total checks
7,422

Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.

compliance A (13/14): declares the current x402 version (2)

13 of 14 x402 conformance checks pass; failing: declares the current x402 version (2). Full checklist below.

jump to compliance checklist

price $0.01 (p58 in Data)
price (min)
$0.01
category percentile (min)
p58 in Data
endpoints / prices
3 / 1
model
flat
stability
100%
risk clean

No deterministic risk flag. Risk fires only on an exact blocklist match, or a reserved-brand name with a mismatched verified payTo. Never from low uptime, a high price, or a model guess.

domain age
1400d
registrar
Amazon Registrar, Inc.
hosting
custom
domain created
2022-11-01

Identity facts, not a risk score.

traction $0.00 30d · 0 buyers
volume 30d
$0.00
buyers 30d
0
settlements 30d
0
measured since
2026-01-16 (start of our harvest window)
last settlement
2026-07-17
top buyer share
-
trend 7d vs 30d
-
networks
eip155:8453
volume all-time
$179.26
settlements all-time
36,246
median settlement 30d
-
max settlement 30d
-
settled via
-

Conservative undercount: only USDC settlements via facilitators we measure are counted. A measured floor, not an estimate.

Top buyer share is a concentration signal, not part of the ranking score.

WHAT IT DOES

ai-derived

Provides API services for accessing Farcaster social network data including casts, feeds, and user information

category
social-api
in
query params
social-mediafarcasterapidata-fetching

AI-generated summary. The measured data is never altered by it.

ENDPOINTS

Service endpoints with HTTP method, path, description, pricing, and network
METHOD PATH DESCRIPTION PRICE NETWORK ASSET 402 CHANNEL
GET /v2/farcaster/cast Fetch cast by hash $0.01 Base USDC body (v1 style)
GET /v2/farcaster/feed Farcaster feed $0.01 Base USDC body (v1 style)
GET /v2/farcaster/user/by_username Lookup user by Farcaster handle $0.01 Base USDC body (v1 style)
3 endpoints

REQUEST / RESPONSE EXAMPLE

An unpaid request to GET /v2/farcaster/cast returns HTTP 402 with the payment terms. Settle onchain via your facilitator, then retry with the X-Payment header.

// request
curl -i 'https://api.neynar.com/v2/farcaster/cast'
// 402 response (captured by monitor) · 3 payloads · click to expand
[
  {
    "error": "X-PAYMENT header or API key required",
    "accepts": [
      {
        "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
        "extra": {
          "name": "USD Coin",
          "version": "2"
        },
        "payTo": "0xA6a8736f18f383f1cc2d938576933E5eA7Df01A1",
        "scheme": "exact",
        "network": "base",
        "mimeType": "",
        "resource": "http://api.neynar.com/farcaster/user/by_username",
        "description": "",
        "outputSchema": {
          "input": {
            "type": "http",
            "method": "GET",
            "discoverable": true
          }
        },
        "maxAmountRequired": "10000",
        "maxTimeoutSeconds": 60
      }
    ],
    "x402Version": 1
  },
  {
    "error": "X-PAYMENT header or API key required",
    "accepts": [
      {
        "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
        "extra": {
          "name": "USD Coin",
          "version": "2"
        },
        "payTo": "0xA6a8736f18f383f1cc2d938576933E5eA7Df01A1",
        "scheme": "exact",
        "network": "base",
        "mimeType": "",
        "resource": "http://api.neynar.com/farcaster/cast",
        "description": "",
        "outputSchema": {
          "input": {
            "type": "http",
            "method": "GET",
            "discoverable": true
          }
        },
        "maxAmountRequired": "10000",
        "maxTimeoutSeconds": 60
      }
    ],
    "x402Version": 1
  },
  {
    "error": "X-PAYMENT header or API key required",
    "accepts": [
      {
        "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
        "extra": {
          "name": "USD Coin",
          "version": "2"
        },
        "payTo": "0xA6a8736f18f383f1cc2d938576933E5eA7Df01A1",
        "scheme": "exact",
        "network": "base",
        "mimeType": "",
        "resource": "http://api.neynar.com/farcaster/feed",
        "description": "",
        "outputSchema": {
          "input": {
            "type": "http",
            "method": "GET",
            "discoverable": true
          }
        },
        "maxAmountRequired": "10000",
        "maxTimeoutSeconds": 60
      }
    ],
    "x402Version": 1
  }
]

OVER TIME

All charts use the 30d selector; each series spans only the dates it has data for. Every series is also served as JSON at /api/v1/services/neynar/price, /scores, /volume and /buyers. On-chain volume and distinct buyers are measured over the service's settlement address and are a conservative undercount (only settlements that reach a measured facilitator are counted). The on-chain series roll up hourly, so the latest day can be up to about an hour behind; distinct buyers are counted per payout address, so a service that settles to more than one address is an upper bound.

UPTIME
08-04 · uptime 100.0% · 257ms avg08-05 · uptime 100.0% · 324ms avg08-06 · uptime 100.0% · 277ms avg08-07 · uptime 100.0% · 267ms avg08-08 · uptime 100.0% · 307ms avg08-09 · uptime 100.0% · 313ms avg08-10 · uptime 100.0% · 245ms avg08-11 · uptime 100.0% · 258ms avg08-12 · uptime 100.0% · 268ms avg08-13 · uptime 100.0% · 221ms avg08-14 · uptime 100.0% · 219ms avg08-15 · uptime 99.6% · 258ms avg08-16 · uptime 100.0% · 228ms avg08-17 · uptime 100.0% · 238ms avg08-18 · uptime 100.0% · 256ms avg08-19 · uptime 100.0% · 261ms avg08-20 · uptime 100.0% · 311ms avg08-21 · uptime 100.0% · 284ms avg08-22 · uptime 100.0% · 250ms avg08-23 · uptime 100.0% · 267ms avg08-24 · uptime 100.0% · 308ms avg08-25 · uptime 100.0% · 348ms avg08-26 · uptime 100.0% · 365ms avg08-27 · uptime 100.0% · 364ms avg08-28 · uptime 100.0% · 362ms avg08-29 · uptime 100.0% · 396ms avg08-30 · uptime 100.0% · 418ms avg08-31 · uptime 100.0% · 339ms avg09-01 · uptime 100.0% · 334ms avg09-02 · uptime 100.0% · 413ms avg08-0409-02
30d UPTIME 100%
RESPONSE TIME
08-04 · 257ms avg08-04 · 257ms avg08-05 · 324ms avg08-05 · 324ms avg08-06 · 277ms avg08-06 · 277ms avg08-07 · 267ms avg08-07 · 267ms avg08-08 · 307ms avg08-08 · 307ms avg08-09 · 313ms avg08-09 · 313ms avg08-10 · 245ms avg08-10 · 245ms avg08-11 · 258ms avg08-11 · 258ms avg08-12 · 268ms avg08-12 · 268ms avg08-13 · 221ms avg08-13 · 221ms avg08-14 · 219ms avg08-14 · 219ms avg08-15 · 258ms avg08-15 · 258ms avg08-16 · 228ms avg08-16 · 228ms avg08-17 · 238ms avg08-17 · 238ms avg08-18 · 256ms avg08-18 · 256ms avg08-19 · 261ms avg08-19 · 261ms avg08-20 · 311ms avg08-20 · 311ms avg08-21 · 284ms avg08-21 · 284ms avg08-22 · 250ms avg08-22 · 250ms avg08-23 · 267ms avg08-23 · 267ms avg08-24 · 308ms avg08-24 · 308ms avg08-25 · 348ms avg08-25 · 348ms avg08-26 · 365ms avg08-26 · 365ms avg08-27 · 364ms avg08-27 · 364ms avg08-28 · 362ms avg08-28 · 362ms avg08-29 · 396ms avg08-29 · 396ms avg08-30 · 418ms avg08-30 · 418ms avg08-31 · 339ms avg08-31 · 339ms avg09-01 · 334ms avg09-01 · 334ms avg09-02 · 413ms avg09-02 · 413ms avg08-0409-02
AVG RESP 295ms
PRICE (captured 402, USD)
08-03 · $0.0109-02 · $0.01$0.0108-0309-02

Median across 3 endpoints. Use the selector to isolate one.

SUB-SCORES (uptime + x402 compliance)
08-03 uptime: 100.0% compliance: 93% checks08-04 uptime: 100.0% compliance: 93% checks08-05 uptime: 100.0% compliance: 93% checks08-06 uptime: 100.0% compliance: 93% checks08-07 uptime: 100.0% compliance: 93% checks08-08 uptime: 100.0% compliance: 93% checks08-09 uptime: 100.0% compliance: 93% checks08-10 uptime: 100.0% compliance: 93% checks08-11 uptime: 100.0% compliance: 93% checks08-12 uptime: 100.0% compliance: 93% checks08-13 uptime: 100.0% compliance: 93% checks08-14 uptime: 100.0% compliance: 93% checks08-15 uptime: 100.0% compliance: 93% checks08-16 uptime: 100.0% compliance: 93% checks08-17 uptime: 100.0% compliance: 93% checks08-18 uptime: 100.0% compliance: 93% checks08-19 uptime: 100.0% compliance: 93% checks08-20 uptime: 100.0% compliance: 93% checks08-21 uptime: 100.0% compliance: 93% checks08-22 uptime: 100.0% compliance: 93% checks08-23 uptime: 100.0% compliance: 93% checks08-24 uptime: 100.0% compliance: 93% checks08-25 uptime: 100.0% compliance: 93% checks08-26 uptime: 100.0% compliance: 93% checks08-27 uptime: 100.0% compliance: 93% checks08-28 uptime: 100.0% compliance: 93% checks08-29 uptime: 100.0% compliance: 93% checks08-30 uptime: 100.0% compliance: 93% checks08-31 uptime: 100.0% compliance: 93% checks09-01 uptime: 100.0% compliance: 93% checks09-02 uptime: 100.0% compliance: 93% checksuptimecompliance08-0309-02

checklist grew 11->14 on 2026-07-28; a step here is a metric change, not a regression

PILLARS OVER TIME (measured)

Measured site and economics pillars from the assessment history, so the latest value shown elsewhere on this page reads as a point on a trend rather than a permanent state.

VOLUME (on-chain settlement, USD)
no on-chain volume yet
DISTINCT BUYERS
no distinct buyers yet

COMPLIANCE

13/14 checks pass · grade A · failing: declares the current x402 version (2)

last 402 captured 2026-06-16 · last up 2026-09-02

  • 402 payload captured
  • accepts[] array present
  • payTo address recoverable
  • payTo at accepts[0].payTo (conformant shape)
  • payTo is a valid on-chain address
  • atomic price declared
  • atomic price in a sane range
  • asset (token) address declared
  • network resolves to CAIP-2
  • payment scheme declared
  • served over HTTPS
  • declares the current x402 version (2)
  • EIP-712 domain parameters present on every EVM entry
  • x402 v2 envelope delivered in the payment-required header

SITE PILLARS

  • homepage reachable
  • openapi doc
  • pricing page
  • llms.txt
  • robots.txt
  • terms page
recent checks (18) live · click to expand
TIME STATUS RESP CAUSE
● OK 276ms
● SLOW 637ms
● OK 383ms
● OK 317ms
● OK 224ms
● OK 310ms
● SLOW 1608ms
● OK 311ms
● OK 297ms
● SLOW 1138ms
● OK 297ms
● OK 378ms
● OK 336ms
● OK 363ms
● OK 319ms
● OK 276ms
● OK 309ms
● OK 425ms

EMBED THIS BADGE

Show that Neynar is monitored on x402-list. Paste this on your site or README, it links back to this live listing.

Neynar listed on x402-list
status
Neynar uptime on x402-list
live uptime
// HTML
<a href="https://x402-list.com/services/neynar?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/neynar.svg" alt="Neynar listed on x402-list" height="28">
</a>
// Markdown
[![Neynar on x402-list](https://x402-list.com/badge/neynar.svg)](https://x402-list.com/services/neynar?utm_source=badge&utm_medium=referral&utm_campaign=embed)
// HTML · live uptime variant
<a href="https://x402-list.com/services/neynar?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/neynar.svg?data=uptime" alt="Neynar uptime on x402-list" height="28">
</a>

RUN THIS SERVICE?

Keep this listing accurate: propose changes to the name, description, website, category or add new endpoints to monitor. Ownership is verified with a domain proof and every change is reviewed manually; measured data stays read-only.

[ update this listing ]

Earn the verified tier: x402list pays a real call to this endpoint and, if it delivers, the service is delivery-verified. The fee covers the cost of the probe, not the badge; there is no refund if the call does not deliver. Agent and API only, no in-browser signing. See /api.

[ verify this service ($0.25) ]

To request delisting, email info@x402-list.com or update your listing at /services/neynar/update.