Quai Network

Quai Network is a sharded, EVM-compatible proof-of-work Layer-1 blockchain built by Dominant Strategies, featuring two native assets: QUAI, a smart-contract account-model asset, and Qi, a UTXO-model privacy asset. Quai uses Proof-of-Entropy-Minima (PoEM) consensus with merged mining across a hierarchical structure of Prime, Region, and Zone chains braided into one network. For developers, Quai exposes an Ethereum-compatible JSON-RPC API in the `quai_` namespace (plus a GraphQL endpoint and Postman collection), the Quais SDK (a fork of Ethers v6) for JavaScript/TypeScript dApps and wallets, and the go-quai node/CLI for running nodes and miners. The canonical active zone is Cyprus-1 (chainId 9 on mainnet, 15000 on the Orchard testnet).

Quai Network publishes 1 API on the APIs.io network: JSON-RPC API. Tagged areas include Company, Layer 1, Blockchain, Cryptocurrency, and Web3.

Quai Network’s developer surface includes documentation, API reference, getting-started guide, engineering blog, support, CLI, authentication, and 15 more developer resources.

🌐 Visit website 📡 Source on GitHub

25.3/100 emerging ▬ flat Agent 5/100 agent aware library Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

1 APIs

Company Layer 1 Blockchain Cryptocurrency Web3 Smart Contracts EVM JSON-RPC Proof of Work Developer Tools

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 25.3/100 · emerging

Contract Quality 0.0 / 25

Developer Ergonomics 14.8 / 20

Access Clarity 0.0 / 20

Operational Transparency 2.4 / 13

Contract Governance 0.5 / 12

Discoverability 7.6 / 10

Agent readiness — 5/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 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 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

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 github.com/api-evangelist/quai-network: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

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

Quai Network JSON-RPC API

Ethereum-compatible JSON-RPC API for Quai Network in the `quai_` namespace. Query balances, code, storage and proofs; read blocks, headers and uncles; look up and send transacti...

Security Posture 2

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

Quai Network Authentication

none · 2 schemes

SECURITY

Quai Network Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

X-MCPServerCandidate

X-MCPServerCandidate

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

Build 5

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Postman

Packages

SDKs

CLI

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Support

Support

ChangeLog

ChangeLog

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Grants

Grants

Source (apis.yml)

aid: quai-network
name: Quai Network
description: 'Quai Network is a sharded, EVM-compatible proof-of-work Layer-1 blockchain built by Dominant Strategies, featuring
  two native assets: QUAI, a smart-contract account-model asset, and Qi, a UTXO-model privacy asset. Quai uses Proof-of-Entropy-Minima
  (PoEM) consensus with merged mining across a hierarchical structure of Prime, Region, and Zone chains braided into one network.
  For developers, Quai exposes an Ethereum-compatible JSON-RPC API in the `quai_` namespace (plus a GraphQL endpoint and Postman
  collection), the Quais SDK (a fork of Ethers v6) for JavaScript/TypeScript dApps and wallets, and the go-quai node/CLI for
  running nodes and miners. The canonical active zone is Cyprus-1 (chainId 9 on mainnet, 15000 on the Orchard testnet).'
deliveryModel:
  model: library
  open_source: false
  commercial: false
  callable_host: false
  label: Library · distributed through package registries, no callable service
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://avatars.githubusercontent.com/u/54382906?v=4
url: https://raw.githubusercontent.com/api-evangelist/quai-network/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- polychain
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Company
- Layer 1
- Blockchain
- Cryptocurrency
- Web3
- Smart Contracts
- EVM
- JSON-RPC
- Proof of Work
- Developer Tools
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: Quai Network JSON-RPC API
  description: 'Ethereum-compatible JSON-RPC API for Quai Network in the `quai_` namespace. Query balances, code, storage
    and proofs; read blocks, headers and uncles; look up and send transactions (Protobuf-encoded); inspect the txpool; read
    gas and fee history; and perform Quai <-> Qi conversions. Served over HTTPS and WSS per zone (canonical zone: Cyprus-1).'
  humanURL: https://docs.qu.ai/build/playground/overview
  baseURL: https://rpc.quai.network/cyprus1
  properties:
  - type: Documentation
    url: https://docs.qu.ai/build/introduction
  - type: APIReference
    url: https://docs.qu.ai/build/playground/overview
  - type: GraphQL
    url: https://graph.quai.network
  - type: Postman
    url: https://docs.qu.ai/build/apis/postman/setup
  - type: Authentication
    url: authentication/quai-network-authentication.yml
  - type: Conventions
    url: conventions/quai-network-conventions.yml
  - type: ErrorCatalog
    url: errors/quai-network-problem-types.yml
  - type: Conformance
    url: conformance/quai-network-conformance.yml
  - type: X-MCPServerCandidate
    url: mcp/quai-network-mcp.yml
    note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list
      derived from the published API contracts, not an existing server. The scorer already read the manifest and reported
      mcp_server correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
common:
- type: Website
  url: https://qu.ai
- type: DeveloperPortal
  url: https://docs.qu.ai
- type: Documentation
  url: https://docs.qu.ai/build/introduction
- type: APIReference
  url: https://docs.qu.ai/build/playground/overview
- type: GettingStarted
  url: https://docs.qu.ai/build/introduction
- type: GitHubOrganization
  url: https://github.com/dominant-strategies
- type: Blog
  url: https://quainetwork.com/blog
- type: Support
  url: https://discord.com/invite/ngw88VXXnV
- type: Grants
  url: https://docs.qu.ai/build/grants
- type: Postman
  url: https://docs.qu.ai/build/apis/postman/setup
- type: LLMsTxt
  url: llms/quai-network-llms.txt
- type: Packages
  url: packages/quai-network-packages.yml
- type: SDKs
  url: packages/quai-network-packages.yml
- type: CLI
  url: cli/quai-network-cli.yml
- type: Authentication
  url: authentication/quai-network-authentication.yml
- type: Conventions
  url: conventions/quai-network-conventions.yml
- type: ErrorCatalog
  url: errors/quai-network-problem-types.yml
- type: Lifecycle
  url: lifecycle/quai-network-lifecycle.yml
- type: Conformance
  url: conformance/quai-network-conformance.yml
- type: X-MCPServerCandidate
  url: mcp/quai-network-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: ChangeLog
  url: changelog/quai-network-changelog.yml
- type: DomainSecurity
  url: security/quai-network-domain-security.yml
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 12
  pass: local-v1

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/quai-network"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/quai-network/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

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.