x402.fairseal.io
https://x402.fairseal.io/v1/veo/verifyShares a payout wallet with 3 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
Verify AI agent outputs against a VEO-2 schema. Checks structural validity, SHA-256 hash integrity (if content hash is present), and optional cryptographic signature on the output (if proof.provider_signature is present). Returns a verdict with per-check details.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
0.0% avgResponse time
Data table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 8/27/2026, 3:00:00 AM | 0% | 1 | — |
| 8/28/2026, 3:00:00 AM | 0% | 1 | — |
| 8/29/2026, 4:00:00 AM | 0% | 1 | — |
| 8/30/2026, 4:00:00 AM | 0% | 1 | — |
- Availability
- 0
- Latency
- not yet measured
- Security
- 100
- Transparency
- 30
- Activity
- 2
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 8% — 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
- —
- Domain registered
- —
- Hosting network
- —
- 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/30/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 8/1/2026 | 3 | 0 | 1 |
| 8/2/2026 | 1 | 0 | 1 |
| 8/19/2026 | 6 | 0.01 | 1 |
| 8/20/2026 | 2 | 0.01 | 2 |
| 8/21/2026 | 4 | 0.05 | 1 |
| 8/24/2026 | 1 | 0.01 | 1 |
| 8/27/2026 | 9 | 0.06 | 2 |
| 8/28/2026 | 4 | 0.03 | 1 |
| 8/30/2026 | 9 | 0.05 | 2 |
Payout address changed 2 times, last on 8/28/2026
- 0x6323…10dC → 0xBd5e…ce28 (base) · 8/28/2026
- 0x6323…10dC → 0xBd5e…ce28 (base) · 8/28/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 4 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.