# three.ws Market Fees Lookup

> three.ws Market Fees Lookup is a paid API for AI agents from three.ws, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-15).

Returns 24-hour and 30-day fee or revenue totals for the three.ws AI agent marketplace, broken down by payment protocol.

## Facts

- Endpoint: GET https://three.ws/api/x402/market-fees?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/three-ws-market-fees-lookup-7b28f20b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0jziJlOfnl6HGFIT9OMKs

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 three-ws-market-fees-lookup-7b28f20b
```

Example prompt: What are the total marketplace fees collected on three.ws in the last 24 hours, broken down by payment protocol — show me fees mode?

## When to prefer this

Use this endpoint when you specifically need marketplace-level fee or revenue analytics for the three.ws 3D AI agent platform, broken down by payment protocol (e.g. Tether). Prefer it over generic analytics APIs when the goal is monitoring micropayment volume or protocol economics within the three.ws x402 ecosystem.

## Known failure modes

- Invalid 'type' query param value returns unexpected/default behavior
- Missing required 'method' or 'type' fields in input schema causes validation error
- Payment of $0.001 USDC required per call via x402 — missing payment returns 402 response
- Stale or unavailable fee data may result in partial protocol breakdowns
- Network timeout if three.ws backend is unavailable

## How this service works

Make a 3D AI agent from a selfie in 60 seconds. Drop one HTML tag to embed it on any website. Agents think on IBM watsonx.ai (Granite); optionally charge per chat with built-in micropayments.

## Output

Returns a JSON object with the query type ('fees' or 'revenue'), a total24h integer (in smallest units, e.g. millionths of USDC), and an array of protocols each with name, slug, total24h, and total30d values.

## 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",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "type": {
       "type": "string",
       "description": "'fees' (default — what users pay) or 'revenue' (what the protocol keeps)."
      }
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "type": "fees",
  "total24h": 61000000,
  "protocols": [
   {
    "name": "Tether",
    "slug": "tether",
    "total24h": 18400000,
    "total30d": 512000000
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/three-ws-market-fees-lookup-7b28f20b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from three.ws](https://www.zero.xyz/host/three.ws/llms.txt)