# x.1x402.sh — X (Twitter) JSON API

> A clean, read-only JSON mirror of X/Twitter — profiles, timelines, tweets, search and lists. No API keys and no signup: each call is paid with an [x402](https://x402.org) micropayment (default $0.005 in USDC on Base). An x402-capable agent pays per request straight from its own wallet.

## How to use it

- Every endpoint is a `GET` under `https://x.1x402.sh/api/`.
- A request with no payment returns HTTP `402` with a `PAYMENT-REQUIRED` header describing the price and recipient; an x402 client pays and retries automatically.
- Most responses are `{ "code": 0, "data": ... }` on success and `{ "code": -1, "error", "error_type" }` on error. The List endpoints return the bare object.
- Paginate by passing a response's `pagination.bottom` (or `replies.bottom`) cursor back as `?cursor=`. Append `?no-cache` to force fresh data.

## Machine-readable contracts

- [OpenAPI 3.1 spec](https://x.1x402.sh/openapi.json): the canonical, full description of every endpoint, schema, and price (`x-payment-info`).
- [Agent skill](https://x.1x402.sh/skill.md): a drop-in skill file. Point an x402-capable agent at it and it learns every endpoint and the payment flow.

## Quick start

- Set up as a skill: `Set up https://x.1x402.sh/skill.md with x402`
- One call with an x402 client: `npx agentcash fetch https://x.1x402.sh/api/jack/profile`

## Key endpoints

- `GET /api/{name}/profile` — user object, photo rail, pinned tweet
- `GET /api/{name}` — user timeline (also `/with_replies`, `/media`)
- `GET /api/{name}/status/{id}` — a tweet and its conversation (or `/api/i/status/{id}` for just the tweet)
- `GET /api/{name}/status/{id}/history` — a tweet's edit history (latest plus prior versions)
- `GET /api/search?q=...` — tweet search (a leading `@` or `f:user` returns users)
- `GET /api/i/lists/{id}` — a List (also `/timeline`, `/members`)
- `GET /api/i/user/{id}` — resolve a numeric user id to a username