X user timeline

Fetch an X (Twitter) account's most recent tweets by user id or username (username is resolved first). Send POST /api/x-user-tweets with no required fields (7 optional) and pay $0.08 per call over x402 or MPP (there is no free tier). It returns a JSON object with source, fetchedAt, user, count, tweets and 1 more.

Options to exclude retweets and replies, page with pagination_token, or fetch only tweets newer than since_id. Each tweet carries text, created time, language and engagement metrics.

Category: Web & documents · Tags: x twitter social x-api tweets timeline user-tweets

TRY IN PLAYGROUND →

Parameters

Example request

curl -i -X POST https://agent402.tools/api/x-user-tweets \
  -H "Content-Type: application/json" \
  -d '{"username":"coinbase","max_results":10,"exclude_retweets":true,"exclude_replies":true}'

Without payment this returns HTTP 402 Payment Required with the exact price for x-user-tweets; any x402 v2 or MPP client pays it and retries.

Example response

{
  "source": "x-api-v2",
  "fetchedAt": "2026-08-20T14:10:00.000Z",
  "user": {
    "id": "574032254",
    "username": "coinbase",
    "name": "Coinbase",
    "verified": true
  },
  "count": 1,
  "tweets": [
    {
      "id": "20",
      "text": "just setting up my twttr",
      "createdAt": "2006-03-21T20:50:14.000Z",
      "lang": "en",
      "authorId": "574032254",
      "author": {
        "username": "coinbase",
        "name": "Coinbase",
        "verified": true
      },
      "conversationId": "20",
      "possiblySensitive": false,
      "metrics": {
        "likes": 180000,
        "retweets": 120000,
        "replies": 10000,
        "quotes": 30000,
        "bookmarks": 5000,
        "impressions": 0
      },
      "url": "https://x.com/coinbase/status/1800000000000000000"
    }
  ],
  "nextToken": "7140dibdnow9c7btw4xxxxx"
}

From an MCP client

catalog.call {
  "slug": "x-user-tweets",
  "params": {
    "username": "coinbase",
    "max_results": 10,
    "exclude_retweets": true,
    "exclude_replies": true
  }
}

The hosted connector at https://agent402.tools/mcp needs a payment for x-user-tweets; the stdio package pays it from a wallet or from AGENT402_CREDITS_KEY. Local install: npx -y agent402-mcp.

Errors and behavior

• Every field is optional. An input the tool rejects returns an HTTP 4xx whose body carries error, tool, expected, required and example.
• A paid call that ends in any status of 400 or above is not charged over x402, MPP or a prepaid credits key: settlement is cancelled when the tool fails. The exception is a Tempo push credential, a transfer the buyer sent before the call: it settles before the tool runs, so if the tool then fails the payment is recorded as a refund owed to the paying wallet.
• Wallet-only: this tool reaches the network or stored state, so it has no proof-of-work tier. A prepaid card-credits key issued earlier (Authorization: Bearer a402_...) also pays it.
• A GET or HEAD to /api/x-user-tweets returns the same 402 quote, so the price can be read without a body.
• An Idempotency-Key header makes a retried paid call replay the first 200 instead of charging again (an answer larger than 1 MB is not replayed).

Paid call (JavaScript agent)

import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

const client = new x402Client();
client.setSpendControls?.(false); // keep your own spending ceiling in code
registerExactEvmScheme(client, { signer: privateKeyToAccount(KEY) });
const payFetch = wrapFetchWithPayment(fetch, client);

const res = await payFetch("https://agent402.tools/api/x-user-tweets", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    "username": "coinbase",
    "max_results": 10,
    "exclude_retweets": true,
    "exclude_replies": true
  }),
});

Related tools