twitr.sh valid
twitr.sh
Pay-per-call X/Twitter API for AI agents. No signup — the wallet is the
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://twitr.sh/llms.txt
- llms-full.txt
- https://twitr.sh/llms-full.txt
- Sections
- 8
- Links
- 28
- Size
- 12539 bytes
- Country
- United States Hosting inference
- Hosting country
- United States Hosting inference
- Country evidence
- No published address evidence collected yet
- Categories
- AI and machine learning
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-27T13:27:55.678Z
- Last checked
- 2026-10-27T13:27:56.596Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T13:27:55.682Z. Cached copy · Source on twitr.sh
# twitr.sh
> Pay-per-call X/Twitter API for AI agents. No signup — the wallet is the
> account. Every call is paid in USDC via x402 (Base, Solana) or MPP (Tempo)
> through the HTTP 402 flow, or with an API key against a prepaid card balance.
## Per-result billing
Searches, timelines, list and community reads use x402 upto on Base. The 402 amount is a maximum authorization; payment.amount is the actual charge. Empty results cost $0; non-empty reads have a $0.0024 minimum at $0.0012 per record. Use current AgentCash for gasless approval. Other operations retain their advertised fixed/prepaid payment options.
For "this week", calculate Monday and state that date window. If empty, say no matching posts; any older timeline context must be labeled with its dates. Never silently change filters.
Run paid calls sequentially from one wallet; an overlapping call receives HTTP 429 before dispatch and costs zero. Wait for the other call, then retry with a fresh credential. Start research with 3–5 results to keep rich post data within context limits.
## How payment works
1. POST any tool endpoint without credentials → HTTP 402 with an x402
`PAYMENT-REQUIRED` header; fixed-price operations may also offer an MPP `WWW-Authenticate: Payment` header.
2. Authorize the maximum for per-result reads on Base; use an offered protocol for fixed-price operations.
3. Retry with the payment credential → data + settlement receipt.
4. Volume tools (search, timelines, lists, community reads) REQUIRE
`resultsLimit` (1–10000) and bill per returned item; the cap is enforced
so you never pay for more than requested. draws, x_extract + x_monitor
require an `Idempotency-Key` header. x_extract is async → poll
`GET /api/snapshots/{id}` (free, SIWX) for the dataset. x402 reads settle after success; prepaid operations may fail after payment.
## API key + card balance (optional)
Sign in at https://twitr.sh/dashboard (wallet or Google), add a card balance, create a key, and send
`Authorization: Bearer tw_live_…` on any tool call (HTTP or MCP). Same prices; per-result
reads charge only returned records; `payment.balance_remaining_usd` is in every response.
Short balance → 402 `payment-insufficient` (nothing charged); unknown/revoked key → 401.
## Tools (POST https://twitr.sh/api/tools/{tool})
- `x_read` — Read live X/Twitter data: look up a single tweet or user profile, batch-read up to 100 tweets or users at once, check whether one account follows another, fetch trending topics by region, extract a long-form article, or download tweet media. Pay per call in USDC — no API key, no signup; failed calls are never charged. ($0.002400–$1.200000 USD / call · docs: https://twitr.sh/tools/x_read)
- `x_search` — Search X/Twitter tweets with the full operator set — keyword, exact phrase, from-user, language, date range, media type, minimum likes/retweets, verified-only — or search user profiles by keyword. Billed per tweet returned against your resultsLimit cap. Built for tra
…Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| postory.io | Postory | interface Marketing | — | 45 | ✓ | ✓ | |
| twitterviewer.net | Twitter Viewer | interface AI and machine learning | — | 53 | ✓ | ||
| backtweets.com | backtweets | interface Community Marketing | — | 53 | ✓ | ||
| twitterapi.io | twitterapi.io | interface AI and machine learning APIs and SDKs +1 | US | 47 | ✓ | ✓ | |
| xanguard.tech | Xanguard — Real-Time Twitter/X Monitoring | documentation | US | 45 | ✓ | ✓ | |
| omar-thing.site | Omar-Thing | documentation Media | — | 55 | ✓ | ||
| hitools.pro | HiTools.Pro | documentation Marketing Design | — | 56 | ✓ | ✓ | |
| tweet-catcher.com | Tweet Catcher | interface Data and analytics | — | 50 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=twitr.sh · GET /v1/domain/twitr.sh · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage twitr.sh, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for twitr.sh:
1. POST https://agentwebmap.com/v1/sites/twitr.sh/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://twitr.sh/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/twitr.sh/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/twitr.sh).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.