Kairos Signal — verifiable DePIN data API

Correlation spectrum vs Marchenko-Pastur for one network (paid)

get_rmt_regime_state

Destructive

Paid: 1 credit ($1.00) per answered call, charged once and only after a non-empty answer is computed; an unavailable answer, a refusal or an error costs nothing. Send your API key in the X-API-Key header or as api_key. Each call is a new answer and a new charge (no idempotency key). For one DePIN network: the correlation matrix of the daily log changes of its stored first-party metrics over the last days complete UTC days (one publisher per metric; exact combinations of other metrics, e.g. writer-derived ratios, excluded and named; effective rank and near-identical pairs reported), its eigenvalues, and the Marchenko-Pastur edges for the same number of independent series (q = N / (T-1)). Reports the largest eigenvalue over the upper edge, how many eigenvalues exceed it, the absorption ratio (variance share of the top ceil(N/5) eigenvalues) and each metric's loading on the top eigenvector. The edge is a reference for independent light-tailed series; telemetry changes are neither, so exceeding it describes co-movement and is not a test. Uses up to max_metrics (3-60, default 30) metrics, by name order. Every input daily close is returned with its as_of and verify_url. No regime label, position size or trading mode is produced.

Input Schema

Name	Required	Description
`days`	No	Daily changes in the window (default 30), ending at the latest complete UTC day.
`symbol`	Yes	One network ticker, e.g. AKT, FIL, RENDER.
`api_key`	No	Your API key, only if your client cannot send the X-API-Key header.
`max_metrics`	No	Metrics used (default 30).
`metric_filter`	No	Optional case-insensitive substring of metric names, e.g. GPU.

Output Schema

Name	Required	Description	Default
`tool`	No
`result`	Yes
`schema`	Yes
`status`	Yes
`symbol`	Yes
`call_id`	No
`credit_cost`	Yes
`charge_state`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026
RemovedOct 23, 2026
AddedOct 22, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Exceptional disclosure beyond the annotations: exact price (1 credit / $1.00), the charge condition (only after a non-empty answer is computed; errors/refusals free), the explicit absence of idempotency (each call is a new charge), and the header/param auth options — all consistent with idempotentHint=false and with a paid tool where destructiveHint reflects credit spend.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense but efficient: billing terms first, then the computation, then interpretation limits and outputs. The opening sentence is about cost rather than what the tool does, which delays purpose slightly, but for a metered tool the charge semantics are the highest-stakes fact and earn their position.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paid, multi-parameter analytical tool this covers pricing, auth, idempotency, inputs used, exclusions, statistical caveat, and explicitly what is NOT returned ('No regime label, position size or trading mode'). With an output schema present, return-value detail is correctly left light while provenance (as_of, verify_url) is still flagged.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: `days` is complete UTC days, `max_metrics` operates 'by name order' with a 3-60 range, and the q = N/(T-1) definition ties the window to the spectrum. It does not explain `metric_filter`, leaving that to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a precise computation on a specific resource: the correlation matrix of daily log changes of a network's stored first-party metrics, its eigenvalues, and the Marchenko-Pastur edges (q = N/(T-1)). That verb+resource pair is specific enough to separate it from spectral siblings like get_hodge_regime_sieve or get_network_signals.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the description of the statistic and the caveat that exceeding the edge 'describes co-movement and is not a test', which tells an agent how to interpret, not when to pick this tool. No sibling alternative is named and no precondition (e.g. minimum metric availability) is stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Kairos Signal — verifiable DePIN data API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.