task-radar-x402.vercel.app
Paid API · task-radar-x402.vercel.app · found in a public list · checked since 2026-11-18
Not checked yet
GET https://task-radar-x402.vercel.app/api/funding-historyNo per-call price knownThe name is the registry's label, not ours. Not reviewed by a person. See 42 endpoints from task-radar-x402.vercel.app.
Our checks
An unpaid request daily, from eastern North AmericaNo recent checks to show yet
0 passed, 0 failed, 30 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Details
Payment terms
- Price per call
- —
- Protocols
- none seen yet
- Networks
- —
- Terms changes, 90 days
- no valid payment request yet
Price from the registry's payment terms; protocols and networks as the registry states. Definitions
Access
- Our latest check
- not observed
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Links
Pages we read:
- llms.txt: task-radar-x402.vercel.app/llms.txt, read
Its own links, from its llms.txt, under its own headings and names. These are its words, not ours:
Endpoints (30)
- GET /api/radar
- GET /api/sample
- GET /api/token-risk
- GET /api/markdown
- GET /api/price
- GET /api/gas
- GET /api/ens
- GET /api/tvl
- GET /api/wallet
- GET /api/fear-greed
- GET /api/stablecoins
- GET /api/yields
- GET /api/dex-search
- GET /api/chains
- GET /api/domain
- GET /api/abi
- GET /api/tx
- GET /api/signature
- GET /api/token-price
- GET /api/token-pairs
- GET /api/url-meta
- GET /api/news
- GET /api/fees
- GET /api/dex-volumes
- GET /api/trending
- GET /api/block
- GET /api/erc20
- GET /api/address-type
- GET /api/market-global
- GET /api/sectors
The first 30 of the 39 links in its llms.txt; the rest are in the file itself.
Links only (links/4): we follow none of them when showing this page, and a link is not a recommendation. How links are chosen.
Listing
In the capability tree: Other (not placed in a branch yet) (primary). Placed by keyword rules (placement-rules/3, tree/3) on 2026-11-18. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/6): ✗ what it does is unclear to our placement; not checked yet.
Purpose tags: none in the registry
Recent probes
| When | Result | Networks offered | Time to headers |
|---|---|---|---|
| Not probed yet. Each discovered service is probed on its published schedule, from hourly to monthly by usage. | |||
What these figures do not show
- A passing probe means the endpoint answered an unpaid request with a valid payment request on a production network (x402 on a mainnet network, or MPP on Tempo mainnet). It does not show that a paid call succeeds or returns useful results.
- Payer and call counts are the registry's own figures, not our measurements.
- The registry's description is not republished.
- Limited evidence: monitored for under 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_19401ead31a747cd