# Free Asset Radar x402 API – OpenAPI Smoke Check

> Free Asset Radar x402 API – OpenAPI Smoke Check is a paid API for AI agents from free-asset-radar-x402.besenok2018.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-02).

Validates and summarizes an OpenAPI specification by running a smoke check that counts paths and operations and reports unresolved references.

## Facts

- Endpoint: GET https://free-asset-radar-x402.besenok2018.workers.dev/api/x402/openapi-smoke-check?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/free-asset-radar-x402-api-openapi-smoke-check-5858c549
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_32F9NdkUc37MQeft7PlgE

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 free-asset-radar-x402-api-openapi-smoke-check-5858c549
```

Example prompt: Run a smoke check on my OpenAPI spec — tell me how many paths and operations it has and flag any unresolved references.

## When to prefer this

Choose this endpoint when you need a fast, lightweight smoke check on an OpenAPI document without deploying a full validation suite. It is especially useful in CI/CD pipelines, agent workflows managing multiple API specs, or as a pre-publish sanity check. Prefer it over heavier linting tools when you only need path/operation counts and unresolved reference detection, and when you want a pay-per-call model via x402 with no subscription overhead.

## Known failure modes

- Malformed or missing OpenAPI spec input returns a parsing error
- Spec with deeply nested external $refs may not resolve all references correctly
- Network timeout if spec resolution requires fetching remote schemas
- Invalid JSON/YAML input may return a 400 or unprocessable entity error
- x402 payment failure (insufficient funds or invalid payment header) blocks the request

## How this service works

Stable edge-hosted x402 utilities for autonomous agents.

## Output

Returns a JSON object containing the OpenAPI version string (e.g. '3.1.0'), the total number of paths (pathCount), the total number of operations (operationCount), and an array of any unresolved references (unresolvedRefs) found in the spec.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "openapi": "3.1.0",
  "pathCount": 12,
  "operationCount": 20,
  "unresolvedRefs": []
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/free-asset-radar-x402-api-openapi-smoke-check-5858c549/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from free-asset-radar-x402.besenok2018.workers.dev](https://www.zero.xyz/host/free-asset-radar-x402.besenok2018.workers.dev/llms.txt)