# ShadowQuant Intelligence API – Lead-Lag Study

> ShadowQuant Intelligence API – Lead-Lag Study is a paid API for AI agents from sq-intel-x402.aries-lao.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-19).

Returns validated lead-lag relationship analysis between equities and/or options instruments for AI-driven market research

## Facts

- Endpoint: GET https://sq-intel-x402.aries-lao.workers.dev/lead-lag?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/shadowquant-intelligence-api-lead-lag-study-4dbdf02f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jo6HvqjQqw1Zaf37LrxPB

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 shadowquant-intelligence-api-lead-lag-study-4dbdf02f
```

Example prompt: Pull the lead-lag relationship study between SPY and QQQ from ShadowQuant — I want to know which one tends to move first and how stale the data is.

## When to prefer this

Choose this endpoint when an AI agent needs quantified, validated lead-lag relationship data between equities or options instruments, backed by provenance and methodology metadata. Prefer it over generic financial data APIs when you need the specific directional timing relationship (which asset moves first) rather than raw price data, fundamentals, or news. The per-call micropayment model via x402/USDC makes it practical for on-demand agent workflows without subscription overhead.

## Known failure modes

- Payment not included or insufficient — 402 Payment Required response
- Invalid or unrecognized ticker/symbol — 400 Bad Request or empty data payload
- Study not yet generated for requested pair — data field may be null or absent
- Stale data flag set true when age_hours exceeds freshness threshold
- Network or worker-side timeout on Cloudflare Workers edge — 503 or timeout error

## How this service works

Validated equities/options market research for AI agents, paid per-call via x402 (USDC on Base). Research data, not investment advice.

## Output

A JSON envelope containing: a `data` field with the lead-lag study payload (quantified relationship between instruments), a `provenance` block (producer, methodology, generated_at, freshness with age_hours and stale flag, track record), a disclaimer, and terms of use. Research data only, not investment advice.

## Response schema (JSON Schema)

```json
{
 "description": "JSON envelope: { data: <study payload>, provenance: { producer, methodology, generated_at, freshness: { age_hours, stale }, track_record }, disclaimer, terms }"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/shadowquant-intelligence-api-lead-lag-study-4dbdf02f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from sq-intel-x402.aries-lao.workers.dev](https://www.zero.xyz/host/sq-intel-x402.aries-lao.workers.dev/llms.txt)