# ReadX Article Entities Endpoint

> ReadX Article Entities Endpoint is a paid API for AI agents from readx.1x402.sh, paid per call via x402, $0.03/call, status down (last checked 2026-09-15).

Retrieves named entities extracted from a specific article by article ID from the X/Twitter platform via the ReadX API

## Facts

- Endpoint: GET https://readx.1x402.sh/api/article-entities/%7Barticle_id%7D
- Price: $0.03/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/readx-article-entities-endpoint-c8e4f7cd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VLPfuP_hxrTH8_TpGzs8r

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability readx-article-entities-endpoint-c8e4f7cd
```

Example prompt: Can you pull all the named entities — people, organizations, topics — mentioned in the X/Twitter article with ID 1234567890 using ReadX?

## When to prefer this

Use this endpoint when you need structured entity data (people, organizations, locations, topics) extracted from a specific X/Twitter article and want to avoid managing API keys, paying a flat subscription, or dealing with X's own API access restrictions. Best when you already have an article_id and need quick entity enrichment via pay-per-call micropayments.

## Known failure modes

- Invalid or malformed article_id returns an error response
- Article not found returns empty data or non-zero code
- Payment failure via x402 micropayment (insufficient USDC balance) blocks the request
- Rate limiting or network timeout from upstream X/Twitter data source
- Article may not have extractable entities, returning empty data object

## How this service works

ReadX is a read-only X/Twitter JSON API. Profiles, timelines, tweets, search, lists, followers & following — pay per call with x402 micropayments in USDC on Base or Solana. No API keys.

## Output

A JSON object with a code field and a data object containing named entities extracted from the specified X/Twitter article, such as people, organizations, locations, and topics referenced within it.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "code": 0,
  "data": {}
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/readx-article-entities-endpoint-c8e4f7cd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from readx.1x402.sh](https://www.zero.xyz/host/readx.1x402.sh/llms.txt)