# CoCo XRP Events Feed

> CoCo XRP Events Feed is a paid API for AI agents from cocoeatsai.com, paid per call via x402, $0.0135/call, status unknown (last checked 2026-10-19).

Retrieves a list of XRP-related events from Zach Riehn's Launch Lab research endpoint

## Facts

- Endpoint: GET https://cocoeatsai.com/area4/agent/xrp/events?utm_source=zero.xyz
- Price: $0.0135/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/coco-xrp-events-feed-b4178e9f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fSgYuIg_qf4GQSVew_3WP

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 coco-xrp-events-feed-b4178e9f
```

Example prompt: Can you pull the latest XRP events from the Launch Lab and show me what's coming up?

## When to prefer this

Choose this endpoint when you need a curated, researcher-maintained list of XRP-specific events from an independent lab perspective (Launch Lab by Zach Riehn), rather than scraping a generic crypto news aggregator or exchange API. Best used when you want low-cost, lightweight event discovery for XRP without needing a full exchange or analytics platform subscription.

## Known failure modes

- Payment required (402) if USDC payment is not attached to the request
- Empty events array if no events are currently available
- Malformed or incomplete response if the endpoint is under maintenance
- Network timeout if the server is slow or unavailable
- Invalid properties filter parameter causing a 400 error

## How this service works

Zach Riehn's lab: an about-me and portfolio, a news desk, The Atelier for AI experiments, Launch Lab for XRP research, and Fracture for games.

## Output

Returns a JSON object containing an array of XRP-related events, each with at minimum a title field, and potentially additional event metadata such as dates, descriptions, or categories.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "events": [
   {
    "title": "Example event"
   }
  ]
 },
 "exampleNote": "Illustrative response subset; not a live observation."
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/coco-xrp-events-feed-b4178e9f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from cocoeatsai.com](https://www.zero.xyz/host/cocoeatsai.com/llms.txt)