OpenZeppelin

OpenZeppelin is a Web3 security platform providing tools for secure smart contract development, deployment, monitoring, and automation. The platform includes OpenZeppelin Contracts (battle-tested Solidity libraries), Defender (a developer security platform for auditing, deploying, and operating blockchain applications), the open-source OpenZeppelin Relayer for transaction relay infrastructure across EVM, Solana, and Stellar networks, and OpenZeppelin Monitor for real-time on-chain activity detection and alerting. Defender is sunsetting on July 1, 2026, with users migrating to the open-source Relayer and Monitor projects.

OpenZeppelin publishes 9 API contracts indexed on the APIs.io network, including Health API, Metrics API, Networks API, and 6 more. Tagged areas include Web3, Smart Contracts, Blockchain, Security, and Ethereum.

The OpenZeppelin catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

OpenZeppelin’s developer surface includes authentication, documentation, GitHub presence, engineering blog, product news, status page, signup flow, and 22 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

52.8/100 developing ▬ flat Agent 33/100 agent ready Front door AI 4/6 moderate Heartbeat 98/100 alive open core · AGPL-3.0 Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemiumSelf serve⚡ Free to try

1 published contract

Web3 Smart Contracts Blockchain Security Ethereum DeFi SolidityRelayerMonitoring Auditing

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Blockchain & Digital Assets

AE-240

Signers

POST /api/v1/signers

Kin Score

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

Composite quality — 52.8/100 · developing

Contract Quality 8.7 / 16

Developer Ergonomics 6.8 / 13

Access Clarity 6.5 / 13

Operational Transparency 3.3 / 8

Contract Governance 0.8 / 8

Discoverability 3.8 / 7

Regulatory Posture 4.4 / 15

Open Source Surface 10.0 / 10

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 33/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 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 Horizontal (data, software, accessibility, platform) 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.

Open Source Surface applies to this provider. This product is open source and we read its repository directly, so Open Source Surface carries 10 points of the composite. It is scored from what the repository actually publishes — a security policy, a contribution guide, a release history, a code of conduct — read live from the provider rather than inferred from our own catalog pointers. This facet adds; nothing was taken away to make room for it. An open-source project is not excused from the commercial facets, because exemption would strip it of the points it does earn. If we have the wrong repository, or this product is not open source, say so on your provider repo and we will drop the facet rather than have you publish against it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 65 points between them, because both conditional facets apply and carry 35 points together. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 65% 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/openzeppelin/"><img src="https://apis.io/badge/openzeppelin/card.svg" alt="OpenZeppelin 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):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
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
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks

6 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 53.4 — up to +11.7 composite points
Contract Governance scores 9.8 — up to +10.8 composite points
Access Clarity scores 50.0 — up to +10.0 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/openzeppelin/apis.yml: open an issue on github.com/api-evangelist/openzeppelin 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
LF Decentralized Trust (Hyperledger) Members and Projects (enterprise blockchain, digital identity, CBDC)	standard	17.2 (thin)	-	-

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 1

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.

OpenAPI

measured — observed by APIs.io (published)

APIs 9

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

OpenZeppelin Monitor API

OpenZeppelin Monitor is an open-source blockchain monitoring service that watches for specific on-chain activities and triggers notifications based on configurable conditions. I...

OpenZeppelin Contracts API Reference

The OpenZeppelin Contracts library provides a comprehensive collection of modular, reusable, and secure Solidity smart contracts for building decentralized applications. The API...

OpenZeppelin Health API

Health is responsible for showing the health of the relayers.

OpenZeppelin Metrics API

Metrics are responsible for showing the metrics related to the relayers.

OpenZeppelin Networks API

Networks represent blockchain network configurations including RPC endpoints and network-specific settings.

OpenZeppelin Notifications API

Notifications are responsible for showing the notifications related to the relayers.

OpenZeppelin Plugins API

Plugins are TypeScript functions that can be used to extend the OpenZeppelin Relayer API functionality.

OpenZeppelin Relayers API

Relayers are the core components of the OpenZeppelin Relayer API. They are responsible for executing transactions on behalf of users and providing a secure and reliable way to i...

OpenZeppelin Signers API

Signers are responsible for signing the transactions related to the relayers.

Scroll for all 9

Open Collections 7

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

OpenZeppelin Relayer Health API

OPEN COLLECTION

OpenZeppelin Relayer Health Metrics API

OPEN COLLECTION

