api.osf-master-server.com
https://api.osf-master-server.com/x402/screen/sanctions/:nameShares a payout wallet with 3 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
Debarment and exclusion screening, not just sanctions: 291,000+ parties on 11 authorities in one call. SAM.gov federal exclusions, HHS OIG healthcare exclusions, World Bank debarment, Federal Reserve enforcement, OFAC SDN and Consolidated, EU, UK, UN, Trade.gov CSL, FBI Wanted. Provable negative: NO_MATCH only when the complete candidate set on all 11 lists was examined, otherwise INCOMPLETE_SCREEN. sha256 receipt. KYB, vendor onboarding, AML, KYC.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 14ms · p95 39msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 7/22/2026, 12:00:00 AM | 100% | 1 | 262ms |
| 7/23/2026, 12:00:00 AM | 100% | 1 | 14ms |
| 7/24/2026, 12:00:00 AM | 100% | 1 | 15ms |
| 7/25/2026, 12:00:00 AM | 100% | 1 | 13ms |
| 7/26/2026, 12:00:00 AM | 100% | 1 | 14ms |
| 7/27/2026, 12:00:00 AM | 100% | 1 | 15ms |
| 7/28/2026, 12:00:00 AM | 100% | 1 | 15ms |
| 7/29/2026, 12:00:00 AM | 100% | 1 | 16ms |
| 7/30/2026, 12:00:00 AM | 100% | 1 | 12ms |
| 7/31/2026, 12:00:00 AM | 100% | 1 | 14ms |
| 8/1/2026, 12:00:00 AM | 100% | 1 | 13ms |
| 8/2/2026, 12:00:00 AM | 100% | 1 | 13ms |
| 8/3/2026, 12:00:00 AM | 100% | 1 | 23ms |
| 8/4/2026, 12:00:00 AM | 100% | 1 | 15ms |
| 8/5/2026, 12:00:00 AM | 100% | 1 | 15ms |
| 8/6/2026, 12:00:00 AM | 100% | 1 | 16ms |
| 8/7/2026, 12:00:00 AM | 100% | 1 | 18ms |
| 8/8/2026, 12:00:00 AM | 100% | 1 | 15ms |
| 8/9/2026, 12:00:00 AM | 100% | 1 | 15ms |
| 8/10/2026, 12:00:00 AM | 100% | 1 | 14ms |
| 8/11/2026, 12:00:00 AM | 100% | 1 | 39ms |
| 8/12/2026, 12:00:00 AM | 100% | 1 | 28ms |
| 8/13/2026, 12:00:00 AM | 100% | 1 | 14ms |
| 8/14/2026, 12:00:00 AM | 100% | 1 | 14ms |
| 8/15/2026, 12:00:00 AM | 100% | 1 | 14ms |
| 8/16/2026, 12:00:00 AM | 100% | 1 | 12ms |
| 8/17/2026, 12:00:00 AM | 100% | 1 | 13ms |
| 8/18/2026, 12:00:00 AM | 100% | 5 | 12ms |
| 8/19/2026, 12:00:00 AM | 100% | 21 | 13ms |
| 8/20/2026, 12:00:00 AM | 100% | 15 | 15ms |
- Availability
- 100
- Latency
- 100
- Security
- 100
- Transparency
- 6
- Activity
- 10
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 100% — 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
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- NameCheap, Inc.
- Domain registered
- 2026-05-20
- Hosting network
- CONSTANT
- 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 8/20/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 7/22/2026 | 14 | 0.64 | 3 |
| 7/23/2026 | 9 | 0.42 | 2 |
| 7/24/2026 | 7 | 0.32 | 2 |
| 7/25/2026 | 34 | 1.62 | 2 |
| 7/26/2026 | 23 | 0.33 | 2 |
| 7/27/2026 | 28 | 1.14 | 2 |
| 7/28/2026 | 8 | 0.3 | 2 |
| 7/29/2026 | 7 | 0.11 | 1 |
| 7/30/2026 | 3 | 0.1 | 1 |
| 7/31/2026 | 4 | 0.15 | 2 |
| 8/1/2026 | 7 | 0.3 | 1 |
| 8/2/2026 | 54 | 2.46 | 1 |
| 8/3/2026 | 22 | 0.95 | 1 |
| 8/4/2026 | 8 | 0.25 | 1 |
| 8/5/2026 | 3 | 0.1 | 1 |
| 8/6/2026 | 3 | 0.1 | 1 |
| 8/7/2026 | 3 | 0.1 | 1 |
| 8/8/2026 | 3 | 0.1 | 1 |
| 8/9/2026 | 3 | 0.1 | 1 |
| 8/10/2026 | 3 | 0.1 | 1 |
| 8/11/2026 | 3 | 0.1 | 1 |
| 8/12/2026 | 3 | 0.1 | 1 |
| 8/13/2026 | 3 | 0.1 | 1 |
| 8/14/2026 | 3 | 0.1 | 1 |
| 8/15/2026 | 3 | 0.1 | 1 |
| 8/16/2026 | 7 | 0.3 | 2 |
| 8/17/2026 | 3 | 0.1 | 1 |
| 8/18/2026 | 3 | 0.1 | 1 |
| 8/19/2026 | 3 | 0.1 | 1 |
| 8/20/2026 | 3 | 0.1 | 1 |
Payout address changed 1 time, last on 7/20/2026
- 0x051A…Af85 → 0x72f6…396c (base) · 7/20/2026
A changed payout address is worth a second look — it can be routine, but it is also how a hijacked listing redirects funds.
This payout wallet is shared: figures cover all 17 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.