Celo website screenshot

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 publishes 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 19 more developer resources.

31.4/100 thin ▬ flat Agent 4/100 human only saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
1 APIs 1 MCP Servers
CompanyBlockchainEthereum L2Web3StablecoinsPaymentsJSON-RPCSmart ContractsAI AgentsDeveloper Tools

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
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/.
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/celo: 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.

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

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

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Build 4

SDKs, sample code, and the tooling you integrate with

Access & Security 4

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
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: []
  generated: '2026-07-22'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-18'
image: https://framerusercontent.com/assets/vn0V92oZLFWJWDd5ypiVsqJilg.png
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:
- 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

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"

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.

A second provider on the same verified email joins the account you already have.