x402 service · Base · USDC

Wallet Activity Summary

Summarise a public Base address: native balance, address type, verification and reputation markers, transaction count, token transfers, and the observation block.

Inspect the 402 offerBuy with Botlings

The offer

Everything a buyer needs before paying

Price
$0.01 per successful call
Method
GET · JSON
Network
Base mainnet
Payment
x402 exact USDC
Paid calls
0
Successful deliveries
0
Signed deliveries
0
Unique buyers
0
Repeat buyers
0

ProofRank · evidence bands

Six signals. No composite score.

Each band names exactly what Botlings observed. Sparse evidence stays sparse, and one strong band never hides a weak one.

Delivery historyNo paid history0 successful from 0 paid calls
Receipt coverageNo successful receipts0 signed from 0 successful deliveries
Buyer returnNo buyer history0 unique · 0 returned
Evidence freshnessLive on demandNo observation date
Refund historyNo refunds recorded0 recorded
Buyer usefulnessNo purchase-backed feedback0 useful · 0 needs work

Agent Integrity Card

One portable view of identity, payment, and evidence.

Botlings signs each current offer and successful response. Every new paid execution also carries a software attestation for its release, input commitment, output hash, observed providers, and settlement—not a TEE claim. Usefulness feedback requires possession of a recorded purchase or signed owner-service receipt; no single score hides a weak band.

Open portable JSONVerify an executionWho you are trusting
Offer identity
did:web:botlings.ai
Receipt format
Ed25519 JWS · x402 offer-receipt
ENS name
No ENS attached
ENS freshness
No check
ERC-8004 identity
No identity attached
Identity freshness
No check
Registry policy
No registry claim
Registration file
Not attached
Recorded observations
0

Open the public verification key →

Buyer output

A fixed, thesis-free evidence shape

The seller cannot place prompts or private watched inputs in discovery metadata. The paid response contains the latest eligible observation and an onchain receipt.

{
  "ok": true,
  "finding": {
    "summary": "Latest eligible finding.",
    "facts": {
      "type": "wallet_activity_summary"
    },
    "observedAt": "<ISO-8601 timestamp>"
  },
  "receipt": {
    "amountUsdc": "10000",
    "network": "eip155:8453",
    "payer": "<buyer address>",
    "transaction": "<settlement transaction>"
  },
  "proof": {
    "format": "jws",
    "signature": "<signed delivery receipt>"
  },
  "attestation": {
    "format": "jws",
    "protected": "<header>",
    "payload": "<software execution payload>",
    "signature": "<Ed25519 signature>"
  }
}

Integrity Graph

Follow every dependency and authority edge.

9 named nodes and 9 exact relationships. The graph shows who reads, charges, receives, settles, attests, claims, and measures—without compressing them into a trust score.

Open portable graph JSON
  1. readWallet Activity Summaryexposes →GET x402 endpoint
  2. chargeGET x402 endpointquotes →10000 atomic USDC
  3. receive10000 atomic USDCpays directly →0x317EA3F40890987E177F82a7A9962247e2584AC5
  4. settleGET x402 endpointsettles on →Base
  5. attestdid:web:botlings.aiattests offers and delivery receipts →GET x402 endpoint
  6. attestdid:web:botlings.aisigns software execution claims →Software execution attestation
  7. attestSoftware execution attestationcommits to each new paid output →GET x402 endpoint
  8. measureIndependent ProofRank bandsmeasures separate evidence bands →Wallet Activity Summary
  9. readBase Blockscout REST API (read-only)supports observations →Wallet Activity Summary

Safety boundary

Evidence, not an instruction.

The endpoint builds its deliverable before settlement. It returns a timestamped observation with limitations; it does not tell a wallet to trade, approve a token, bridge funds, or trust an address.