Celo

Celo is a leading Ethereum Layer 2 (L2) blockchain built for real-world usage, mobile-first payments, and stablecoins, run by cLabs and the Celo Foundation. It offers a fully EVM- and Ethereum-JSON-RPC-compatible network reachable through the public Forno RPC endpoints, gas-fee abstraction that lets users pay fees in stablecoins, and a developer stack spanning TypeScript SDKs (ContractKit, @celo/connect, @celo/abis, @celo/identity), the Celo Composer CLI scaffolding tool, a published Model Context Protocol (MCP) server for AI agents, and agent-payment protocols (x402, MPP, ERC-8004). Developers build dApps, MiniPay mini-apps, DeFi, and AI agents against the Celo Mainnet (chain 42220) and the Celo Sepolia testnet.

Celo is listed with 1 API on the APIs.io network. Tagged areas include Company, Blockchain, Ethereum L2, Web3, and Stablecoins.

Celo’s developer surface includes sandbox, documentation, API reference, getting-started guide, engineering blog, support, CLI, and 20 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

30.4/100 thin ▬ flat Agent 4/100 human only Front door AI 5/6 prominent Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API 1 MCP Servers

Company BlockchainEthereum L2Web3 Stablecoins Payments JSON-RPC Smart Contracts AI Agents Developer Tools

Kin Score

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

Composite quality — 30.4/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 11.3 / 17

Access Clarity 3.6 / 17

Operational Transparency 2.6 / 11

Contract Governance 1.9 / 10

Discoverability 6.1 / 9

Regulatory Posture 3.3 / 15

Agent readiness — 4/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 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

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 Payments 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/celo/"><img src="https://apis.io/badge/celo/card.svg" alt="Celo 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):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
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

12 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 21.1 — up to +15.8 composite points
Operational Transparency scores 23.7 — up to +9.9 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/celo/apis.yml: open an issue on github.com/api-evangelist/celo 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
Agent Skills (SKILL.md packages)	standard	26.8 (thin)	-	1
Stablecoins and Tokenization (stablecoin issuers, tokenized assets)	standard	26.8 (thin)	-	1
x402 Micropayments & Agentic Pay-per-Call	standard	26.8 (thin)	-	1

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.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

JSON RPC

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

Model Context Protocol (MCP)

measured — observed by APIs.io (documented)

APIs 1

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

Celo JSON-RPC API

Ethereum-compatible JSON-RPC API for the Celo Layer 2 network, served over the public Forno endpoints. Supports the standard eth_* / net_* / web3_* method set for reading chain ...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Celo MCP Server

Model Context Protocol server providing AI assistants and IDEs comprehensive access to the Celo blockchain: blockchain data, token operations, NFTs, smart contracts, transaction...

MCP SERVER

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Celo

SLA

Security Posture 2

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

Celo Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Celo Vulnerability Disclosure

security.txt · contact published

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

Sandbox

Sandbox

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

MCPServer

MCPServer

LLMsTxt

LLMsTxt

WellKnown

WellKnown

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Lifecycle

Lifecycle

Conformance

Conformance

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

SDKs

CLI

Access & Security 4

Authentication, authorization, and security posture

SecurityTxt

SecurityTxt

DomainSecurity

DomainSecurity

VulnerabilityDisclosure

VulnerabilityDisclosure

Security

Security

Operate 3

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

Deprecation

Deprecation

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

BlogRSS

BlogRSS

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Whitepaper

Whitepaper

Source (apis.yml)

aid: celo
name: Celo
description: Celo is a leading Ethereum Layer 2 (L2) blockchain built for real-world usage, mobile-first payments, and stablecoins,
  run by cLabs and the Celo Foundation. It offers a fully EVM- and Ethereum-JSON-RPC-compatible network reachable through
  the public Forno RPC endpoints, gas-fee abstraction that lets users pay fees in stablecoins, and a developer stack spanning
  TypeScript SDKs (ContractKit, @celo/connect, @celo/abis, @celo/identity), the Celo Composer CLI scaffolding tool, a published
  Model Context Protocol (MCP) server for AI agents, and agent-payment protocols (x402, MPP, ERC-8004). Developers build dApps,
  MiniPay mini-apps, DeFi, and AI agents against the Celo Mainnet (chain 42220) and the Celo Sepolia testnet.
