# ShadowQuant Intelligence API – Correlation Endpoint

> ShadowQuant Intelligence API – Correlation Endpoint 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-21).

Returns quantitative correlation analysis between equities and/or options symbols, with provenance metadata and freshness tracking, paid per-call via x402 USDC.

## Facts

- Endpoint: GET https://sq-intel-x402.aries-lao.workers.dev/correlation?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/shadowquant-intelligence-api-correlation-endpoint-fb018eb5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_smhHtqizRrTusbTeazHCf

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-correlation-endpoint-fb018eb5
```

Example prompt: What's the correlation between AAPL and MSFT right now? Use ShadowQuant's validated market research — I want to see the correlation coefficient, how fresh the data is, and the methodology behind it.

## When to prefer this

Choose this endpoint when you need a paid, validated, provenance-tracked quantitative correlation between two equity or options symbols, especially when data freshness guarantees and methodology transparency matter. Prefer over free alternatives when auditability (track record, methodology) is required or when integrating into an automated agent pipeline that bills per-research-call via crypto micropayments.

## Known failure modes

- Invalid or unrecognized ticker symbols return an error in the data envelope
- Payment failure via x402 (insufficient USDC balance or unsupported wallet) blocks the response
- Stale data flagged in freshness.stale field when age_hours exceeds threshold — data returned but marked stale
- Missing required query parameters result in a 4xx error
- Service unavailable on Cloudflare Workers edge returns 5xx

## 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 correlation study payload (coefficient and supporting statistics), a 'provenance' object with producer name, methodology description, generation timestamp, and freshness indicators (age in hours, staleness flag with track record), plus a disclaimer and terms of use.

## 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-correlation-endpoint-fb018eb5/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)