Clearhouse

Clearhouse Receipts API

Keys for verifying signed receipts.

Documentation GitHub OpenAPI

Operations 1

GET /.well-known/clearhouse-keys.json Receipt signing keys #

Specifications

⚙

OpenAPI

https://artifacts.apis.io/clearhouse-sh/openapi/clearhouse-sh-receipts-api-openapi.yml

Work with this as data

Every API 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 apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
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 API

curl "https://apis.io/api/v1/apis/clearhouse-sh:clearhouse-sh-receipts-api"

All apis

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

GitHub Google LinkedIn

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

OpenAPI Specification

openapi: 3.2.0
info:
  title: Clearhouse Receipts API
  description: 'One search across every agent registry. Clearhouse crawls the official MCP registry, Glama, Smithery and the x402 Bazaar every six hours, deduplicates across them, and exposes one index.


    No key is required. Responses are JSON. The same index is available to agents natively as an MCP server at `https://mcp.clearhouse.sh/mcp`.


    Receipts issued by Clearhouse verify against the key published at `/.well-known/clearhouse-keys.json`.'
  contact:
    name: Clearhouse
    url: https://clearhouse.sh/
    email: contact@clearhouse.sh
  version: 0.1.0
servers:
- url: https://api.clearhouse.sh
  description: Production
tags:
- name: Receipts
  description: Keys for verifying signed receipts.
paths:
  /.well-known/clearhouse-keys.json:
    get:
      tags:
      - Receipts
      summary: Receipt signing keys
      description: 'Published signing keys. Verifiers MUST pin against this set (by

        key_id) rather than trusting a key delivered alongside a receipt.'
      operationId: wellknown_keys__well_known_clearhouse_keys_json_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties: true
                type: object
                title: Response Wellknown Keys  Well Known Clearhouse Keys Json Get