# WarpPay402 Feed Data Endpoint

> WarpPay402 Feed Data Endpoint is a paid API for AI agents from api.warppay402.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-02).

Retrieves oracle report data for a specific feed ID from the WarpPay402 monetization network, payable via x402 micropayment protocol.

## Facts

- Endpoint: GET https://api.warppay402.com/api/v1/feeds/%7BfeedId%7D?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/warppay402-feed-data-endpoint-75507ba0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MvA0L0I9E4VETUCzWgO6G

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 warppay402-feed-data-endpoint-75507ba0
```

Example prompt: Fetch the latest oracle report from WarpPay402 for feed ID 'btc-usd-price' and show me what data it returns.

## When to prefer this

Choose this endpoint when you need to consume a specific x402-monetized oracle data feed from the WarpPay402 network and you have a known feedId. It is best suited for AI agents that support the x402 payment protocol and need lightweight, per-call data access without custodial account management.

## Known failure modes

- Invalid or non-existent feedId returns an error or empty report
- Payment not included or insufficient — x402 payment required for access
- Malformed feedId path parameter causes a 400 or routing error
- Feed temporarily unavailable returns a non-success status
- Network or server error returns a 500 response

## How this service works

Non-Custodial x402 Monetization Server & MCP Tools for AI Agents.

## Output

Returns a JSON object containing the oracle name ('WarpPay402 Network'), a status field (e.g. 'success'), and a report object with the feed-specific data payload. The exact structure of the report object depends on the feed being queried.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "feedId"
 ],
 "properties": {
  "feedId": {
   "type": "string",
   "description": "Feed report ID"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "oracle": "WarpPay402 Network",
  "report": {},
  "status": "success"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/warppay402-feed-data-endpoint-75507ba0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.warppay402.com](https://www.zero.xyz/host/api.warppay402.com/llms.txt)