Consensys

Consensys is a blockchain and Web3 software company founded by Ethereum co-founder Joseph Lubin that builds core Ethereum infrastructure and developer tooling for the decentralized web. Its product suite includes MetaMask (the self-custodial wallet and MetaMask Developer / Connect SDK), Infura (managed, high-availability JSON-RPC blockchain node APIs, IPFS, and a Gas API across Ethereum and 40+ EVM networks), Linea (a zkEVM Layer 2 network), Besu and Teku (execution and consensus clients), and Diligence/MythX smart-contract security tooling. Developers use Infura's API-key-authenticated JSON-RPC 2.0 endpoints to read and broadcast to Ethereum, Base, Arbitrum, Optimism, Polygon, Linea and more without operating their own nodes.

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

Consensys’ developer surface includes documentation, API reference, getting-started guide, support, engineering blog, pricing, signup flow, and 24 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

50.1/100 developing ▲ 7.9 Agent 5/100 agent aware Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →

1 API

Company Infrastructure Blockchain Ethereum Web3 Developer Tools JSON-RPC Node Infrastructure Wallets Layer 2

Kin Score

Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0

Composite quality — 50.1/100 · developing

Contract Quality 0.0 / 21

Developer Ergonomics 12.1 / 17

Access Clarity 17.0 / 17

Operational Transparency 4.4 / 11

Contract Governance 1.9 / 10

Discoverability 5.6 / 9

Regulatory Posture 4.8 / 15

Agent readiness — 5/100 · agent aware

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

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

11 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
Contract Governance scores 18.2 — up to +9.8 composite points
Operational Transparency scores 39.5 — up to +7.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/consensys/apis.yml: open an issue on github.com/api-evangelist/consensys 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
Infrastructure-as-Code Provider Registries (Terraform, OpenTofu, Pulumi)	standard	56.5	-	-
LF Decentralized Trust (Hyperledger) Members and Projects (enterprise blockchain, digital identity, CBDC)	standard	56.5	-	-

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.

The Ethereum JSON-RPC Interface

prose — states compatibility; nothing published to check it against

22 core of 78 operations graded · api-commons/blockchain

JSON RPC

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

APIs 1

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

Infura Web3 API

Infura's managed Web3 API surface — JSON-RPC 2.0 access to Ethereum and 40+ EVM networks (Base, Arbitrum, Optimism, Polygon, Linea, and more), plus IPFS and a Gas API. Authentic...

Pricing Plans 2

Published pricing tiers and plan structures.

Consensys Plans Pricing

5 plans

PLANS

Consensys Price Estimates

0 plans

PLANS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Consensys Finops

FINOPS

Security Posture 4

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

Consensys Authentication

apiKey · 1 scheme

SECURITY

Consensys Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Consensys Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Consensys Trust Center

SOC 2, ISO 27001

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

GettingStarted

SignUp

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 7

Authentication, authorization, and security posture

Authentication

Compliance

TrustCenter

Security

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

SecurityTxt

SecurityTxt

Scroll for all 7

Operate 3

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

Deprecation

Deprecation

Commercial 4

Pricing, plans, and the legal terms of use

Plans

Pricing

TermsOfService

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: consensys
name: Consensys
description: Consensys is a blockchain and Web3 software company founded by Ethereum co-founder Joseph Lubin that builds core
  Ethereum infrastructure and developer tooling for the decentralized web. Its product suite includes MetaMask (the self-custodial
  wallet and MetaMask Developer / Connect SDK), Infura (managed, high-availability JSON-RPC blockchain node APIs, IPFS, and
  a Gas API across Ethereum and 40+ EVM networks), Linea (a zkEVM Layer 2 network), Besu and Teku (execution and consensus
  clients), and Diligence/MythX smart-contract security tooling. Developers use Infura's API-key-authenticated JSON-RPC 2.0
  endpoints to read and broadcast to Ethereum, Base, Arbitrum, Optimism, Polygon, Linea and more without operating their own
  nodes.
url: https://raw.githubusercontent.com/api-evangelist/consensys/refs/heads/main/apis.yml
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:
  - authentication
  - security
  - sandbox
  generated: '2026-09-03'
  method: derived
