SnowSignals

SnowSignals is a crypto market-data platform (data-as-a-service) whose TrendVane product serves multi-timeframe market-phase (regime) classifications — market state, not trade signals — for BTC, ETH, GRAM, SOL and TRX over a metered REST API and a hosted, OAuth-gated MCP server. Pricing is prepaid in stablecoin and served in-band by a free, no-auth discovery call, so an agent can compute the exact cost of a read before spending; a free phase-resolution model (successor-transition probabilities, continuation rates, MFE/MAE) supports interpreting each reading. The platform is deliberately agent-native: first-party llms.txt, self-hosted APIs.json, RFC 8414/9728 OAuth discovery, and an official MCP registry listing. A first-party x402 gateway (pay.snowsignals.io, live 2026-09-10) additionally sells the same phase reads pay-per-call in USDC on Base with no account at all.

SnowSignals publishes 5 API contracts indexed on the APIs.io network, including Notifications API, Phase API, Phases API, and 2 more. Tagged areas include Cryptocurrency, Market Data, Bitcoin, Analytics, and market-phase.

The SnowSignals catalog on APIs.io includes 1 Spectral governance ruleset.

SnowSignals’ developer surface includes engineering blog, authentication, and 22 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

33.8/100 thin ▬ flat Agent 54/100 agent ready Front door AI 3/6 light saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessOpen

2 published contracts 1 MCP Servers 2 Agent Skills

Cryptocurrency Market Data Bitcoin Analyticsmarket-phaseregimetrendvaneDaaS MCP Agent-Native Financial Data x402

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Data & Reference Information Services

AE-230

Phase

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 33.8/100 · thin

Contract Quality 9.2 / 19

Developer Ergonomics 3.8 / 15

Access Clarity 3.2 / 15

Operational Transparency 0.5 / 10

Contract Governance 2.9 / 9

Discoverability 5.3 / 8

Regulatory Posture 4.6 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 54/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 6 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Securities & Market Data regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/snowsignals/"><img src="https://apis.io/badge/snowsignals/card.svg" alt="SnowSignals on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks
Agentic Commerce Well-Known Document +5 pts — a parsing /.well-known/ucp.json or acp.json declaring a version and at least one service, OR (0.27) a live x402 payment challenge from _data/x402-adoption.json — `self` when its endpoints are on the provider's own domain, `platform` when they are on a vendor's
Dry-Run / Simulate Mode +4 pts — OpenAPI: destructive operations expose a dry_run / simulate / preview / validate_only parameter

2 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 21.1 — up to +15.8 composite points
Developer Ergonomics scores 25.6 — up to +14.9 composite points
Contract Quality scores 48.8 — up to +12.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/snowsignals/apis.yml: open an issue on github.com/api-evangelist/snowsignals to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
x402 Micropayments & Agentic Pay-per-Call	undeclared	-	1	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 5

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

measured — observed by APIs.io (verified)

x402

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

Dynamic Client Registration

measured — observed by APIs.io (published)

OpenAPI

measured — observed by APIs.io (published)

APIs 5

Individual APIs this provider publishes, each with its own machine-readable definition.

SnowSignals Notifications API

The Notifications API from SnowSignals — 1 operation(s) for notifications.

SnowSignals Phase API

The Phase API from SnowSignals — 6 operation(s) for phase.

SnowSignals Phases API

The Phases API from SnowSignals — 2 operation(s) for phases.

SnowSignals Time API

The Time API from SnowSignals — 1 operation(s) for time.

SnowSignals User API

The User API from SnowSignals — 3 operation(s) for user.

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

SnowSignals MCP Server

MCP SERVER

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

snowsignals-manage-prepaid-balance

AGENT SKILL

snowsignals-read-market-phase

AGENT SKILL

SnowSignals API pricing

Prices published by SnowSignals.