OpenZeppelin Relayer Health Networks API

OPEN COLLECTION

OpenZeppelin Relayer Health Notifications API

OPEN COLLECTION

OpenZeppelin Relayer Health Plugins API

OPEN COLLECTION

OpenZeppelin Relayer Health Relayers API

OPEN COLLECTION

OpenZeppelin Relayer Health Signers API

OPEN COLLECTION

Scroll for all 7

OpenZeppelin API pricing

Not yet checked against OpenZeppelin's own pricing page. Compiled by API Evangelist; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Builder	Free
Professional	—
Enterprise	—
Open Source (Self-Hosted)	Free

Plan details, limits and sources →

Rate limits

Defender API - Standard Rate Limit: 100
Defender Relayer - Transaction Throughput: 50
Defender API - JWT Token Expiry: 60

Compiled by API Evangelist, not yet checked against OpenZeppelin's documentation. All 5 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Plans

4 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Rate Limits

5 limits

RATE LIMITS

Service Levels 1

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

OpenZeppelin

SLA

FinOps 1

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

Finops

FINOPS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Openzeppelin Context

47 classes · 2 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

OpenZeppelin — jsonschema rules

5 rules · 4 warnings 1 info

SPECTRAL

JSON Schema 3

Standalone JSON Schema definitions for this provider's data models.

NotificationResponse

6 properties

JSON SCHEMA

RelayerResponse

12 properties

JSON SCHEMA

TransactionResponse

18 properties

JSON SCHEMA

Examples 3

Example request and response payloads for these APIs.

Create Relayer

4 fields

EXAMPLE

Health Check

4 fields

EXAMPLE

Send Transaction

4 fields

EXAMPLE

Security Posture 3

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

Openzeppelin Authentication

http · 1 scheme

SECURITY

Openzeppelin Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Openzeppelin Trust Center

SOC 2, ISO 27001

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Openzeppelin Agentic Access

43 operations · 22 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

Signup

Signup

Documentation 2

Reference material describing how the API behaves

ContributionGuide

ContributionGuide

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Build 2

SDKs, sample code, and the tooling you integrate with

CodeOfConduct

CodeOfConduct

GitHub

GitHub

Access & Security 5

Authentication, authorization, and security posture

SecurityPolicy

TrustCenter

DomainSecurity

Authentication

Security

Operate 7

Status, limits, changes, and where to get help

RateLimits

IssueTracker

Releases

Forums

OpenSourceStack

Discord

Status

Scroll for all 7

Commercial 5

Pricing, plans, and the legal terms of use

Plans

FinOps

License

TermsOfService

PrivacyPolicy

Company 5

The organization behind the API

Website

Blog

News

Twitter

LinkedIn

Other 1

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Source (apis.yml)

name: OpenZeppelin
description: 'OpenZeppelin is a Web3 security platform providing tools for secure smart contract development, deployment,
  monitoring, and automation. The platform includes OpenZeppelin Contracts (battle-tested Solidity libraries), Defender (a
  developer security platform for auditing, deploying, and operating blockchain applications), the open-source OpenZeppelin
  Relayer for transaction relay infrastructure across EVM, Solana, and Stellar networks, and OpenZeppelin Monitor for real-time
  on-chain activity detection and alerting. Defender is sunsetting on July 1, 2026, with users migrating to the open-source
  Relayer and Monitor projects.

  '
