Clearhouse Index API
Search and read the unified registry index.
Search and read the unified registry index.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/clearhouse-sh:clearhouse-sh-index-api"
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.
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.
openapi: 3.2.0
info:
title: Clearhouse Index 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: Index
description: Search and read the unified registry index.
paths:
/v0/stats:
get:
tags:
- Index
summary: Index statistics
description: How many listings are indexed, broken down by source registry, plus how many are unique after deduplication and how many are callable over the network.
operationId: stats_v0_stats_get
responses:
'200':
description: Successful Response
content:
application/json:
schema:
additionalProperties: true
type: object
title: Response Stats V0 Stats Get
/v0/search:
get:
tags:
- Index
summary: Search every registry
description: Full-text search across names and descriptions. Duplicates across registries collapse into one result; `also_listed_on` names the other registries it appears on. Use `remote=1` for services callable right now and `source=x402_bazaar` for pay-per-call only.
operationId: search_v0_search_get
parameters:
- name: q
in: query
required: true
schema:
type: string
minLength: 1
maxLength: 200
title: Q
- name: remote
in: query
required: false
schema:
anyOf:
- type: integer
- type: 'null'
description: 1 = only remotely-callable
title: Remote
description: 1 = only remotely-callable
- name: source
in: query
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: Source
- name: limit
in: query
required: false
schema:
type: integer
maximum: 100
minimum: 1
default: 20
title: Limit
responses:
'200':
description: Successful Response
content:
application/json:
schema:
type: object
additionalProperties: true
title: Response Search V0 Search Get
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
/v0/listing/{listing_id}:
get:
tags:
- Index
summary: One listing
description: Full record for a single listing by its Clearhouse id.
operationId: listing_v0_listing__listing_id__get
parameters:
- name: listing_id
in: path
required: true
schema:
type: integer
title: Listing Id
responses:
'200':
description: Successful Response
content:
application/json:
schema:
type: object
additionalProperties: true
title: Response Listing V0 Listing Listing Id Get
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
components:
schemas:
HTTPValidationError:
properties:
detail:
items:
$ref: '#/components/schemas/ValidationError'
type: array
title: Detail
type: object
title: HTTPValidationError
ValidationError:
properties:
loc:
items:
anyOf:
- type: string
- type: integer
type: array
title: Location
msg:
type: string
title: Message
type:
type: string
title: Error Type
input:
title: Input
ctx:
type: object
title: Context
type: object
required:
- loc
- msg
- type
title: ValidationError