# ReadX Community Metadata Lookup

> ReadX Community Metadata Lookup is a paid API for AI agents from readx.sh, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-10).

Fetches metadata for an X/Twitter Community by ID, including name, description, member/moderator counts, rules, topic, admin, and creator.

## Facts

- Endpoint: GET https://readx.sh/api/communities/:id?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/readx-community-metadata-lookup-cc738aeb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_u2L1BUp7NYb7wg6ybcZxe

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-community-metadata-lookup-cc738aeb
```

Example prompt: Can you pull up the metadata for X community 1493446837214187523 — I want to see its name, description, member count, rules, and who created it?

## When to prefer this

Use this endpoint when you need structured metadata about a specific X/Twitter community and have its numeric community ID. It is ideal for agents that need to display, audit, or store community profile information without scraping the web. Prefer this over general web search when you need reliable, structured JSON data about community attributes like member counts and rules.

## Known failure modes

- Invalid or non-existent community ID returns a 404 or error response
- Private or restricted communities may return incomplete metadata
- Payment failure (x402) results in a 402 response and no data returned
- Malformed community ID (non-numeric or wrong format) may return a validation error

## How this service works

A Community's metadata: name, description, member/moderator counts, rules, topic, admin and creator. Example: GET /api/communities/1493446837214187523

## Output

Returns a JSON object containing the community's name, description, member count, moderator count, rules, topic, admin details, and creator information.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/readx-community-metadata-lookup-cc738aeb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from readx.sh](https://www.zero.xyz/host/readx.sh/llms.txt)