Base smart contract due diligence
● LiveVerificationx402-hosting.com
Base mainnet contract due-diligence check: bytecode, Sourcify verification, EIP-1967 proxy slots, ERC interfaces, token metadata, owner. Paid results include a UTC timestamp and the settlement transaction. 0.01 USDC on Base via x402 v2.
- Price
- $0.01
- Asked in its payment challenge
- Chain
- Base
- Paid in
- USDC
- Live
- 3 of 3 checks
Endpoint
Base mainnet contract due-diligence check: bytecode presence/hash, Sourcify verification status, EIP-1967 proxy slots, ERC-165/721/1155/2981 interface support, token name/symbol/decimals/totalSupply, owner(). Live reads at request time. $0.01 asked in its payment challenge on 18 Nov 2026
- addressquery, required0x9d2aC6efE086631DA94DF08E37563CdA5dD288F60x-prefixed Base mainnet contract address (20 bytes)
curl -i 'https://app-00c89dcdfe54831bf106.x402-hosting.com/v1/base/contract-check?address=0x9d2aC6efE086631DA94DF08E37563CdA5dD288F6'
Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/app-00c89dcdfe54831bf106.x402-hosting.com
Recent checks
- Median response
- 1136 ms
- Last checked
- 18 Nov, 03:20 UTC
Our probes look for a payment challenge. They don't test payment or delivery.
All 3 checks
| When (UTC) | Result | HTTP | Response |
|---|---|---|---|
| 18 Nov, 03:20 UTC | Live | 402 | 1464ms |
| 16 Nov, 15:24 UTC | Live | 402 | 1136ms |
| 16 Nov, 12:25 UTC | Live | 402 | 736ms |
Questions
Did our last probe detect a payment challenge?
At our last probe on 18 Nov, 03:20 UTC, it returned HTTP 402 or another detected payment-challenge signal.
What payment terms does ReefScout Base Contract Check advertise?
The listing advertises x402, Base and USDC. Check the seller's current payment challenge and authentication requirements before paying.
Something wrong on this page? Tell us.