# ylk.one x402 Spike Detector

> ylk.one x402 Spike Detector is a paid API for AI agents from ylk.one, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-17).

Returns live x402 settlement rail spike data: current $/hr and tx/hr vs 24h baseline, last completed hour summary, and every ≥2.5× activity spike in the past 24 hours with named driver

## Facts

- Endpoint: GET https://ylk.one/v1/spikes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ylk-one-x402-spike-detector-05399eca
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__PP3yTEoVgpghr3W1B67i

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 ylk-one-x402-spike-detector-05399eca
```

Example prompt: Show me any x402 payment rail spikes from the last 24 hours — I want to see which hours hit 2.5× or more above baseline and what drove each spike, plus the current $/hr rate right now.

## When to prefer this

Use this endpoint when you need to detect and understand anomalous x402 payment rail activity derived from actual on-chain settlement data. Prefer this over the snapshot (/v1 live) or day-over-day (/v1/delta) endpoints when your goal is specifically to identify spike events, understand their magnitude relative to baseline, and get named drivers. It is the first step in the recommended habit SKU path before upgrading to /v1/vet or /v1/x402/brief for deep-dives on hot payTo addresses.

## Known failure modes

- No spike data available if the rail has been quiet (returns empty spike list)
- Payment required error if USDC microtransaction not included
- Stale data if on-chain settlement indexing lags
- Rate limiting if called too frequently

## How this service works

Settlement-derived x402 market tape: live $/hr and tx/hr vs 24h baseline, last completed hour, every ≥2.5× spike hour in the past 24h with named driver. Habit SKU after vet — upgrade path to /v1/vet then /v1/x402/brief for any hot payTo. Not self-reported.

## Output

A JSON tape of the live x402 settlement rail including: current $/hr and tx/hr versus 24h baseline, a summary of the last completed hour, and a list of every hour in the past 24h where activity hit ≥2.5× the baseline with a named driver explaining the cause. Data is settlement-derived, not self-reported.

## 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"
    },
    "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/ylk-one-x402-spike-detector-05399eca/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from ylk.one](https://www.zero.xyz/host/ylk.one/llms.txt)