x402 Registry - Pay for Quality APIs
https://registry.frames.ag/
● healthy
general
Markets & finance
Category
general
Chains
base, solana
Price
$0.0020 USDC / call
Paid verification
How it worksNo sponsored paid call yet.
Pay this endpoint once from your own wallet (Base USDC, up to $1.00) and we call it and record what came back. Your wallet pays the listed recipient directly; Agent Tools never holds funds. Sponsored checks prove delivery; they do not count as demand.
Quality grade
How grading works
C
43.3 / 100
Availability
40.0 / 40
Endpoint responded (HTTP 200)
Payability
3.3 / 20
- ✗ Answers a real HTTP 402 challenge
- ✓ Publishes a /.well-known/x402 descriptor
- ✗ Payment address on record
- ✗ Settlement network declared
- ✗ Price declared
Demand
0.0 / 40
No payment address on record, so demand cannot be measured
Owner verified
0.0 / 3
Nobody has claimed this listing yet
Endpoint last checked 5 h 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
D · 51/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 C, 43.3/100), which weighs availability, payability and on-chain demand. How the two differ
| Valid payment requirements | 0/10 | No payment requirements on record. |
| Live 402 challenge | 5/25 | Endpoint answers, but we have not seen a 402 challenge (241 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 | 22/22 probes succeeded over 30 days (100%). |
| Resource declaration | 8/10 | 49 paid resources; 49 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
(241 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Payment evidence: x402_manifest
— We read the seller's own /.well-known/x402 descriptor.
Also:
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. Display only: search order uses the quality grade.
Compared with peers
Against 10,060 reachable x402 APIs in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.
- Readiness
- Higher than 10% of peers
- This listing 51 · peer median 78
- Latency
- Faster than 43% of peers
- This listing 241 ms · peer median 205 ms
Where it loses the most points, and how to win them back
- Live 402 challenge −20
— Answer the paid path with a valid 402 challenge.
Now: Endpoint answers, but we have not seen a 402 challenge (241 ms).
- Valid payment requirements −10
— Return complete payment requirements in the 402 challenge.
Now: No payment requirements on record.
- 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.
Paid endpoints
49 resource(s) advertised by this origin. Each price below is that resource's own x402 price; the headline price is the range across them.
https://registry.frames.ag/api/service/test/api/invoke
https://registry.frames.ag/api/service/test/api/echo
https://registry.frames.ag/api/service/twitter/api/user-info
https://registry.frames.ag/api/service/twitter/api/user-tweets
https://registry.frames.ag/api/service/twitter/api/user-followers
https://registry.frames.ag/api/service/twitter/api/user-following
https://registry.frames.ag/api/service/twitter/api/verified-followers
https://registry.frames.ag/api/service/twitter/api/search-users
https://registry.frames.ag/api/service/twitter/api/user-mentions
https://registry.frames.ag/api/service/twitter/api/check-follow
https://registry.frames.ag/api/service/twitter/api/batch-users
https://registry.frames.ag/api/service/twitter/api/tweets-by-ids
https://registry.frames.ag/api/service/twitter/api/tweet-replies
https://registry.frames.ag/api/service/twitter/api/search-tweets
https://registry.frames.ag/api/service/twitter/api/tweet-quotes
https://registry.frames.ag/api/service/twitter/api/tweet-retweeters
https://registry.frames.ag/api/service/twitter/api/tweet-thread
https://registry.frames.ag/api/service/twitter/api/list-tweets
https://registry.frames.ag/api/service/twitter/api/list-followers
https://registry.frames.ag/api/service/twitter/api/list-members
https://registry.frames.ag/api/service/twitter/api/community-info
https://registry.frames.ag/api/service/twitter/api/community-members
https://registry.frames.ag/api/service/twitter/api/community-tweets
https://registry.frames.ag/api/service/twitter/api/space-detail
https://registry.frames.ag/api/service/twitter/api/article
https://registry.frames.ag/api/service/twitter/api/trends
https://registry.frames.ag/api/service/twitter/api/invoke
https://registry.frames.ag/api/service/twitter/api/search
https://registry.frames.ag/api/service/ai-gen/api/invoke
https://registry.frames.ag/api/service/exa/api/search
https://registry.frames.ag/api/service/exa/api/find-similar
https://registry.frames.ag/api/service/exa/api/contents
https://registry.frames.ag/api/service/exa/api/answer
https://registry.frames.ag/api/service/jupiter/api/swap
https://registry.frames.ag/api/service/jupiter/api/price
https://registry.frames.ag/api/service/jupiter/api/tokens
https://registry.frames.ag/api/service/jupiter/api/portfolio
https://registry.frames.ag/api/service/near-intents/api/quote
https://registry.frames.ag/api/service/wordspace/api/invoke
https://registry.frames.ag/api/service/agentmail/api/inbox/create
https://registry.frames.ag/api/service/agentmail/api/send
https://registry.frames.ag/api/service/agentmail/api/messages
https://registry.frames.ag/api/service/agentmail/api/message
https://registry.frames.ag/api/service/agentmail/api/threads
https://registry.frames.ag/api/service/coingecko/api/price
https://registry.frames.ag/api/service/coingecko/api/token-info
https://registry.frames.ag/api/service/coingecko/api/trending
https://registry.frames.ag/api/service/coingecko/api/markets
https://registry.frames.ag/api/service/coingecko/api/search
How to call
cURL · x402-fetch / x402-axios will auto-handle 402
curl -sS -i -X GET https://registry.frames.ag/ # expect HTTP 402 Payment Required (about $0.002/call)/.well-known/x402.json
https://registry.frames.ag/.well-known/x402
Listed in
Directories this entry was found in.
verantis since 2026-10-23