Checkpoint402 · OpenAPI Overlay 1.0.0

Checkpoint402 API enhancements (API Evangelist)

6 actions 6 updates update extends ../openapi/_original/checkpoint402-com-openapi.yml
Derived by API Evangelist Built from the contracts Checkpoint402 publishes. Checkpoint402 did not publish this file.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-mcp-toolresponses

Targets 6

$.paths['/v1/tx-explain'].get
$.paths['/v1/defi-yields'].get
$.paths['/v1/new-tokens'].get
$.paths['/v1/token-check'].get
$.paths['/v1/company-events'].get
$.paths['/v1/sanctions-screen'].get

OpenAPI Overlay

Raw ↑
overlay: 1.0.0
info:
  title: Checkpoint402 API enhancements (API Evangelist)
  version: 1.0.0
  x-provenance:
    generated: '2026-11-03'
    method: derived
    source: https://checkpoint402.com/docs; mcp/checkpoint402-com-tool-crosswalk.yml
extends: ../openapi/_original/checkpoint402-com-openapi.yml
actions:
- target: $.paths['/v1/tx-explain'].get
  description: Link txExplainer to its MCP tool and describe the x402 handshake
  update:
    x-mcp-tool:
      server: https://api.checkpoint402.com/mcp
      name: explain_transaction
    responses:
      '402':
        description: Payment Required. The unpaid request is answered with a PAYMENT-REQUIRED header stating the exact price, network and receiving
          wallet; repeat the call with a signed USDC transfer authorization in a PAYMENT-SIGNATURE header. Failed requests are not charged (https://checkpoint402.com/docs).
- target: $.paths['/v1/defi-yields'].get
  description: Link defiYields to its MCP tool and describe the x402 handshake
  update:
    x-mcp-tool:
      server: https://api.checkpoint402.com/mcp
      name: find_defi_yields
    responses:
      '402':
        description: Payment Required. The unpaid request is answered with a PAYMENT-REQUIRED header stating the exact price, network and receiving
          wallet; repeat the call with a signed USDC transfer authorization in a PAYMENT-SIGNATURE header. Failed requests are not charged (https://checkpoint402.com/docs).
- target: $.paths['/v1/new-tokens'].get
  description: Link newTokens to its MCP tool and describe the x402 handshake
  update:
    x-mcp-tool:
      server: https://api.checkpoint402.com/mcp
      name: new_token_safety_feed
    responses:
      '402':
        description: Payment Required. The unpaid request is answered with a PAYMENT-REQUIRED header stating the exact price, network and receiving
          wallet; repeat the call with a signed USDC transfer authorization in a PAYMENT-SIGNATURE header. Failed requests are not charged (https://checkpoint402.com/docs).
- target: $.paths['/v1/token-check'].get
  description: Link tokenCheck to its MCP tool and describe the x402 handshake
  update:
    x-mcp-tool:
      server: https://api.checkpoint402.com/mcp
      name: token_safety_check
    responses:
      '402':
        description: Payment Required. The unpaid request is answered with a PAYMENT-REQUIRED header stating the exact price, network and receiving
          wallet; repeat the call with a signed USDC transfer authorization in a PAYMENT-SIGNATURE header. Failed requests are not charged (https://checkpoint402.com/docs).
- target: $.paths['/v1/company-events'].get
  description: Link sec8k to its MCP tool and describe the x402 handshake
  update:
    x-mcp-tool:
      server: https://api.checkpoint402.com/mcp
      name: sec_8k_company_events
    responses:
      '402':
        description: Payment Required. The unpaid request is answered with a PAYMENT-REQUIRED header stating the exact price, network and receiving
          wallet; repeat the call with a signed USDC transfer authorization in a PAYMENT-SIGNATURE header. Failed requests are not charged (https://checkpoint402.com/docs).
- target: $.paths['/v1/sanctions-screen'].get
  description: Link ofacScreen to its MCP tool and describe the x402 handshake
  update:
    x-mcp-tool:
      server: https://api.checkpoint402.com/mcp
      name: ofac_sanctions_screen
    responses:
      '402':
        description: Payment Required. The unpaid request is answered with a PAYMENT-REQUIRED header stating the exact price, network and receiving
          wallet; repeat the call with a signed USDC transfer authorization in a PAYMENT-SIGNATURE header. Failed requests are not charged (https://checkpoint402.com/docs).

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/checkpoint402-com-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.