# NAKONETS Service Proof / Health Check

> NAKONETS Service Proof / Health Check is a paid API for AI agents from x402vercel.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-02).

Returns a proof-of-service response confirming the NAKONETS x402 payment gateway is live on the Base network.

## Facts

- Endpoint: GET https://x402vercel.vercel.app/api/service-proof?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/nakonets-service-proof-health-check-f1b70d1e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MKxVD8HwOvWKrB8CnMlzJ

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 nakonets-service-proof-health-check-f1b70d1e
```

Example prompt: Can you ping the NAKONETS x402 service proof endpoint and confirm it's live on the Base network before I kick off my pipeline?

## When to prefer this

Use this endpoint as a lightweight preflight or health check before invoking costlier NAKONETS utility calls. It is ideal for CI pipelines, monitoring scripts, or any workflow that needs to confirm the x402 payment gateway and Base network connectivity are operational before committing to paid calls. It is not a substitute for full functional testing of individual utility endpoints.

## Known failure modes

- Non-200 HTTP status if the Vercel deployment is down or cold-starting
- Payment required (402) if the x402 header is missing or the USDC micropayment of $0.01 was not processed
- Malformed JSON response if the upstream service is in an error state
- Network mismatch in the response if the service is misconfigured for a different chain

## How this service works

Pay-per-call deterministic utilities for CI diagnosis, data validation, JavaScript syntax checks, market snapshots and opportunity preflight.

## Output

A JSON object with three fields: `ok` (boolean true if the service is healthy), `network` (the EIP-155 chain identifier, e.g. 'eip155:8453' for Base), and `service` (a string confirming the service name 'NAKONETS x402 service proof'). On success this confirms the endpoint is live and payment-ready.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "network": "eip155:8453",
  "service": "NAKONETS x402 service proof"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/nakonets-service-proof-health-check-f1b70d1e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402vercel.vercel.app](https://www.zero.xyz/host/x402vercel.vercel.app/llms.txt)