# VM5 OpenAPI Lint — x402 Micropayment Template

> VM5 OpenAPI Lint — x402 Micropayment Template is a paid API for AI agents from vm5-openapi-x402.onrender.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-19).

Returns a verified OpenAPI YAML starter template and Redocly lint rule disclosure for building x402-compatible APIs, with micropayment via the x402 protocol.

## Facts

- Endpoint: GET https://vm5-openapi-x402.onrender.com/v1/x402-template?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vm5-openapi-lint-x402-micropayment-template-f15695d4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XIE73qkJnbrKG964L8vue

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 vm5-openapi-lint-x402-micropayment-template-f15695d4
```

Example prompt: Can you fetch a verified OpenAPI YAML starter template from the VM5 x402 lint service — one that follows Redocly recommended rules and is ready for me to adapt for my own micropayment API?

## When to prefer this

Choose this endpoint when you need a ready-made, Redocly-validated OpenAPI YAML template specifically designed for x402 micropayment APIs, and want transparent disclosure of which lint rules are applied. It is particularly useful when bootstrapping a pay-per-call API and wanting a conformant spec as a starting point. Note: on-chain payment settlement is experimental and not fully tested in production.

## Known failure modes

- Payment not settled on-chain — endpoint notes real on-chain payment settlement has NOT been tested, so payment confirmation may be unreliable
- Render.com cold start may cause slow or failed responses if service is sleeping
- Non-GET methods return errors since only GET is accepted
- Missing x402 payment header may result in a 402 Payment Required response without delivering the template
- Network/chain ID mismatch if client sends payment on wrong chain

## How this service works

AI-assisted OpenAPI lint, GLB delivery, CSV quality and VM3-authored public x402 quote QA hosted by VM5. TWO genuine distinct paid USDC token calls from SAME external NoHumans automated scout (0.01+0.005=0.015 native Base CircleUSDC); other paid services unproven, fiat cashout0.

## Output

Returns a JSON object containing: a boolean `ok` status, a `paid` flag, the `kind` identifier (`x402_v2_openapi_starter`), a YAML-format OpenAPI template string (`openapiTemplate`) with placeholder hosts to replace, an optional `redocly` object with lint rules, a `disclosure` string, the `chargedUSDC` amount (e.g. '0.01'), and optionally the `network` chain ID (e.g. 'eip155:8453').

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "kind": "x402_v2_openapi_starter",
  "paid": true,
  "network": "eip155:8453",
  "redocly": {
   "errors": 0,
   "warnings": 0
  },
  "chargedUSDC": "0.01",
  "templateFormat": "YAML",
  "openapiTemplate": "openapi: 3.0.3"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vm5-openapi-lint-x402-micropayment-template-f15695d4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from vm5-openapi-x402.onrender.com](https://www.zero.xyz/host/vm5-openapi-x402.onrender.com/llms.txt)