Agent Tools
List
Back to directory

Surf Twitter

https://twitter.surf.cascade.fyi/communities/%7Bid%7D
● healthy search

Pay-per-use Twitter/X data API with x402 micropayments.

Category
search
Chains
base, eip155:8453, solana, solana:5eykt4usfv8p8njdtrepy1vzqkqzkvdp
Price
$0.0010–$0.0050 USDC

Quality grade

How grading works
B+ 69.8 / 100
Availability 20.0 / 20
Endpoint responded (HTTP 200)
Payability 15.0 / 15
  • ✓ Answers a real HTTP 402 challenge
  • ✓ Publishes a /.well-known/x402 descriptor
  • ✓ Payment address on record
  • ✓ Settlement network declared
  • ✓ Price declared
Demand 19.5 / 35
60 distinct payers, 10627 USDC transfers in the last 30 days; discounted because most transfers come from few payers
Performance 2.7 / 10
Last probe answered in 1517 ms (full marks at 200 ms or less)
Readiness 12.6 / 15
Agent readiness 84/100
Owner verified 0.0 / 5
Nobody has claimed this listing yet
Endpoint last checked 20 h ago. On-chain activity last read 3 d ago. Availability and on-chain demand are both re-probed daily; the grade updates automatically on the next pass. This grade sets search order and leaderboards; the readiness score below is shown for reference only.

x402 readiness

B · 84/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B+, 69.8/100), which weighs availability, payability and on-chain demand. How the two differ

Valid payment requirements 10/10 Payment requirements carry a payee, a mainnet network and a price.
Live 402 challenge 20/25 Endpoint reachable; its 402 challenge was seen earlier (1517 ms).
x402 version n/a x402 version not observed yet.
Signed descriptor n/a No x402 standard defines a signed descriptor.
Uptime (30 days) 15/15 32/32 probes succeeded over 30 days (100%).
Resource declaration 8/10 33 paid resources; 33 sampled lack a description.
Verified identity 5/10 Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
Freshness + modern flags 5/5 seen in a source within 7 days; declares x402.
Security declaration n/a Payment is the access control for an x402 resource.
Applicable criteria total 75 points, scaled to 100.
Responsiveness: Responsive (1517 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Payment evidence: x402_challenge — We sent a request and got a live HTTP 402 challenge. Also: x402_manifest, catalog_listing. Qualifies the payment claim; adds no points.
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily probe of the paid endpoint, its payment requirements and 30-day probe history. Signed descriptor and security declaration are n/a for x402 (payment is the access control), as is an x402 version we have not observed; the remaining points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. It also feeds 15 points of the x402 quality grade.

Compared with peers

Against 10,082 reachable x402 APIs in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness
Higher than 67% of peers
This listing 84 · peer median 78
Latency
Faster than 5% of peers
This listing 1,517 ms · peer median 205 ms

Where it loses the most points, and how to win them back

  • Live 402 challenge −5 — Answer the paid path with a valid 402 challenge.
    Now: Endpoint reachable; its 402 challenge was seen earlier (1517 ms).
  • Verified identity −5 — Claim the listing and prove control of its domain.
    Now: Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
  • Resource declaration −2 — Declare each paid resource with its input and output schema.
    Now: 33 paid resources; 33 sampled lack a description.

How many agent tools actually work · All statistics

Paid endpoints

33 resource(s) advertised by this origin. Each price below is that resource's own x402 price; the headline price is the range across them.

POST https://twitter.surf.cascade.fyi/api/v1/twitter/search
POST https://twitter.surf.cascade.fyi/api/v1/twitter/get
POST https://twitter.surf.cascade.fyi/api/v1/reddit/search
POST https://twitter.surf.cascade.fyi/api/v1/reddit/get
POST https://twitter.surf.cascade.fyi/api/v1/web/search
POST https://twitter.surf.cascade.fyi/api/v1/web/fetch
POST https://twitter.surf.cascade.fyi/api/v1/github/search
POST https://twitter.surf.cascade.fyi/api/v1/github/get
POST https://twitter.surf.cascade.fyi/api/v1/twitter/tweets/search
POST https://twitter.surf.cascade.fyi/api/v1/twitter/tweets/:id
POST https://twitter.surf.cascade.fyi/api/v1/twitter/tweets
POST https://twitter.surf.cascade.fyi/api/v1/twitter/tweets/:id/replies
POST https://twitter.surf.cascade.fyi/api/v1/twitter/tweets/:id/quotes
POST https://twitter.surf.cascade.fyi/api/v1/twitter/tweets/:id/retweeters
POST https://twitter.surf.cascade.fyi/api/v1/twitter/tweets/:id/thread
POST https://twitter.surf.cascade.fyi/api/v1/twitter/tweets/:id/article
POST https://twitter.surf.cascade.fyi/api/v1/twitter/users/search
POST https://twitter.surf.cascade.fyi/api/v1/twitter/users/relationship
POST https://twitter.surf.cascade.fyi/api/v1/twitter/users/:ref
POST https://twitter.surf.cascade.fyi/api/v1/twitter/users
POST https://twitter.surf.cascade.fyi/api/v1/twitter/users/:ref/tweets
POST https://twitter.surf.cascade.fyi/api/v1/twitter/users/:ref/mentions
POST https://twitter.surf.cascade.fyi/api/v1/twitter/users/:ref/followers
POST https://twitter.surf.cascade.fyi/api/v1/twitter/users/:ref/following
POST https://twitter.surf.cascade.fyi/api/v1/twitter/users/:ref/verified_followers
POST https://twitter.surf.cascade.fyi/api/v1/twitter/lists/:id/tweets
POST https://twitter.surf.cascade.fyi/api/v1/twitter/lists/:id/members
POST https://twitter.surf.cascade.fyi/api/v1/twitter/trends
POST https://twitter.surf.cascade.fyi/api/v1/amazon/search
POST https://twitter.surf.cascade.fyi/api/v1/amazon/get
POST https://twitter.surf.cascade.fyi/api/v1/youtube/get
POST https://twitter.surf.cascade.fyi/api/v1/telegram/get
POST https://twitter.surf.cascade.fyi/api/v1/telegram/search

How to call

cURL · x402-fetch / x402-axios will auto-handle 402
curl -sS -i -X GET https://twitter.surf.cascade.fyi/communities/%7Bid%7D  # expect HTTP 402 Payment Required (about $0.001/call)
/.well-known/x402.json
https://twitter.surf.cascade.fyi/.well-known/x402

Listed in

Directories this entry was found in.

x402scan since 2026-05-22 paygent-discover since 2026-07-03