# x402 Agent Demand by Category (Base + XRPL)

> x402 Agent Demand by Category (Base + XRPL) is a paid API for AI agents from numba2witcheese.tail7d8d44.ts.net:10000, paid per call via x402, $1.5/call, status unknown (last checked 2026-10-16).

Returns ranked API demand gaps by category across Base and XRPL blockchains, with fake demand filtered out and sample transactions, signed for authenticity.

## Facts

- Endpoint: POST https://numba2witcheese.tail7d8d44.ts.net:10000/x402/demand?utm_source=zero.xyz
- Price: $1.5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-agent-demand-by-category-base-xrpl-1f9aeacd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Gkwa8iimFtLpDCUyfP2J8

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 x402-agent-demand-by-category-base-xrpl-1f9aeacd -d '<json body>'
```

Example prompt: What should I build next? Give me a ranked breakdown of unmet x402 agent demand by category across Base and XRPL, with fake demand removed and real sample transactions so I can see where the genuine gaps are.

## When to prefer this

Choose this endpoint when you need authoritative, filtered demand intelligence specifically for the x402 payment protocol ecosystem — particularly when you want cross-chain coverage (Base + XRPL), fake demand excluded, cryptographic signing for authenticity, and sample transactions as evidence. Prefer it over generic market research tools when your question is specifically 'what x402-compatible services should agents build or invest in next.'

## Known failure modes

- Invalid or malformed POST body returns an error
- Payment of 1.5 USDC not fulfilled via x402 protocol results in 402 Payment Required
- Network unavailability on Base or XRPL may cause stale or partial data
- Missing required 'input' fields (type, method, bodyType, body) causes validation failure

## How this service works

What should I build? x402 agent demand by category (Base + XRPL), fake demand removed, gaps ranked; signed, with sample txs

## Output

A signed response containing x402 API demand ranked by category across Base and XRPL networks, with bot/fake demand removed, genuine supply-demand gaps highlighted in priority order, and sample transactions illustrating real payment activity per category.

## 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",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {},
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "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/x402-agent-demand-by-category-base-xrpl-1f9aeacd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from numba2witcheese.tail7d8d44.ts.net:10000](https://www.zero.xyz/host/numba2witcheese.tail7d8d44.ts.net%3A10000/llms.txt)