Supra
Supra is a vertically integrated Layer 1 blockchain developed by the Swiss-based Entropy Foundation, combining a MultiVM execution layer (MoveVM plus an EVM) with services that most chains outsource: DORA native oracle price feeds (push and pull), decentralized verifiable randomness (dVRF), protocol-level automation (AutoFi), on-chain technical indicators and indices, and the SupraNova / HyperNova cross-chain bridge. Developers reach the network through a public, keyless REST + JSON node API at rpc-mainnet.supra.com that publishes a live OpenAPI 3.1 description covering 56 operations across accounts, transactions, blocks, events, view functions, tables and inclusion proofs, plus a JSON-RPC WebSocket subscription stream for newly committed blocks. Market data is served separately by an API-key-gated Price Feeds REST and WebSocket API for real-time and historical OHLC data. Supra is headquartered in Miami, Florida and was founded in 2019.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Supra the way a machine reads it — 9 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Supra scores 49.9/100 (developing), with a separate agent-readiness read of 36/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-01 · rubric v0.18.0
Put this on your own site. The badge is drawn live from Supra's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/supra/"
title="Supra on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/supra.svg"
alt="Supra Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/supra/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/supra/"
title="Supra on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/supra/card.svg"
alt="Supra Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Supra
Each block below is one kind of artifact we hold for Supra. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 4
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Supra RPC Node API
Public, keyless REST + JSON API served by every Supra RPC node. Covers accounts (resources, modules, coin and fungible-asset statements), transaction submission and simulation, ...
Supra Price Feeds REST API
Oracle market-data REST API returning the latest price for a trading pair and historical OHLC candles for up to one month, on the DORA data feeds Supra publishes on-chain. Two d...
Supra Price Feeds WebSocket API
Streaming oracle market-data API. Clients open a WebSocket to wss://prod-kline-ws.supra.com with an x-api-key header and send a subscribe action naming the ohlc_datafeed channel...
Supra Automation API
Read and observation surface for Supra's native on-chain automation (AutoFi) registry. Automation tasks are registered and cancelled through the Supra CLI and Move entry functio...
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Supra Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Supra Rate Limits
RATE LIMITSSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Supra — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/supra · machine-readable index on apis.io
This is an independent, third-party profile of Supra, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.