Kronos (CoinOpAI)
Specialized verticals · tested 2026-08-05 · re-test due 2026-11-05 · by the Hlido desk, not the vendor
In short: A pay-per-call market-context API for agents that repeatedly refuses to be a trading signal — the disclaimers are the most credible thing on the page.
5 PASS · 0 FAIL of 5 public-surface claims
Quick answer
Kronos (CoinOpAI) scores 71/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-08-05). STEADY (71) for disciplined scoping and genuine agent-readiness: a calibrated range rather than a direction call, an explicit non-oracle disclaimer repeated where it matters, a verifiable preflight→decision→audit loop, p Pricing: Usage-based.
Kronos sells structured crypto-market context to agents over x402 on Base mainnet: a conformally-calibrated 80% price range, a risk/cooldown state, a decision journal that returns a decision_id, and an audit endpoint that later checks the outcome against real prices. The product's own framing does the heavy lifting on credibility. It says outright that Kronos is not a buy/sell oracle, repeats twice that directional values are supporting context rather than trade instructions, and organises the whole loop around verification — preflight, decision, audit — under the line "trust the process less, verify the record more". In a category built on implied certainty, an API whose central feature is a calibrated interval and an auditable record is a meaningfully better design. The agent-readiness is also concrete: per-endpoint pricing down to half a cent, a published OpenAPI document, and an llms.txt. The reservations are real. Calibration is asserted ("~0.80 empirical coverage") with no published backtest, sample size, or period; there is no named team, track record, or third-party validation; the operator bundles an unrelated image-generation endpoint and 819 automation prompts, which muddies the focus; and the underlying domain is one where confident-sounding numbers cause real financial loss even when hedged well. Reviewed from the public surface only — we did not pay for a call.
Why STEADY
STEADY (71) for disciplined scoping and genuine agent-readiness: a calibrated range rather than a direction call, an explicit non-oracle disclaimer repeated where it matters, a verifiable preflight→decision→audit loop, per-endpoint pricing to the half-cent, plus OpenAPI and llms.txt. Held below VITAL because the calibration claim is published without any backtest, sample size or period, there is no named team or track record, and the surface mixes in unrelated image-generation and prompt-catalogue endpoints.
Public-surface checklist
- PASS Homepage loads (required)
- PASS Primary value prop (required) — 'Calibrated forecast ranges, risk context, and auditable decision records.'
- PASS Cta present (required) — OpenAPI and llms.txt links plus copy-ready curl examples
- PASS Pricing or access — Full per-endpoint price table, $0.005–$0.25 per call
- PASS Evidence or demo — Sample responses and a documented verification loop; no backtest or third-party validation
What we saw
4 screenshots captured by the Hlido engine during the reviewed run (run-1a0dd38cc879b484-x402-coinopai-com). Our own captures — not vendor marketing material.
What it does well
- Leads with a calibrated 80% interval and risk state rather than a directional buy/sell call
- States plainly that it is not a buy/sell oracle, and repeats that directional values are not trade instructions
- Auditable loop by design — preflight, decision journal with a decision_id, then outcome verification against later prices
- Per-endpoint pricing published to the half-cent, so an agent can budget before calling
- Machine-readable surface: OpenAPI document and llms.txt both published and linked
- x402 pay-per-call on Base mainnet — no account, no subscription, agent-native payment
What it fails at
- The ~0.80 empirical coverage claim is published with no backtest, sample size, time period, or methodology
- No named team, operating history, or third-party validation anywhere on the surface
- Focus is diluted by unrelated bundled endpoints (AI image generation, 819 automation prompts, 115 platforms)
- Crypto market forecasting is a domain where even well-hedged outputs can drive real financial loss
- Data freshness is surfaced as a field but no uptime, latency or availability record is published
- Not tested — we did not purchase a call, so the response quality behind the pricing table is unverified
Red flags
- [object Object]
Best for
- Agent developers who want structured, auditable market context rather than a signal to act on
- Systems that need a decision journal and later outcome verification for compliance or post-mortem
- x402-native agents that must pay per call without an account relationship
Not recommended for
- Anyone seeking trading signals or investment advice — the vendor says this is not that, and neither do we
- Buyers who need published calibration evidence before relying on an interval
- Use cases requiring an availability guarantee or an identifiable, accountable operator
Pricing & access
- ModelUsage-based
- Price points we recorded
Per-endpoint pricing from $0.005 to $0.25, paid via x402 on Base mainnet
- Pricing findable on the public surfacePASS Full per-endpoint price table, $0.005–$0.25 per call (tested 2026-08-04)
Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-04.
Related agents
Agent relevance
API MCP Behavioral-testable
Agentic-Commerce Readiness 71/100 · INTEGRABLE
Independent readiness for agent delegation & transaction. How it’s scored · check live
Agent-native end to end: x402 pay-per-call means no account or key exchange, OpenAPI plus llms.txt make the surface machine-discoverable, and the decision/audit endpoints exist so an agent can journal and later verify its own reasoning.
Agent-friendly score: 9/10
Score over time
The longitudinal record — every point is the score as published on that date. Raw series.
Evidence
- Conformally-calibrated 80% price range as the primary output — source (2026-08-05) verified
- Explicit statement that Kronos is not a buy/sell oracle and directional values are not trade instructions — source (2026-08-05) verified
- Verifiable loop: /api/kronos/preflight → /decision (decision_id) → /audit against later prices — source (2026-08-05) verified
- Per-endpoint pricing from $0.005 to $0.25, paid via x402 on Base mainnet — source (2026-08-05) verified
- OpenAPI document and llms.txt published for machine consumption — source (2026-08-05) verified
- ~0.80 empirical coverage of the calibrated range — source (2026-08-05)



