x402-catalog-history.ai-business-surface.workers.dev
https://x402-catalog-history.ai-business-surface.workers.dev/leiShares a payout wallet with 41 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
Look up a legal entity in the GLEIF register: the official LEI, the legal name, the registered address, the jurisdiction and the registration status in one GET. curl: GET /lei?q=Apple%20Inc (a company name and a 20-character LEI both work: ?q=HWUPKR0MPOU8FGXBT394). Response: {"query":"Apple Inc","count":1,"total_matches":24,"results":[{"lei":"HWUPKR0MPOU8FGXBT394","legal_name":"Apple Inc.","entity_status":"ACTIVE","registration_status":"ISSUED","jurisdiction":"US-CA","legal_address":{"city":"Glendale","region":"US-CA","country":"US","postal_code":"91203"}}],"source":{"name":"GLEIF","api":"https://api.gleif.org/api/v1/lei-records","fetched_at":"…"}}. Every value is read from the GLEIF public API (Global Legal Entity Identifier Foundation) at the moment of the call, and the response carries the API URL and the fetched_at it came from. 0.005 USDC, no account, no key, one GET, one delivery. A purchase is two calls by design: this first call returns 402 with the price and the payment terms, and you then repeat the same request with the PAYMENT-SIGNATURE header to receive the 200 delivery.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 10ms · p95 75msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 10/21/2026, 12:00:00 AM | 100% | 10 | 10ms |
| 10/22/2026, 12:00:00 AM | 100% | 1 | 9ms |
| 10/23/2026, 12:00:00 AM | 100% | 1 | 9ms |
| 10/24/2026, 12:00:00 AM | 100% | 1 | 21ms |
| 10/25/2026, 12:00:00 AM | 100% | 1 | 8ms |
| 10/27/2026, 12:00:00 AM | 100% | 1 | 8ms |
| 10/29/2026, 12:00:00 AM | 100% | 1 | 8ms |
| 10/31/2026, 12:00:00 AM | 100% | 1 | 7ms |
| 11/2/2026, 12:00:00 AM | 100% | 1 | 23ms |
| 11/5/2026, 12:00:00 AM | 100% | 1 | 24ms |
| 11/7/2026, 12:00:00 AM | 100% | 1 | 9ms |
| 11/9/2026, 12:00:00 AM | 100% | 1 | 11ms |
| 11/12/2026, 12:00:00 AM | 100% | 1 | 8ms |
| 11/14/2026, 12:00:00 AM | 100% | 1 | 26ms |
| 11/16/2026, 12:00:00 AM | 100% | 1 | 22ms |
- Availability
- 100
- Latency
- 100
- Security
- 100
- Transparency
- 61
- Activity
- 0
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 48% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- USDC
- Networks
- base
- Facilitator
- self-hosted
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- CloudFlare, Inc.
- Domain registered
- 2019-02-08
- Hosting network
- CLOUDFLARENET
- Hosting country
- —
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.
On-chain activity (base)
Payments per day
last payment 11/15/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 10/21/2026 | 4 | 0.03 | 3 |
| 10/22/2026 | 3 | 0.03 | 2 |
| 10/23/2026 | 3 | 0.02 | 2 |
| 10/25/2026 | 1 | 0.01 | 1 |
| 10/26/2026 | 2 | 0.01 | 2 |
| 10/27/2026 | 2 | 0.02 | 1 |
| 10/28/2026 | 1 | 0.01 | 1 |
| 10/30/2026 | 1 | 0 | 1 |
| 11/1/2026 | 1 | 0.01 | 1 |
| 11/9/2026 | 10 | 0.1 | 1 |
| 11/10/2026 | 10 | 0.1 | 1 |
| 11/15/2026 | 1 | 0 | 1 |
This payout wallet is shared: figures cover all 42 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.
Linked by wallet — likely same operator
On-chain agent identity and the x402 endpoint that shares its settlement wallet.
Response schema
{
"additionalProperties": true,
"description": "One delivery: the paid payload plus the period, coverage and evidence fields this service reports with it.",
"type": "object"
}