deliveryModel:
  model: open-core
  license: AGPL-3.0
  open_source: true
  commercial: true
  callable_host: true
  label: Open core · an OSS project plus a commercial hosted product
  confidence: high
  source:
  - license
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Freemium · Self-serve signup
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://www.openzeppelin.com/hubfs/openzeppelin-logo.png
tags:
- Web3
- Smart Contracts
- Blockchain
- Security
- Ethereum
- DeFi
- Solidity
- Relayer
- Monitoring
- Auditing
created: '2026-06-13'
modified: '2026-06-13'
url: https://raw.githubusercontent.com/api-evangelist/openzeppelin/refs/heads/main/apis.yml
specificationVersion: '0.23'
apis:
- name: OpenZeppelin Monitor API
  description: 'OpenZeppelin Monitor is an open-source blockchain monitoring service that watches for specific on-chain activities
    and triggers notifications based on configurable conditions. It supports real-time monitoring of EVM-compatible networks,
    Solana, and Stellar with flexible match conditions on functions, events, and transactions. Notification channels include
    Slack, Discord, Email, Telegram, Webhooks, and custom scripts. Configurable via JSON files with cron-based scheduling
    and optional metrics server on port 8081.

    '
  image: https://www.openzeppelin.com/hubfs/openzeppelin-logo.png
  humanURL: https://docs.openzeppelin.com/monitor
  baseURL: http://localhost:8081
  tags:
  - Monitors
  - Blockchain
  - Alerts
  - Event
  - Smart Contracts
  - Notification
  - Open Source
  - Onchain
  tags_raw:
  - Monitor
  - Blockchain
  - Alerts
  - Events
  - Smart Contracts
  - Notifications
  - Open Source
  - On-chain
  - Open-Source
  properties:
  - type: Documentation
    url: https://docs.openzeppelin.com/monitor
  - type: GettingStarted
    url: https://docs.openzeppelin.com/monitor/quickstart
  - type: GitHubRepository
    url: https://github.com/OpenZeppelin/openzeppelin-monitor
  - type: Plans
    url: plans/plans.yml
  - type: RateLimits
    url: rate-limits/rate-limits.yml
  - type: FinOps
    url: finops/finops.yml
  contact:
  - FN: OpenZeppelin Community
    url: https://github.com/OpenZeppelin/openzeppelin-monitor/issues
    email: ''
- name: OpenZeppelin Contracts API Reference
  description: 'The OpenZeppelin Contracts library provides a comprehensive collection of modular, reusable, and secure Solidity
    smart contracts for building decentralized applications. The API reference covers ERC token standards (ERC-20, ERC-721,
    ERC-1155), access control, governance, security utilities (reentrancy guards, pausable), upgradeable proxy patterns, and
    cryptographic primitives. Used by thousands of blockchain projects as the industry standard for secure smart contract
    development.

    '
  image: https://www.openzeppelin.com/hubfs/openzeppelin-logo.png
  humanURL: https://docs.openzeppelin.com/contracts
  baseURL: https://docs.openzeppelin.com/contracts
  tags:
  - Smart Contracts
  - Solidity
  - ERC-20
  - ERC-721
  - ERC-1155
  - Governance
  - Security
  - Open Source
  tags_raw:
  - Smart Contracts
  - Solidity
  - ERC-20
  - ERC-721
  - ERC-1155
  - Governance
  - Security
  - Open Source
  - Open-Source
  properties:
  - type: Documentation
    url: https://docs.openzeppelin.com/contracts
  - type: APIReference
    url: https://docs.openzeppelin.com/contracts/5.x/api/access
  - type: GitHubRepository
    url: https://github.com/OpenZeppelin/openzeppelin-contracts
  - type: NPMPackage
    url: https://www.npmjs.com/package/@openzeppelin/contracts
  - type: Plans
    url: plans/plans.yml
  - type: RateLimits
    url: rate-limits/rate-limits.yml
  - type: FinOps
    url: finops/finops.yml
  contact:
  - FN: OpenZeppelin Community
    url: https://forum.openzeppelin.com/
    email: ''
- aid: openzeppelin:openzeppelin-health-api
  name: OpenZeppelin Health API
  description: Health is responsible for showing the health of the relayers.
  humanURL: https://docs.openzeppelin.com/defender/sdk
  baseURL: https://defender-api.openzeppelin.com/v2
  tags:
  - Health
  properties:
  - type: OpenAPI
    url: openapi/openzeppelin-health-api-openapi.yml
  - type: Documentation
    url: https://docs.openzeppelin.com/defender/sdk
  - type: Authentication
    url: https://docs.openzeppelin.com/defender/settings
  - type: SDKs
    url: https://www.npmjs.com/package/@openzeppelin/defender-sdk
  - type: GitHubRepository
    url: https://github.com/OpenZeppelin/defender-sdk
  - type: ChangeLog
    url: https://docs.openzeppelin.com/defender
  - type: Plans
    url: plans/plans.yml
  - type: RateLimits
    url: rate-limits/rate-limits.yml
  - type: FinOps
    url: finops/finops.yml
  - type: Documentation
    url: https://docs.openzeppelin.com/relayer
  - type: OpenAPISpec
    url: https://raw.githubusercontent.com/api-evangelist/openzeppelin/main/openapi/openzeppelin-relayer-openapi.json
  - type: GitHubRepository
    url: https://github.com/OpenZeppelin/openzeppelin-relayer
  - type: SDKs
    url: https://github.com/OpenZeppelin/openzeppelin-relayer-sdk
  - type: Configuration
    url: https://docs.openzeppelin.com/relayer/configuration
