Services tagged “user-tweets”
Services that meet our listing criteria. Include everything we watch. The same metrics for each. Agents can run the same query at /api/v1/services.
| Our checks (unpaid requests) | Payment terms | Reported by the registry | Listing | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Service | Latest scheduled check | Last 30 checks, oldest to newest | Scheduled checks passed (7-day window) | Scheduled checks passed / run (30-day window) | Response time of latest check (ms) | Check schedule | Freshness | Monitoring since | Lowest price per call (US$) | Payment protocols offered | Payment networks | Payment-terms changes (90 days) | Registry: unique payers (30 days) | Registry: paid calls (30 days) | What it does (capability tree) | Type | Added from | Purpose tags | Provider | Endpoint we check |
| Twitter/X APItwitter.use.x402atlas.com | Live, payment required · HTTP 402 | 2 passed, 0 failed, 28 not run, of the last 30 checks | short history2 of 2 run | short history2 of 2 run · 0 missed · 2 days | 62 | daily | Fresh | 2026-10-16 | $0.005registry's terms | x402 | eip155:8453eip155:137+2 | 0since 2026-10-16 | 6 | 23 | Read posts and profiles | Paid API | A public registry | twitteruser-tweetstimeline+1 | x402atlas.com236 endpoints | GET twitter.use.x402atlas.com/user-tweets |
21 columns; scroll sideways for more. Each heading links to its definition in the field dictionary. Registry columns are the registry's own figures.