url: https://raw.githubusercontent.com/api-evangelist/celo/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- a16z
- general-catalyst
- version-one-ventures
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
image: https://framerusercontent.com/assets/vn0V92oZLFWJWDd5ypiVsqJilg.png
x-docs-platform: mintlify
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-09-21
x-docs-hosting: vercel
tags:
- Company
- Blockchain
- Ethereum L2
- Web3
- Stablecoins
- Payments
- JSON-RPC
- Smart Contracts
- AI Agents
- Developer Tools
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: Celo JSON-RPC API
  description: Ethereum-compatible JSON-RPC API for the Celo Layer 2 network, served over the public Forno endpoints. Supports
    the standard eth_* / net_* / web3_* method set for reading chain state, submitting transactions, calling smart contracts,
    and querying balances, plus Celo fee-abstraction extensions.
  humanURL: https://docs.celo.org/build-on-celo/network-overview
  baseURL: https://forno.celo.org
  properties:
  - type: Documentation
    url: https://docs.celo.org/build-on-celo/network-overview
  - type: MCPServer
    url: mcp/celo-mcp.yml
common:
- url: https://blog.celo.org/feed
  type: BlogRSS
- type: Whitepaper
  url: https://celo.org/papers
- type: Sandbox
  url: sandbox/celo-sandbox.yml
- type: Website
  url: https://celo.org
- type: DeveloperPortal
  url: https://docs.celo.org
- type: Documentation
  url: https://docs.celo.org
- type: APIReference
  url: https://docs.celo.org/build-on-celo/network-overview
- type: GettingStarted
  url: https://docs.celo.org/build-on-celo/quickstart
- type: Blog
  url: https://blog.celo.org
- type: Support
  url: https://forum.celo.org
- type: GitHubOrganization
  url: https://github.com/celo-org
- type: TermsOfService
  url: https://celo.org/terms-of-use
- type: PrivacyPolicy
  url: https://celo.org/privacy-policy
- type: StatusPage
  url: https://status.celo.org
- type: Packages
  url: packages/celo-packages.yml
- type: SDKs
  url: packages/celo-packages.yml
- type: CLI
  url: cli/celo-cli.yml
- type: MCPServer
  url: mcp/celo-mcp.yml
- type: LLMsTxt
  url: llms/celo-llms.txt
- type: WellKnown
  url: well-known/celo-well-known.yml
- type: SecurityTxt
  url: well-known/celo-security.txt
- type: DomainSecurity
  url: security/celo-domain-security.yml
- type: VulnerabilityDisclosure
  url: security/celo-vulnerability-disclosure.yml
- type: Security
  url: https://celo.org/.well-known/security.txt
- type: Lifecycle
  url: lifecycle/celo-lifecycle.yml
- type: Deprecation
  url: lifecycle/celo-lifecycle.yml
- type: Conformance
  url: conformance/celo-conformance.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Celo API — frequently asked questions

Does Celo have an API?

Yes. APIs.io lists 1 API from Celo, including Celo JSON-RPC API.

Does Celo have an MCP server?

Yes. APIs.io lists 1 MCP server for Celo: Model Context Protocol server providing AI assistants and IDEs comprehensive access to the Celo blockchain: blockchain data, token operations, NFTs, smart contracts, transactions, and governance. Publ

Is the Celo API ready for AI agents?

Celo has a Kin Score of 30.4 out of 100 (thin) and an Agent Readiness score of 3.5 (human-only), 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/celo"

All providers

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

Every operation they expose

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

How their score was established

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