- aid: openzeppelin:openzeppelin-metrics-api
  name: OpenZeppelin Metrics API
  description: Metrics are responsible for showing the metrics related to the relayers.
  humanURL: https://docs.openzeppelin.com/defender/sdk
  baseURL: https://defender-api.openzeppelin.com/v2
  tags:
  - Metrics
  properties:
  - type: OpenAPI
    url: openapi/openzeppelin-metrics-api-openapi.yml
  - type: Documentation
    url: https://docs.openzeppelin.com/defender/sdk
  - type: Authentication
    url: https://docs.openzeppelin.com/defender/settings
  - type: SDKs
    url: https://www.npmjs.com/package/@openzeppelin/defender-sdk
  - type: GitHubRepository
    url: https://github.com/OpenZeppelin/defender-sdk
  - type: ChangeLog
    url: https://docs.openzeppelin.com/defender
  - type: Plans
    url: plans/plans.yml
  - type: RateLimits
    url: rate-limits/rate-limits.yml
  - type: FinOps
    url: finops/finops.yml
  - type: Documentation
    url: https://docs.openzeppelin.com/relayer
  - type: OpenAPISpec
    url: https://raw.githubusercontent.com/api-evangelist/openzeppelin/main/openapi/openzeppelin-relayer-openapi.json
  - type: GitHubRepository
    url: https://github.com/OpenZeppelin/openzeppelin-relayer
  - type: SDKs
    url: https://github.com/OpenZeppelin/openzeppelin-relayer-sdk
  - type: Configuration
    url: https://docs.openzeppelin.com/relayer/configuration
- aid: openzeppelin:openzeppelin-networks-api
  name: OpenZeppelin Networks API
  description: Networks represent blockchain network configurations including RPC endpoints and network-specific settings.
  humanURL: https://docs.openzeppelin.com/defender/sdk
  baseURL: https://defender-api.openzeppelin.com/v2
  tags:
  - Networks
  properties:
  - type: OpenAPI
    url: openapi/openzeppelin-networks-api-openapi.yml
  - type: Documentation
    url: https://docs.openzeppelin.com/defender/sdk
  - type: Authentication
    url: https://docs.openzeppelin.com/defender/settings
  - type: SDKs
    url: https://www.npmjs.com/package/@openzeppelin/defender-sdk
  - type: GitHubRepository
    url: https://github.com/OpenZeppelin/defender-sdk
  - type: ChangeLog
    url: https://docs.openzeppelin.com/defender
  - type: Plans
    url: plans/plans.yml
  - type: RateLimits
    url: rate-limits/rate-limits.yml
  - type: FinOps
    url: finops/finops.yml
  - type: Documentation
    url: https://docs.openzeppelin.com/relayer
  - type: OpenAPISpec
    url: https://raw.githubusercontent.com/api-evangelist/openzeppelin/main/openapi/openzeppelin-relayer-openapi.json
  - type: GitHubRepository
    url: https://github.com/OpenZeppelin/openzeppelin-relayer
  - type: SDKs
    url: https://github.com/OpenZeppelin/openzeppelin-relayer-sdk
  - type: Configuration
    url: https://docs.openzeppelin.com/relayer/configuration
- aid: openzeppelin:openzeppelin-notifications-api
  name: OpenZeppelin Notifications API
  description: Notifications are responsible for showing the notifications related to the relayers.
  humanURL: https://docs.openzeppelin.com/defender/sdk
  baseURL: https://defender-api.openzeppelin.com/v2
  tags:
  - Notification
  tags_raw:
  - Notifications
  properties:
  - type: OpenAPI
    url: openapi/openzeppelin-notifications-api-openapi.yml
  - type: Documentation
    url: https://docs.openzeppelin.com/defender/sdk
  - type: Authentication
    url: https://docs.openzeppelin.com/defender/settings
  - type: SDKs
    url: https://www.npmjs.com/package/@openzeppelin/defender-sdk
  - type: GitHubRepository
    url: https://github.com/OpenZeppelin/defender-sdk
  - type: ChangeLog
    url: https://docs.openzeppelin.com/defender
  - type: Plans
    url: plans/plans.yml
  - type: RateLimits
    url: rate-limits/rate-limits.yml
  - type: FinOps
    url: finops/finops.yml
  - type: Documentation
    url: https://docs.openzeppelin.com/relayer
  - type: OpenAPISpec
    url: https://raw.githubusercontent.com/api-evangelist/openzeppelin/main/openapi/openzeppelin-relayer-openapi.json
  - type: GitHubRepository
    url: https://github.com/OpenZeppelin/openzeppelin-relayer
  - type: SDKs
    url: https://github.com/OpenZeppelin/openzeppelin-relayer-sdk
  - type: Configuration
    url: https://docs.openzeppelin.com/relayer/configuration
