# VM5 OpenAPI Lint x402 Ping

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

Health/connectivity ping endpoint for the VM5 OpenAPI linting and quality-check service, gated by x402 micropayment in USDC on Base

## Facts

- Endpoint: GET https://vm5-openapi-x402.onrender.com/v1/ping?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vm5-openapi-lint-x402-ping-4cff334d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mpOGJ3DI3fH7hpFOBWxkf

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-ping-4cff334d
```

Example prompt: Can you ping the VM5 OpenAPI lint service to confirm it is live and that my x402 USDC micropayment on Base goes through correctly?

## When to prefer this

Use this endpoint when you need to verify that x402 micropayment-gated API access is functional end-to-end on the Base network before committing to heavier operations like OpenAPI linting or CSV auditing. Prefer it over a free health check when you specifically need to confirm the full payment flow — from USDC deduction through middleware to service response — is working correctly.

## Known failure modes

- Insufficient USDC balance — payment rejected before reaching service
- x402 middleware failure — payment deducted but service does not respond
- Network unavailability — Render host down, returns 503 or timeout
- Invalid or missing x402 payment header — returns 402 Payment Required
- Base network congestion causing payment processing delays

## 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 confirming the service is reachable, that a real x402 USDC payment of 0.001 was charged on the Base network (eip155:8453), and that the service responded successfully after the payment middleware processed the transaction. Fields include: ok (boolean), kind ('x402_paid_integration_ping'), paid (boolean), network, chargedUSDC, thirdPartyFinalityProof, and serviceResponseAfterPaymentMiddleware.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "kind": "x402_paid_integration_ping",
  "paid": true,
  "network": "eip155:8453",
  "chargedUSDC": "0.001",
  "thirdPartyFinalityProof": false,
  "serviceResponseAfterPaymentMiddleware": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vm5-openapi-lint-x402-ping-4cff334d/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)