# Bot Bazaar CORS Header Linter for x402 Payments

> Bot Bazaar CORS Header Linter for x402 Payments is a paid API for AI agents from bot-bazaar.fly.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-30).

Validates CORS response headers to confirm browser and agent x402 clients can send PAYMENT-SIGNATURE and read PAYMENT-REQUIRED / PAYMENT-RESPONSE headers

## Facts

- Endpoint: GET https://bot-bazaar.fly.dev/v1/x402/cors-header-check?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bot-bazaar-cors-header-linter-for-x402-payments-51814b61
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BmqxNvOZ1NUBkQdF_zq8U

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 bot-bazaar-cors-header-linter-for-x402-payments-51814b61
```

Example prompt: Can you lint the CORS headers on my x402 endpoint using a GET method and check whether the Access-Control-Expose-Headers includes PAYMENT-REQUIRED and PAYMENT-RESPONSE so browser agents can read them?

## When to prefer this

Choose this endpoint when you need to verify that an x402-enabled HTTP API correctly exposes and allows payment-related CORS headers before deploying or debugging cross-origin agent/browser payment flows. It is specifically tailored to x402 protocol header requirements (PAYMENT-SIGNATURE, PAYMENT-REQUIRED, PAYMENT-RESPONSE) rather than generic CORS testing tools, making it ideal for developers building or integrating x402 payment servers.

## Known failure modes

- Missing required 'input' object in request body returns validation error
- Unsupported HTTP method (e.g. POST, PUT) returns schema error since only GET, HEAD, DELETE are allowed
- Malformed expose_headers query param may produce incomplete lint results
- Server unreachable or timeout returns connection error
- Ambiguous or incomplete CORS configuration may yield inconclusive lint output

## How this service works

Lint CORS response headers to ensure browser/agent x402 clients can send PAYMENT-SIGNATURE and read PAYMENT-REQUIRED / PAYMENT-RESPONSE.

## Output

Returns a structured lint report indicating whether the CORS headers are correctly configured for x402 payment flows, identifying missing or misconfigured headers such as Access-Control-Expose-Headers, Access-Control-Allow-Headers, and specific x402 payment header entries (PAYMENT-SIGNATURE, PAYMENT-REQUIRED, PAYMENT-RESPONSE).

## 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": {
      "expose_headers": {
       "type": "string",
       "description": "Access-Control-Expose-Headers value"
      }
     }
    }
   },
   "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/bot-bazaar-cors-header-linter-for-x402-payments-51814b61/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from bot-bazaar.fly.dev](https://www.zero.xyz/host/bot-bazaar.fly.dev/llms.txt)