Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Cartesi website screenshot

Cartesi

Cartesi is a Linux-based optimistic rollup protocol that lets developers build decentralized applications by running rich off-chain computation inside a sandboxed Linux virtual machine. The core of the stack is the Cartesi Machine, a deterministic RISC-V emulator that boots a real Linux userland so dApps can be written in any language (Rust, Go, Python, JavaScript/TypeScript, C++) using familiar libraries, then settle results on Ethereum and other EVM chains through Cartesi Rollups smart contracts. Cartesi Rollups 2.0 is the current major version, packaging an application-specific rollup as the combination of the Cartesi Machine, the Cartesi Rollups Node middleware (Rust + Go), and a set of Solidity rollup contracts that handle settlement, consensus, and data availability. The DAVE permissionless fraud-proof system provides Stage-2 trust minimization, while the Cartesi CLI (the successor to Sunodo) packages scaffolding, build, and local devnet workflows. Cartesi is stewarded by The Cartesi Foundation and the CTSI token governs the network. Cartesi is fully open source under Apache-2.0 and LGPL-3.0 licenses on github.com/cartesi; there is no proprietary SaaS product, but the Rollups Node ships several developer-facing surfaces — the Rollup HTTP API used by application backends, the Inspect HTTP API for read-only queries from frontends, a GraphQL reader for advance-state inputs / outputs / vouchers / notices / reports, and a JSON-RPC node API for operations.

human only

Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.

Kin Score

API Evangelist profiles Cartesi the way a machine reads it — 2 machine-readable artifacts, 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 — Cartesi scores 12.2/100 (minimal), with a separate agent-readiness read of 0/100 (human only). 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.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 12.2/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 4.8 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 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

How we profile Cartesi

Each block below is one kind of artifact we hold for Cartesi. 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.

GraphQL 1

Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.

GraphQL schemas published by this provider.

Security Posture 1

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.

Cartesi Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Every other property we hold for Cartesi — 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.

Documentation 2

Reference material describing how the API behaves

Access & Security 1

Authentication, authorization, and security posture

Learn 2

Tutorials, courses, talks, and written guidance

Operate 1

Status, limits, changes, and where to get help

Company 3

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/cartesi · machine-readable index on apis.io