image: https://images.ctfassets.net/gjyjx7gst9lo/KSIfy6249SncAzulCYpbk/64a8d62db48e733cb7705247d6d70953/Consensys_is_building_the_era_of_decentralized_finance.png
x-type: company
x-source: vc-portfolio
x-backed-by:
- electric-capital
- softbank-vision-fund
x-tier: enriched
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-18'
tags:
- Company
- Infrastructure
- Blockchain
- Ethereum
- Web3
- Developer Tools
- JSON-RPC
- Node Infrastructure
- Wallets
- Layer 2
tags_raw:
- Company
- Infrastructure
- Blockchain
- Ethereum
- Web3
- Developer Tools
- JSON-RPC
- Node Infrastructure
- Wallet
- Layer 2
apis:
- name: Infura Web3 API
  description: Infura's managed Web3 API surface — JSON-RPC 2.0 access to Ethereum and 40+ EVM networks (Base, Arbitrum, Optimism,
    Polygon, Linea, and more), plus IPFS and a Gas API. Authenticated with an API key embedded in the endpoint path.
  humanURL: https://docs.infura.io/
  baseURL: https://mainnet.infura.io/v3/
  tags:
  - Blockchain
  - Ethereum
  - JSON-RPC
  - Web3
  properties:
  - type: Documentation
    url: https://docs.infura.io/
  - type: APIReference
    url: https://docs.infura.io/reference
  - type: GettingStarted
    url: https://docs.infura.io/get-started/infura
  - type: Authentication
    url: authentication/consensys-authentication.yml
  - type: Conventions
    url: conventions/consensys-conventions.yml
  - type: ErrorCatalog
    url: errors/consensys-problem-types.yml
  - type: Sandbox
    url: sandbox/consensys-sandbox.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Plans
  url: plans/consensys-plans-pricing.yml
- type: Website
  url: https://consensys.io/
- type: DeveloperPortal
  url: https://developer.metamask.io/
- type: Documentation
  url: https://docs.infura.io/
- type: APIReference
  url: https://docs.infura.io/reference
- type: GettingStarted
  url: https://docs.infura.io/get-started/infura
- type: Support
  url: https://support.metamask.io/
- type: Blog
  url: https://consensys.io/blog
- type: GitHubOrganization
  url: https://github.com/Consensys
- type: Pricing
  url: https://www.infura.io/pricing
- type: SignUp
  url: https://app.infura.io/register
- type: TermsOfService
  url: https://consensys.io/terms-of-use
- type: PrivacyPolicy
  url: https://consensys.io/privacy-notice
- type: StatusPage
  url: https://status.infura.io/
- type: Packages
  url: packages/consensys-packages.yml
- type: SDKs
  url: packages/consensys-packages.yml
- type: Authentication
  url: authentication/consensys-authentication.yml
- type: Conventions
  url: conventions/consensys-conventions.yml
- type: ErrorCatalog
  url: errors/consensys-problem-types.yml
- type: Lifecycle
  url: lifecycle/consensys-lifecycle.yml
- type: Deprecation
  url: lifecycle/consensys-lifecycle.yml
- type: Conformance
  url: conformance/consensys-conformance.yml
- type: Compliance
  url: https://trust.consensys.io/
- type: TrustCenter
  url: security/consensys-trust-center.yml
- type: Security
  url: https://consensys.io/security/
- type: VulnerabilityDisclosure
  url: security/consensys-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/consensys-domain-security.yml
- type: Sandbox
  url: sandbox/consensys-sandbox.yml
- type: WellKnown
  url: well-known/consensys-well-known.yml
- type: SecurityTxt
  url: well-known/consensys-security.txt
- type: LLMsTxt
  url: llms/consensys-llms.txt
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Consensys API — frequently asked questions

Does Consensys have an API?

Yes. APIs.io lists 1 API from Consensys, including Infura Web3 API.

How do I authenticate with the Consensys API?

Consensys uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Consensys Authentication.

How much does the Consensys API cost?

APIs.io lists 5 pricing plans for Consensys, with each plan's price, limits and inclusions under Pricing Plans on this page.

Is the Consensys API ready for AI agents?

Consensys has a Kin Score of 50.1 out of 100 (developing) and an Agent Readiness score of 5.4 (agent-aware), scored by API Evangelist on 2026-10-31.

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/consensys"

All providers

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

Every operation they expose

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

How their score was established

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

GitHub Google LinkedIn

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