Plan	Price
Prepaid metered (pay-as-you-go)	— Includes: Free with no account: list_phase_meta / GET /api/phases (metadata + live pricing), phase_resolution_
x402 pay-per-call (retail gateway)	— Includes: Free with no payment: GET /phases (metadata + live price list) and GET /phase/resolution-stats (inte

Plan details, limits and sources →

Pricing Plans 1

Published pricing tiers and plan structures.

Snowsignals Plans Pricing

2 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Snowsignals Rate Limits

0 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

SnowSignals

SLA

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

SnowSignals API Rules

53 rules · 51 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 2

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Snowsignals Daas Overlay

10 actions · documentation · snowsignals-daas-openapi.json

GENERATED

Snowsignals X402 Overlay

4 actions · documentation · snowsignals-x402-openapi.json

GENERATED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Snowsignals Authentication

apiKey · 2 schemes

SECURITY

Snowsignals Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Snowsignals Scopes

1 scope

1 scopes

SCOPES

Resources

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

MCPServer

LLMsTxt

WellKnown

MCPServer

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Conformance

Lifecycle

DataModel

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubRepository

GitHubRepository

ToolCrosswalk

ToolCrosswalk

Packages

Packages

Access & Security 3

Authentication, authorization, and security posture

Authentication

Authentication

OAuthScopes

OAuthScopes

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

Plans

Plans

Company 2

The organization behind the API

Blog

Blog

Website

Website

Other 3

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Overlay

Overlay

Source (apis.yml)

name: SnowSignals
description: 'SnowSignals is a crypto market-data platform (data-as-a-service) whose TrendVane product serves multi-timeframe
  market-phase (regime) classifications — market state, not trade signals — for BTC, ETH, GRAM, SOL and TRX over a metered
  REST API and a hosted, OAuth-gated MCP server. Pricing is prepaid in stablecoin and served in-band by a free, no-auth discovery
  call, so an agent can compute the exact cost of a read before spending; a free phase-resolution model (successor-transition
  probabilities, continuation rates, MFE/MAE) supports interpreting each reading. The platform is deliberately agent-native:
  first-party llms.txt, self-hosted APIs.json, RFC 8414/9728 OAuth discovery, and an official MCP registry listing. A first-party
  x402 gateway (pay.snowsignals.io, live 2026-09-10) additionally sells the same phase reads pay-per-call in USDC on Base
  with no account at all.'
deliveryModel:
  model: saas
  license_evidence:
    not_product:
    - snowkidind/snowsignals-mcp
    - snowkidind/snowsignals-x402
  open_source: unknown
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: low
  source:
  - openapi
  - pricing
  - repository-not-product
  generated: '2026-09-25'
  method: derived
accessModel:
  pricing: unknown
  onboarding: open
  trial: false
  try_now: false
  public: true
  gated: none
  gated_source:
  - onboarding
  label: Open access
  confidence: high
  source:
  - plans
  - authentication
  - scopes
  - security
  generated: '2026-11-06'
  method: derived
image: https://snowsignals.io/og-image.png
url: https://raw.githubusercontent.com/api-evangelist/snowsignals/refs/heads/main/apis.yml
created: '2026-09-10'
modified: '2026-10-06'
specificationVersion: '0.21'
tags:
- Cryptocurrency
- Market Data
- Bitcoin
- Analytics
- market-phase
- regime
- trendvane
- DaaS
- MCP
- Agent-Native
- Financial Data
- x402
tags_raw:
- crypto
- market-data
- bitcoin
- analytics
- market-phase
- regime
- trendvane
- daas
- mcp
- agent-native
- financial-data
- x402
apis:
- aid: snowsignals:snowsignals-notifications-api
  name: SnowSignals Notifications API
  description: The Notifications API from SnowSignals — 1 operation(s) for notifications.
  humanURL: https://snowsignals.io/docs
  baseURL: https://snowsignals.io/v1
  tags:
  - Notification
  tags_raw:
  - Notifications
  properties:
  - type: OpenAPI
    url: openapi/snowsignals-notifications-api-openapi.yml
  - type: Documentation
    url: https://snowsignals.io/docs
  - type: ToolCrosswalk
    url: mcp/snowsignals-tool-crosswalk.yml
  - type: Documentation
    url: https://x402.snowsignals.io
  - type: LLMsTxt
    url: llms/snowsignals-x402-llms.txt
  - type: GitHubRepository
    url: https://github.com/snowkidind/snowsignals-x402
- aid: snowsignals:snowsignals-phase-api
  name: SnowSignals Phase API
  description: The Phase API from SnowSignals — 6 operation(s) for phase.
  humanURL: https://snowsignals.io/docs
  baseURL: https://snowsignals.io/v1
  tags:
  - Phase
  properties:
  - type: OpenAPI
    url: openapi/snowsignals-phase-api-openapi.yml
  - type: Documentation
    url: https://snowsignals.io/docs
  - type: ToolCrosswalk
    url: mcp/snowsignals-tool-crosswalk.yml
  - type: Documentation
    url: https://x402.snowsignals.io
  - type: LLMsTxt
    url: llms/snowsignals-x402-llms.txt
  - type: GitHubRepository
    url: https://github.com/snowkidind/snowsignals-x402
- aid: snowsignals:snowsignals-phases-api
  name: SnowSignals Phases API
  description: The Phases API from SnowSignals — 2 operation(s) for phases.
  humanURL: https://snowsignals.io/docs
  baseURL: https://snowsignals.io/v1
  tags:
  - Phases
  properties:
  - type: OpenAPI
    url: openapi/snowsignals-phases-api-openapi.yml
  - type: Documentation
    url: https://snowsignals.io/docs
  - type: ToolCrosswalk
    url: mcp/snowsignals-tool-crosswalk.yml
  - type: Documentation
    url: https://x402.snowsignals.io
  - type: LLMsTxt
    url: llms/snowsignals-x402-llms.txt
  - type: GitHubRepository
    url: https://github.com/snowkidind/snowsignals-x402
- aid: snowsignals:snowsignals-time-api
  name: SnowSignals Time API
  description: The Time API from SnowSignals — 1 operation(s) for time.
  humanURL: https://snowsignals.io/docs
  baseURL: https://snowsignals.io/v1
  tags:
  - Time
  properties:
  - type: OpenAPI
    url: openapi/snowsignals-time-api-openapi.yml
  - type: Documentation
    url: https://snowsignals.io/docs
  - type: ToolCrosswalk
    url: mcp/snowsignals-tool-crosswalk.yml
  - type: Documentation
    url: https://x402.snowsignals.io
  - type: LLMsTxt
    url: llms/snowsignals-x402-llms.txt
  - type: GitHubRepository
    url: https://github.com/snowkidind/snowsignals-x402
- aid: snowsignals:snowsignals-user-api
  name: SnowSignals User API
  description: The User API from SnowSignals — 3 operation(s) for user.
  humanURL: https://snowsignals.io/docs
  baseURL: https://snowsignals.io/v1
  tags:
  - User
  properties:
  - type: OpenAPI
    url: openapi/snowsignals-user-api-openapi.yml
  - type: Documentation
    url: https://snowsignals.io/docs
  - type: ToolCrosswalk
    url: mcp/snowsignals-tool-crosswalk.yml
  - type: Documentation
    url: https://x402.snowsignals.io
  - type: LLMsTxt
    url: llms/snowsignals-x402-llms.txt
  - type: GitHubRepository
    url: https://github.com/snowkidind/snowsignals-x402
common:
- type: CapabilityMap
  url: capabilities/snowsignals-capability-edges.yml
  name: SnowSignals Business Capability Map
- url: https://snowsignals.io/blog/
  type: Blog
- type: Overlay
  url: overlays/snowsignals-daas-overlay.yaml
- type: MCPServer
  url: https://snowsignals.io/mcp
- type: Overlay
  url: overlays/snowsignals-x402-overlay.yaml
- type: Website
  url: https://snowsignals.io
- type: TermsOfService
  url: https://snowsignals.io/terms
- type: GitHubRepository
  url: https://github.com/snowkidind/snowsignals-mcp
- type: LLMsTxt
  url: llms/snowsignals-llms.txt
- type: WellKnown
  url: well-known/snowsignals-well-known.yml
- type: MCPServer
  url: mcp/snowsignals-mcp.yml
- type: ToolCrosswalk
  url: mcp/snowsignals-tool-crosswalk.yml
- type: Authentication
  url: authentication/snowsignals-authentication.yml
- type: OAuthScopes
  url: scopes/snowsignals-scopes.yml
- type: Conventions
  url: conventions/snowsignals-conventions.yml
- type: ErrorCatalog
  url: errors/snowsignals-problem-types.yml
- type: Conformance
  url: conformance/snowsignals-conformance.yml
- type: Lifecycle
  url: lifecycle/snowsignals-lifecycle.yml
- type: Plans
  url: plans/snowsignals-plans-pricing.yml
- type: RateLimits
  url: rate-limits/snowsignals-rate-limits.yml
- type: DataModel
  url: data-model/snowsignals-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
- type: DomainSecurity
  url: security/snowsignals-domain-security.yml
- type: Packages
  url: packages/snowsignals-packages.yml
maintainers:
- FN: SnowSignals
  url: https://snowsignals.io
x-source:
  via: apis.io/add 0cabc61c, parked unverifiable_host; listed by Kin 2026-09-10 on what is served
  fetched: '2026-09-10'
  note: 'The round-1 guard ("do not reconstruct a spec") is satisfied and dropped: the real contract surfaced and was harvested
    the same day — first-party OpenAPI at https://snowsignals.io/v1/openapi.json (200, servers[] snowsignals.io/v1, contact
    snowsignals.io), live MCP at https://snowsignals.io/mcp (registry io.snowsignals/snowsignals), llms.txt and a self-hosted
    apis.json both advertised from the page head. The host soft-200s unknown HTML routes (SPA shell), so page pointers here
    are limited to provider-declared routes; JSON paths return real 404s and were probed honestly.'