- aid: openzeppelin:openzeppelin-plugins-api
  name: OpenZeppelin Plugins API
  description: Plugins are TypeScript functions that can be used to extend the OpenZeppelin Relayer API functionality.
  humanURL: https://docs.openzeppelin.com/defender/sdk
  baseURL: https://defender-api.openzeppelin.com/v2
  tags:
  - Plugins
  properties:
  - type: OpenAPI
    url: openapi/openzeppelin-plugins-api-openapi.yml
  - type: Documentation
    url: https://docs.openzeppelin.com/defender/sdk
  - type: Authentication
    url: https://docs.openzeppelin.com/defender/settings
  - type: SDKs
    url: https://www.npmjs.com/package/@openzeppelin/defender-sdk
  - type: GitHubRepository
    url: https://github.com/OpenZeppelin/defender-sdk
  - type: ChangeLog
    url: https://docs.openzeppelin.com/defender
  - type: Plans
    url: plans/plans.yml
  - type: RateLimits
    url: rate-limits/rate-limits.yml
  - type: FinOps
    url: finops/finops.yml
  - type: Documentation
    url: https://docs.openzeppelin.com/relayer
  - type: OpenAPISpec
    url: https://raw.githubusercontent.com/api-evangelist/openzeppelin/main/openapi/openzeppelin-relayer-openapi.json
  - type: GitHubRepository
    url: https://github.com/OpenZeppelin/openzeppelin-relayer
  - type: SDKs
    url: https://github.com/OpenZeppelin/openzeppelin-relayer-sdk
  - type: Configuration
    url: https://docs.openzeppelin.com/relayer/configuration
- aid: openzeppelin:openzeppelin-relayers-api
  name: OpenZeppelin Relayers API
  description: Relayers are the core components of the OpenZeppelin Relayer API. They are responsible for executing transactions
    on behalf of users and providing a secure and reliable way to interact with the blockchain.
  humanURL: https://docs.openzeppelin.com/defender/sdk
  baseURL: https://defender-api.openzeppelin.com/v2
  tags:
  - Relayers
  properties:
  - type: OpenAPI
    url: openapi/openzeppelin-relayers-api-openapi.yml
  - type: Documentation
    url: https://docs.openzeppelin.com/defender/sdk
  - type: Authentication
    url: https://docs.openzeppelin.com/defender/settings
  - type: SDKs
    url: https://www.npmjs.com/package/@openzeppelin/defender-sdk
  - type: GitHubRepository
    url: https://github.com/OpenZeppelin/defender-sdk
  - type: ChangeLog
    url: https://docs.openzeppelin.com/defender
  - type: Plans
    url: plans/plans.yml
  - type: RateLimits
    url: rate-limits/rate-limits.yml
  - type: FinOps
    url: finops/finops.yml
  - type: Documentation
    url: https://docs.openzeppelin.com/relayer
  - type: OpenAPISpec
    url: https://raw.githubusercontent.com/api-evangelist/openzeppelin/main/openapi/openzeppelin-relayer-openapi.json
  - type: GitHubRepository
    url: https://github.com/OpenZeppelin/openzeppelin-relayer
  - type: SDKs
    url: https://github.com/OpenZeppelin/openzeppelin-relayer-sdk
  - type: Configuration
    url: https://docs.openzeppelin.com/relayer/configuration
