readx.sh
Web data API on Base, paid per request with x402.
- Endpoints18
- Price per requestfrom $0.01
- Outside payers · 7dn/a
- Answer 4023 of 3
Overview
- Seller wallet
- 0x13e060adcc6f4b731da8382b333027b8b2bff707
- Chains
- Base
- Hosts
- readx.sh
- CategoriesCategoriesAssigned automatically from the seller’s own listing text. A filter hint, not a claim about the service.
- Web data13Other3Identity2
- First seen
- 2026-10-05 · last seen 2026-11-20
Endpoints
EndpointsDescriptions are the seller's own words from the catalogue and are not checked by us. A listed price is a registration, not an observed charge.https://readx.sh/api/:name
A user's timeline: tweets, retweets and quotes. Example: GET /api/jack
BaseWeb data$0.01/ request
2026-11-20
https://readx.sh/api/:name/about
Account info: join date, base location, verification, username changes. Example: GET /api/jack/about
BaseIdentity$0.01/ request
2026-11-18
https://readx.sh/api/:name/affiliates
Accounts affiliated with a user (e.g. an organization's members). Example: GET /api/jack/affiliates
BaseOther$0.01/ request
2026-09-30
https://readx.sh/api/:name/followers
A user's followers (~200 per page; paginate with cursor until has_more is false). Example: GET /api/jack/followers
BaseWeb data$0.01/ request
2026-09-23
https://readx.sh/api/:name/following
Accounts a user follows (~200 per page; paginate with cursor until has_more is false). Example: GET /api/jack/following
BaseWeb data$0.01/ request
2026-09-06
https://readx.sh/api/:name/following_web
Accounts a user follows as shown on the web (~70 per page, capped at ~800; paginate with cursor until has_more is false). Example: GET /api/jack/following_web
BaseWeb data$0.01/ request
2026-10-21
https://readx.sh/api/:name/info
A user's profile info: id, name, bio, location, follower/following counts, verification. Example: GET /api/jack/info
BaseWeb data$0.01/ request
2026-11-13
https://readx.sh/api/:name/mentions
Tweets that mention a user (paginate with cursor until has_more is false). Example: GET /api/jack/mentions
BaseWeb data$0.01/ request
2026-10-11
https://readx.sh/api/:name/pinned
Just the user's pinned tweet, if any. Example: GET /api/jack/pinned
BaseWeb data$0.01/ request
2026-10-21
https://readx.sh/api/:name/profile
Full profile: bio, counts, banner, pinned tweet and a photo rail. Example: GET /api/jack/profile
BaseWeb data$0.01/ request
2026-11-18
https://readx.sh/api/:name/tweets/:id
A single tweet with its full conversation: tweets before, after and replies. Example: GET /api/jack/tweets/20
BaseWeb data$0.01/ request
2026-11-18
https://readx.sh/api/:name/with_replies
A user's timeline including their replies. Example: GET /api/jack/with_replies
BaseOther$0.01/ request
2026-10-28
https://readx.sh/api/articles/:id
An X article (long-form post) by its wrapper tweet id (public). Example: GET /api/articles/1
BaseWeb data$0.01/ request
2026-11-03
https://readx.sh/api/communities/:id
A Community's metadata: name, description, member/moderator counts, rules, topic, admin and creator. Example: GET /api/communities/1493446837214187523
BaseWeb data$0.01/ request
2026-09-28
https://readx.sh/api/lists/:id
Public X/Twitter data as read-only JSON: profiles, timelines, single tweets and conversations, search, hashtags, lists, followers and following. Paid per single call via x402, $0.01 in USDC on Base or Solana, with no AP…
BaseWeb data$0.01/ request
2026-07-23
https://readx.sh/api/lists/:id/timeline
Public X/Twitter data as read-only JSON: profiles, timelines, single tweets and conversations, search, hashtags, lists, followers and following. Paid per single call via x402, $0.01 in USDC on Base or Solana, with no AP…
BaseWeb data$0.01/ request
2026-07-23
https://readx.sh/api/search
Search tweets. Start the query with @ (or add f:user) to search users instead. Example: GET /api/search?q=typescript
BaseWeb data$0.01/ request
2026-10-10
https://readx.sh/api/search/tweets
Search for tweets by query (optional product filter; paginate with cursor). Example: GET /api/search/tweets?q=typescript
BaseWeb data$0.01/ request
2026-11-20
https://readx.sh/api/tools/get_user_id
Resolve an @handle to its numeric user id. Example: GET /api/tools/get_user_id?username=jack
BaseOther$0.01/ request
2026-11-18
https://readx.sh/api/tools/get_username
Resolve a numeric user id to its current @username. Example: GET /api/tools/get_username?user_id=12
BaseIdentity$0.01/ request
2026-11-20
https://readx.sh/api/trends
Trending topics for a location (worldwide by default; filter with country or woeid). Example: GET /api/trends?country=US
BaseWeb data$0.01/ request
2026-11-18
https://readx.sh/api/tweets/:id
A single tweet on its own, without the surrounding conversation. Example: GET /api/tweets/20
BaseWeb data$0.01/ request
2026-11-13
https://readx.sh/api/tweets/:id/replies
Replies to a tweet (paginate with cursor until has_more is false). Example: GET /api/tweets/20/replies
BaseWeb data$0.01/ request
2026-11-18
https://readx.sh/api/tools/get_tweets
Up to 100 tweets by id in one call (requested order; missing ids listed in not_found). Example: GET /api/tools/get_tweets?tweet_ids=20,1
BaseWeb data$0.05/ request
2026-11-13
https://readx.sh/api/tools/get_users
Up to 100 user profiles by numeric id in one call (requested order; suspended ids in unavailable, missing ids in not_found). Example: GET /api/tools/get_users?user_ids=12,44196397
BaseOther$0.05/ request
2026-11-13
Evidence
Answers HTTP 402
Answers HTTP 402Method: one unpaid request per listed endpoint. A 402 with a payment payload a client could parse counts. Nothing is paid.3 of 3
3 of 3 probed endpoints answered HTTP 402 with a parseable payment payload
checked 2026-10-27
x402-style payments, 7-day window (Base)
x402-style paymentsMethod: counted when the transaction carries a signed USDC authorization (EIP-3009), the settlement x402's exact scheme uses. Some non-x402 gasless sends use it too.unknown
unknown. the 7-day payments read on Base did not complete (time budget spent at block 58811722 (574000 of 3024001 blocks read))
window ended 2026-11-19
By chain
| Chain | Seller wallet | Endpoints | Answers 402 | x402-style payments |
|---|---|---|---|---|
| Base | 0x13e060adcc6f4b731da8382b333027b8b2bff707 | 18 | 3 of 3 probed endpoints answered HTTP 402 with a parseable payment payload 2026-10-27 | unknown. the 7-day payments read on Base did not complete (time budget spent at block 58811722 (574000 of 3024001 blocks read)) |
One seller wallet, each chain read on its own. We never send a payment, so we never observe what a paid call returns. Unknown means we hold no reading, not that anything failed.
Pricing
The price each endpoint registered in the x402 catalogue. A listed price is a registration, not an observed charge.
Claim this merchant
Sign a message from the payout address 0x13e060…bff707 to claim this page or download its payment ledger. Claiming proves control of the payout key. It says nothing about the service behind the address, and it does not change how this merchant is ranked. No email, no account: the signature is the whole credential, and signing a message costs no gas and moves nothing.
Data CC-BY-4.0, attribution: data by satohub.ai. Data: x402-list.com (CC BY 4.0). Data as of 2026-11-20. Appearing here is not an endorsement. Check an endpoint with the doctor.