Espresso

Espresso Systems builds the Espresso Network, a high-performance consensus and sequencing layer that gives rollups and institution-grade financial applications real-time settlement (~3 second finality) without sacrificing control, privacy, or connectivity to global onchain liquidity. The network is a permissionless delegated-proof-of-stake system (Mainnet 1.0, live) built on the HotShot BFT consensus protocol and the Tiramisu data-availability layer, confirming transactions for integrated Arbitrum Nitro/Orbit and OP Stack chains. Espresso nodes and query services expose a public, no-auth REST + WebSocket API (built on the Tide Disco framework) across modules for availability, node state, consensus status, catchup, explorer, events streaming, and transaction submission. The API is served on both the Ethereum-mainnet-anchored Mainnet and the Sepolia-anchored Decaf testnet, with content negotiation between JSON and binary and URL-path major versioning (v0 → v1).

Espresso is listed with 1 API on the APIs.io network. Tagged areas include Company, Blockchain, Web3, Infrastructure, and Consensus.

The Espresso catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Espresso’s developer surface includes documentation, API reference, getting-started guide, engineering blog, changelog, support, authentication, and 11 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

35.4/100 thin ▬ flat Agent 20/100 agent aware Front door AI 1/6 silent Heartbeat 98/100 alive Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API

Company Blockchain Web3 Infrastructure ConsensusSequencerRollup Data Availability Ethereum DeFi REST API Cryptography

Kin Score

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

Composite quality — 35.4/100 · thin

Contract Quality 8.3 / 21

Developer Ergonomics 9.7 / 17

Access Clarity 1.8 / 17

Operational Transparency 2.9 / 11

Contract Governance 0.5 / 10

Discoverability 6.2 / 9

Regulatory Posture 3.1 / 15

Agent readiness — 20/100 · agent aware

Machine-Readable Contract 18 / 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 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 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

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) 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 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.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% 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/espresso/"><img src="https://apis.io/badge/espresso/card.svg" alt="Espresso 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):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
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)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)

10 more unmet checks in the Agent Readiness table above.

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

Access Clarity scores 10.5 — up to +17.9 composite points
Contract Quality scores 39.0 — up to +15.3 composite points
Contract Governance scores 4.5 — up to +11.5 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/espresso/apis.yml: open an issue on github.com/api-evangelist/espresso 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
LF Decentralized Trust (Hyperledger) Members and Projects (enterprise blockchain, digital identity, CBDC)	standard	51.7	-	-

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.

APIs 1

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

Espresso Network Query Service API

The public REST and WebSocket API served by Espresso query services and nodes (Tide Disco framework). Comprises independent modules — availability (Tiramisu DA blocks/headers/pa...

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Espresso Events Webhooks

ASYNCAPI

Security Posture 2

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

Espresso Authentication

none · 0 schemes

SECURITY

Espresso 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 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Conventions

Lifecycle

Conformance

Webhooks

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 3

Status, limits, changes, and where to get help

ChangeLog

ChangeLog

Support

Support

ChangeLog

ChangeLog

Commercial 1

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: espresso
name: Espresso
description: Espresso Systems builds the Espresso Network, a high-performance consensus and sequencing layer that gives rollups
  and institution-grade financial applications real-time settlement (~3 second finality) without sacrificing control, privacy,
  or connectivity to global onchain liquidity. The network is a permissionless delegated-proof-of-stake system (Mainnet 1.0,
  live) built on the HotShot BFT consensus protocol and the Tiramisu data-availability layer, confirming transactions for
  integrated Arbitrum Nitro/Orbit and OP Stack chains. Espresso nodes and query services expose a public, no-auth REST + WebSocket
  API (built on the Tide Disco framework) across modules for availability, node state, consensus status, catchup, explorer,
  events streaming, and transaction submission. The API is served on both the Ethereum-mainnet-anchored Mainnet and the Sepolia-anchored
  Decaf testnet, with content negotiation between JSON and binary and URL-path major versioning (v0 → v1).
url: https://raw.githubusercontent.com/api-evangelist/espresso/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- a16z
- electric-capital
- greylock
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  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
  - security
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
image: https://www.espressosys.com/
x-docs-platform: gitbook
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-03
tags:
- Company
- Blockchain
- Web3
- Infrastructure
- Consensus
- Sequencer
- Rollup
- Data Availability
- Ethereum
- DeFi
- REST API
- Cryptography
apis:
- name: Espresso Network Query Service API
  description: The public REST and WebSocket API served by Espresso query services and nodes (Tide Disco framework). Comprises
    independent modules — availability (Tiramisu DA blocks/headers/payloads/VID), node, status, catchup, state, explorer,
    hotshot-events streaming, and submit (post transactions to the public mempool) — each versioned via URL path (v0/v1) and
    negotiating JSON or binary via Content-Type/Accept. Read endpoints are unauthenticated; there is no "latest block" query
    — clients index by block height or hash.
  humanURL: https://docs.espressosys.com/network/developer/espresso-api
  baseURL: https://query.main.net.espresso.network/v1
  tags:
  - Blockchain
  - Consensus
  - Data Availability
  - Query
  - REST
  properties:
  - type: Documentation
    url: https://docs.espressosys.com/network/developer/espresso-api
  - type: APIReference
    url: https://docs.espressosys.com/network/developer/espresso-api
  - type: LLMsTxt
    url: llms/espresso-llms.txt
  - type: Authentication
    url: authentication/espresso-authentication.yml
  - type: Conventions
    url: conventions/espresso-conventions.yml
  - type: Webhooks
    url: asyncapi/espresso-events-webhooks.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.espressosys.com/
- type: DeveloperPortal
  url: https://docs.espressosys.com/
- type: Documentation
  url: https://docs.espressosys.com/network/developer/espresso-api
- type: APIReference
  url: https://docs.espressosys.com/network/developer/espresso-api
- type: GettingStarted
  url: https://docs.espressosys.com/network/learn/quickstart
- type: GitHubOrganization
  url: https://github.com/EspressoSystems
- type: Blog
  url: https://medium.com/@espressosys
- type: ChangeLog
  url: https://docs.espressosys.com/network/network/changelog
- type: PrivacyPolicy
  url: https://www.espressosys.com/privacy-policy
- type: Support
  url: https://discord.com/invite/DRfcHRnnBz
- type: LLMsTxt
  url: llms/espresso-llms.txt
- type: Authentication
  url: authentication/espresso-authentication.yml
- type: Conventions
  url: conventions/espresso-conventions.yml
- type: ChangeLog
  url: changelog/espresso-changelog.yml
- type: Lifecycle
  url: lifecycle/espresso-lifecycle.yml
- type: Conformance
  url: conformance/espresso-conformance.yml
- type: DomainSecurity
  url: security/espresso-domain-security.yml
- type: Webhooks
  url: asyncapi/espresso-events-webhooks.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Espresso API — frequently asked questions

Does Espresso have an API?

Yes. APIs.io lists 1 API from Espresso, including Espresso Network Query Service API.

How do I authenticate with the Espresso API?

Espresso uses bearer-token authentication (none · 0 schemes). The details are profiled on APIs.io as Espresso Authentication.

Is the Espresso API ready for AI agents?

Espresso has a Kin Score of 35.4 out of 100 (thin) and an Agent Readiness score of 19.8 (agent-aware), 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/espresso"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/espresso/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.