- aid: openzeppelin:openzeppelin-signers-api
  name: OpenZeppelin Signers API
  description: Signers are responsible for signing the transactions related to the relayers.
  humanURL: https://docs.openzeppelin.com/defender/sdk
  baseURL: https://defender-api.openzeppelin.com/v2
  tags:
  - Signers
  properties:
  - type: OpenAPI
    url: openapi/openzeppelin-signers-api-openapi.yml
  - type: Documentation
    url: https://docs.openzeppelin.com/defender/sdk
  - type: Authentication
    url: https://docs.openzeppelin.com/defender/settings
  - type: SDKs
    url: https://www.npmjs.com/package/@openzeppelin/defender-sdk
  - type: GitHubRepository
    url: https://github.com/OpenZeppelin/defender-sdk
  - type: ChangeLog
    url: https://docs.openzeppelin.com/defender
  - type: Plans
    url: plans/plans.yml
  - type: RateLimits
    url: rate-limits/rate-limits.yml
  - type: FinOps
    url: finops/finops.yml
  - type: Documentation
    url: https://docs.openzeppelin.com/relayer
  - type: OpenAPISpec
    url: https://raw.githubusercontent.com/api-evangelist/openzeppelin/main/openapi/openzeppelin-relayer-openapi.json
  - type: GitHubRepository
    url: https://github.com/OpenZeppelin/openzeppelin-relayer
  - type: SDKs
    url: https://github.com/OpenZeppelin/openzeppelin-relayer-sdk
  - type: Configuration
    url: https://docs.openzeppelin.com/relayer/configuration
common:
- type: CapabilityMap
  url: capabilities/openzeppelin-capability-edges.yml
  name: OpenZeppelin Business Capability Map
- type: Plans
  url: plans/plans.yml
- type: RateLimits
  url: rate-limits/rate-limits.yml
- type: FinOps
  url: finops/finops.yml
- type: IssueTracker
  url: https://github.com/OpenZeppelin/openzeppelin-monitor/issues
- type: Releases
  url: https://github.com/OpenZeppelin/openzeppelin-monitor/releases
- type: SecurityPolicy
  url: https://github.com/OpenZeppelin/openzeppelin-monitor/blob/main/SECURITY.md
- type: CodeOfConduct
  url: https://github.com/OpenZeppelin/openzeppelin-monitor/blob/main/CODE_OF_CONDUCT.md
- type: ContributionGuide
  url: https://github.com/OpenZeppelin/openzeppelin-monitor/blob/main/CONTRIBUTING.md
- type: License
  name: AGPL-3.0
  url: https://github.com/OpenZeppelin/openzeppelin-monitor/blob/main/LICENSE
- type: AgenticAccess
  url: agentic-access/openzeppelin-agentic-access.yml
- type: TrustCenter
  url: security/openzeppelin-trust-center.yml
- type: DomainSecurity
  url: security/openzeppelin-domain-security.yml
- type: Authentication
  url: authentication/openzeppelin-authentication.yml
- type: Website
  url: https://www.openzeppelin.com/
- type: Documentation
  url: https://docs.openzeppelin.com/
- type: Forums
  url: https://forum.openzeppelin.com/
- type: GitHub
  url: https://github.com/OpenZeppelin
- type: Blog
  url: https://www.openzeppelin.com/blog
- type: News
  url: https://www.openzeppelin.com/news
- type: OpenSourceStack
  url: https://www.openzeppelin.com/open-source-stack
- type: Security
  url: https://www.openzeppelin.com/security-audits
- type: Twitter
  url: https://twitter.com/OpenZeppelin
- type: Discord
  url: https://discord.openzeppelin.com/
- type: LinkedIn
  url: https://www.linkedin.com/company/openzeppelin/
- type: TermsOfService
  url: https://www.openzeppelin.com/tos
- type: PrivacyPolicy
  url: https://www.openzeppelin.com/privacy
- type: Status
  url: https://status.openzeppelin.com/
- type: Signup
  url: https://defender.openzeppelin.com/
maintainers:
- FN: API Evangelist
  url: https://apievangelist.com
  email: info@apievangelist.com

OpenZeppelin API — frequently asked questions

Does OpenZeppelin have an API?

Yes. APIs.io lists 9 APIs from OpenZeppelin, including OpenZeppelin Monitor API, OpenZeppelin Contracts API Reference and OpenZeppelin Health API, and 6 more.

Is there an OpenAPI specification for the OpenZeppelin API?

Yes. APIs.io indexes 7 OpenAPI specifications for OpenZeppelin, each linked for download from this page.

How do I authenticate with the OpenZeppelin API?

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

How much does the OpenZeppelin API cost?

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

Is the OpenZeppelin API ready for AI agents?

OpenZeppelin has a Kin Score of 52.8 out of 100 (developing) and an Agent Readiness score of 32.5 (agent-ready), 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/openzeppelin"

All providers

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

Every operation they expose

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

How their score was established

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