passlisted in Coinbase#3 by calls of 6 on this host
0.01 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 3
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-09-29 16:52 UTC
- First observed by TOLLderived
- 2026-09-21
- Pricederived
- 0.01 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 2 times across 37 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
farcaster recall is a POST endpoint at x402.billionaireorder.com, listed in the Coinbase registry and filed by TOLL under search.
farcaster recall is priced at 0.01 USDC on Base.
The request to farcaster recall is a json body with the fields chain and input_data.
A response from farcaster recall, as declared, includes fid and facts.
The daily sweep got a valid payment challenge from farcaster recall on 2026-10-01, as at every sweep since 2026-09-22.
farcaster recall is one of 6 listed endpoints on x402.billionaireorder.com, tied 3rd by calls with 3 others among them.
farcaster recall takes 14% of the calls counted across x402.billionaireorder.com.
Over 30 days: 3 calls, 2 payers.
farcaster recall was last called 2 days before the snapshot.
Closest in price to farcaster recall within search: research people at win.oneshotagent.com and search at x402.tavily.com.
Among comparable prices in search, farcaster recall sits above 38% of them.
Across search, 2,195 endpoints carry counters and farcaster recall out-counts 66% of them.
Its payee wallet receives for 6 listed endpoints on one host.
The price of farcaster recall is declared by 785 other listings in search too.
the payment options, as of 2026-10-01 22:40 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0x2f58f2…ee265e |
the checks, as of 2026-10-01 09:49 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-01 09:49 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 09:16 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 21:21 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-23 08:14 UTC | pass | 0 | daily-2026-09-23 |
| 2026-09-22 08:27 UTC | pass | 0 | daily-2026-09-22 |
| 2026-09-22 05:22 UTC | pass | 0 | new-after-daily-2026-09-21 |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-09-29 16:52 UTC · method · live
The input and output block
{
"input": {
"body": {
"chain": "eip155:8453",
"input_data": "trading preferences for fid 3"
},
"type": "http",
"method": "POST",
"bodyType": "json",
"bodyFields": {
"chain": {
"type": "string",
"required": false,
"description": "Chain eip155:8453"
},
"input_data": {
"type": "string",
"required": true,
"description": "Wallet address or input data"
},
"agent_ref_hash": {
"type": "string",
"required": false,
"description": "Agent ref"
}
}
},
"output": {
"type": "json",
"example": {
"fid": 3,
"facts": [
"likes memecoins"
]
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-10-01 22:40 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "farcaster recall on x402.billionaireorder.com", snapshot of 2026-10-01 22:40 UTC. https://tollindex.com/e/x402-billionaireorder-com-v1-farcaster-recall-e74511/at/2026-10-01T22-40Z. Accessed [access date].
BibTeX
@misc{toll-e-x402-billionaireorder-com-v1-farcaster-recall-e74511-2026-10-01T22-40Z,
author = {TOLL},
title = {farcaster recall on x402.billionaireorder.com},
howpublished = {\url{https://tollindex.com/e/x402-billionaireorder-com-v1-farcaster-recall-e74511/at/2026-10-01T22-40Z}},
year = {2026},
month = {10},
note = {Pinned view of the snapshot of 2026-10-01 22:40 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.