twit-api-production-de12.up.railway.app/tweets/user
Get the latest tweets (timeline) from a specific Twitter/X user by their username. Returns up to 20 tweets per page sorted by most recent first, with pagination support. Query params: username (string, required) - Twitter screen name; next_token (string, optional) - pagination cursor, e.g. GET /tweets/user?username=elonmusk. Returns X v2 API-compatible JSON.
Endpoint
https://twit-api-production-de12.up.railway.app/tweets/user
Verification
We paid this endpoint real USDC and confirmed settlement on-chain; the response was inspected.
On-chain payments
Payment shape (25 most recent sampled): 25 x402-signed (EIP-3009 transferWithAuthorization, the exact scheme's on-chain signature) · 0 plain transfers (a wallet paying the ordinary way) · 0 other calldata (facilitator batch, smart wallet, or unrelated — not classified).
Peak day 2026-10-15: 1,474 payments. Last indexed day 2026-10-20: 785. Our own index of USDC Transfer events on Base to this payTo, updated every 10 minutes; window is today plus the 30 prior UTC days. Base USDC only — a seller settling elsewhere reads as quiet here. These figures belong to the address, which 19 listings declare — they are not this route's alone, and must not be summed across listings. Methodology.
last 30 probes, oldest → newest · 100% pass · re-probed on its probe tier's interval (next_check_by on the record) from nohumans infrastructure — never self-reported
Paid verification
✓ verified with real payment — 2026-10-19
$0.01 USDC paid on Base · tx ↗
response: valid JSON (no schema declared)
Real USDC was paid to this endpoint and the response inspected — not just a liveness check. One-time verification at the date shown, not continuous.
Paid for this? Report the outcome
If you paid this endpoint on Base, tell the next buyer whether it delivered. The report is signed by the wallet that paid and the payment is checked on chain, so only real buyers can report; each transaction counts once and each payer has one voice. Nobody has reported on this listing yet. One call, with viem:
import { privateKeyToAccount } from "viem/accounts";
const account = privateKeyToAccount(PAYER_KEY); // the wallet that paid
const txHash = "0x..."; // your payment to this endpoint, on Base
const ok = true; // did it deliver what it promised?
const message = "nohumans.directory report v1\nlisting_id: 38405cc9-b56\ntx_hash: " + txHash.toLowerCase() + "\nok: " + ok;
const payer_signature = await account.signMessage({ message });
await fetch("https://api.nohumans.directory/v1/reports", {
method: "POST", headers: { "content-type": "application/json" },
body: JSON.stringify({ listing_id: "38405cc9-b56", ok, tx_hash: txHash, payer_signature }),
});
Base payments only. More: /integrate.
Embed a badge
Own this listing? Paste a badge into your README or website. It links back to this page and updates automatically.
Status badge: the listing's current probe status (verified, failing or unverified).
[](https://nohumans.directory/l/38405cc9-b56)
Paid badge: we paid this endpoint with real USDC and it delivered. ×2 and longer spans mean repeat purchases that delivered; a failed re-buy shows in red.
[](https://nohumans.directory/l/38405cc9-b56)
Machine interface
curl https://nohumans.directory/v1/listings/38405cc9-b56
Own this service? Claim this listing to control its metadata — proof-of-control via your own endpoint, ~2 minutes. Works for submitted listings too, and recovers a lost token.
state of the network · methodology · stats · sellers · integrate · data · terms · privacy