R2 · OpenAPI Overlay 1.0.0

API Evangelist enhancements for R2 APIs

2 actions 2 updates update extends openapi/r2-openapi.json
Derived by API Evangelist Built from the contracts R2 publishes. R2 did not publish this file.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-enrichedx-apievangelist-providerx-apievangelist-notesx-agent-readiness

Targets 1

$.info

OpenAPI Overlay

Raw ↑
overlay: 1.0.0
info:
  title: API Evangelist enhancements for R2 APIs
  version: 1.0.0
extends: openapi/r2-openapi.json
actions:
- target: $.info
  update:
    x-apievangelist-enriched: '2026-07-20'
    x-apievangelist-provider: r2
    x-apievangelist-notes: >-
      Spec reconstructed from R2's per-operation OpenAPI definitions published on
      the ReadMe developer hub (r2-api-docs.readme.io). Authorization is a
      partner-signed HS256 JWT in the Authorization header. Events are delivered
      as HMAC-SHA256-signed webhooks (see asyncapi/r2-events-webhooks.yml).
- target: $.info
  update:
    x-agent-readiness:
      auth: JWT (apiKey header)
      webhooks: true
      sandbox: true
      idempotency: false

Work with this as data

Every overlay 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 openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay in the catalog.
  • 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 overlay
curl "https://apis.io/api/v1/overlays/r2-openapi-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"

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.

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