# CRYPTYX Health & Version Probe

> CRYPTYX Health & Version Probe is a paid API for AI agents from www.cryptyx.ai, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Returns CRYPTYX service build identifier, latest pipeline run timestamp, and current operational counts (active signals, composites, asset universe size) as a low-cost liveness check.

## Facts

- Endpoint: GET https://www.cryptyx.ai/api/x402/health
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cryptyx-health-version-probe-9f59d3bc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mTSr53T02bEfPVQmcWyH2

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 cryptyx-health-version-probe-9f59d3bc
```

Example prompt: Can you do a quick CRYPTYX health ping to confirm the service is live, my payment integration is wired correctly, and tell me the current build version, last pipeline run time, and how many active signals and assets are in the universe?

## When to prefer this

Use this endpoint as a cheap preflight check ($0.01 USDC) before issuing more expensive CRYPTYX analytics queries. Ideal for confirming end-to-end x402 payment integration, verifying service liveness, checking current build version, and getting a snapshot of operational counts without triggering any database writes.

## Known failure modes

- Service unavailable (5xx) if CRYPTYX backend is down
- Payment authentication failure if x402 USDC payment is not correctly wired
- Network timeout if endpoint is unreachable
- Malformed response if service is degraded but partially running

## How this service works

CRYPTYX service health + version probe. Returns build identifier, latest pipeline run timestamp, and current operational counts (active signals, composites, asset universe size). Sub-second response, no DB writes. Use as a low-cost agent ping to confirm pay-per-call is wired correctly end-to-end and the service is live before issuing more expensive queries.

## Output

A sub-second JSON response containing the CRYPTYX build identifier, timestamp of the latest pipeline run, and current operational counts including active signals, composites, and asset universe size. No database writes occur.

## 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"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "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/cryptyx-health-version-probe-9f59d3bc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.cryptyx.ai](https://www.zero.xyz/host/www.cryptyx.ai/llms.txt)