Espresso website screenshot

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 publishes 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.

31.2/100 thin ▬ flat Agent 15/100 agent aware Full breakdown ↓
scored 2026-07-27 · rubric v0.5
1 APIs
CompanyBlockchainWeb3InfrastructureConsensusSequencerRollupData AvailabilityEthereumDeFiREST APICryptography

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 31.2/100 · thin
Contract Quality 5.7 / 25
Developer Ergonomics 10.4 / 20
Commercial Clarity 2.1 / 20
Operational Transparency 3.8 / 13
Governance 0.0 / 12
Discoverability 9.3 / 10
Agent readiness — 15/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
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
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/espresso: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

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.

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

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
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
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-19'
image: https://www.espressosys.com/
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