# ReadX A2A Task Invocation

> ReadX A2A Task Invocation is a paid API for AI agents from readx.sh, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Sends a skill ID and input payload to the ReadX A2A endpoint and returns a completed Task with the result, enabling agent-to-agent invocation of ReadX capabilities.

## Facts

- Endpoint: POST https://readx.sh/api/a2a/v1/message:send
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/readx-a2a-task-invocation-d209f0d5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yhZ04DQ7rBnJvqNkEoUQ9

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-a2a-task-invocation-d209f0d5 -d '<json body>'
```

Example prompt: Use the ReadX A2A endpoint to invoke a skill — send a POST with type 'http' and method 'POST' to retrieve results from a ReadX capability, like fetching a user's timeline or tweet data.

## When to prefer this

Use this endpoint when you need to invoke any ReadX capability through an agent-to-agent (A2A) protocol — especially when orchestrating AI agents that need to retrieve X/Twitter data (profiles, timelines, tweets, search results) programmatically. Prefer this over direct REST calls when you are operating within an A2A task-dispatch framework or when integrating ReadX into a multi-agent pipeline.

## Known failure modes

- Missing required 'input' field returns a validation error
- Invalid or unsupported HTTP method (not POST) in input object causes rejection
- Unknown or malformed skill ID results in a not-found or bad-request error
- Insufficient payment or missing x402 payment header results in 402 Payment Required
- Malformed pathParams or queryParams may cause downstream skill execution failure
- Rate limiting or quota exceeded returns a 429 Too Many Requests response

## How this service works

A2A task invocation — send a skill id + input, get back a completed Task with the result. Example: GET /api/a2a/v1/message:send

## Output

A completed A2A Task object containing the result of the invoked ReadX skill — structured JSON data such as tweets, profiles, search results, or other X/Twitter content depending on the skill called.

## 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": [
      "POST"
     ],
     "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-a2a-task-invocation-d209f0d5/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)