x-enrichment:
  date: '2026-09-10'
  status: enriched
  artifacts_added: 4
  pass: local-v3
  note: 'Second same-day pass: found the x402 gateway LIVE (it 404d on the morning pass) — saved its first-party OpenAPI +
    llms.txt from x402.snowsignals.io, recorded the live 402 challenge in plans/ and conformance/, added the legacy npm package
    inventory (packages/), and registered the gateway as a second API entry.'

SnowSignals API — frequently asked questions

Does SnowSignals have an API?

Yes. APIs.io lists 5 APIs from SnowSignals, including SnowSignals Notifications API, SnowSignals Phase API and SnowSignals Phases API, and 2 more.

Is there an OpenAPI specification for the SnowSignals API?

Yes. APIs.io indexes 5 OpenAPI specifications for SnowSignals, each linked for download from this page.

How do I authenticate with the SnowSignals API?

SnowSignals documents its authentication (apiKey · 2 schemes). The details are profiled on APIs.io as Snowsignals Authentication.

How much does the SnowSignals API cost?

APIs.io lists 2 pricing plans for SnowSignals, with each plan's price, limits and inclusions under Pricing on this page.

Does SnowSignals have an MCP server?

Yes. APIs.io lists 1 MCP server for SnowSignals.

Is the SnowSignals API ready for AI agents?

SnowSignals has a Kin Score of 33.8 out of 100 (thin) and an Agent Readiness score of 53.9 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/snowsignals"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/snowsignals/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/snowsignals/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.