Overview
| Metric | Value |
|---|---|
| Endpoints | 5,700+ |
| Providers | 400+ |
| Protocols | x402, L402, MPP |
| Scan frequency | Every 6 hours |
| Scoring | EWMA health-weighted (0-100) |
SDK Integration
discover() queries the registry API. No static directory is bundled with the SDK.
Filters
All filters are server-side — the registry handles filtering and pagination.DiscoverOptions
| Field | Type | Default | Description |
|---|---|---|---|
protocol | string | — | Filter by protocol: "x402", "l402", "mpp" |
minScore | number | — | Minimum trust score (0-100) |
category | string | — | Filter by category |
query | string | — | Free-text search (name, URL, description) |
limit | number | 200 | Max results per page |
offset | number | 0 | Pagination offset |
signal | AbortSignal | — | Abort signal for cancellation |
DiscoveredEntry
Each entry returned bydiscover():
CLI
MCP Tool
Theboltzpay_discover MCP tool exposes the same filters:
Custom Registry URL
Point the SDK at a self-hosted or staging registry:https://status.boltzpay.ai
Scoring
Each endpoint receives a trust score from 0 to 100 based on:- Availability — uptime over the last 30 days (EWMA-weighted)
- Response time — latency consistency
- Protocol compliance — correct 402 response format
- Price stability — consistent pricing across scans
- Multi-source verification — confirmation from multiple independent sources (capped bonus)
Next Steps
- Configuration — custom registry URL
- SDK API Reference —
discover()method signature - CLI —
discovercommand flags