# x402 Pulse – Payer Wallet Check

> x402 Pulse – Payer Wallet Check is a paid API for AI agents from reactionpulse-production.reactionpulse-x402.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-02).

Looks up an EVM wallet address on Base to verify its USDC balance, ETH balance, transaction count, and ability to pay on the x402 network.

## Facts

- Endpoint: GET https://reactionpulse-production.reactionpulse-x402.workers.dev/v1/x402/payer?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-pulse-payer-wallet-check-8614f107
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1SjuXqlUujyCgXCb4rS1r

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability x402-pulse-payer-wallet-check-8614f107
```

Example prompt: Can you check whether the wallet 0xe0ce8de9d4c3c493acc5da7b3cc5dd0d74f1f140 has enough USDC to pay on x402 — tell me its balance and whether it's a real funded wallet or just a throwaway?

## When to prefer this

Use this endpoint when you need a fast, cheap, live check on whether a specific Base wallet address can pay via x402 — particularly before gating access to a paid service, screening unknown payers, or debugging a payment failure. Prefer this over a full blockchain explorer when you just need the verdict, USDC balance, and basic wallet health in under a second.

## Known failure modes

- Invalid address format (not 0x + 40 hex chars) returns 400 error
- Address not found on Base returns zero balances with empty_throwaway verdict
- RPC node unavailability may cause timeout or 503
- Missing required 'address' query parameter returns 400

## How this service works

x402 Pulse: market intelligence and builder utilities for the x402 economy. What actually sells on x402, demand gaps, per-service traction checks, price benchmarks, payer wallet checks and a client self test, as cheap GET calls answered in under a second with explicit time information. Also on this host, ReactionPulse is an audience reaction and market research simulation for AI agents: it estimates how multiple stakeholder perspectives (customers, skeptical customers, developers, investors, competitors, early adopters, analysts, regulators, the market) would react to a product launch, announcement, price change, decision, news item, hypothesis or proposal, and returns sentiment analysis, objections, positive reactions, failure modes, market implications and recommended fixes. INPUT: JSON body {prompt (required, 8-6000 chars), context? (<=4000 chars), perspectives?[] (e.g. customer, skeptical_customer, developer, investor, competitor, early_adopter), audience?, output_language? (ISO code, default en)}. OUTPUT: strict JSON: overall_sentiment (0-100), positive_probability and negative_probability (0-1), controversy_score (0-100), perspectives[{role, stance, sentiment, headline, reasoning, top_concern, top_appeal}], likely_objections[], likely_positive_reactions[], failure_modes[{description, likelihood}], market_implications[], recommended_adjustments[], key_uncertainties[], confidence (0-1), input_integrity. TIERS: POST /v1/reaction = full analysis, 4-5 perspectives, $0.49 USDC; POST /v1/reaction/quick = 3 perspectives, compact lists, $0.15 USDC. Paid per call via x402 on Base; a free real sample is at GET /v1/example. LATENCY: full 15-30 s, quick 10-25 s (max 90 s; keep client timeouts at 120 s). LIMITATIONS: analytical LLM simulation, not a survey of real people; probabilities are estimates, not calibrated statistics; no web browsing (put relevant facts in context); one subject per call.

## Output

Returns a JSON object with the wallet address, a verdict string (e.g. 'empty_throwaway'), transaction count, ETH balance, USDC balance, a boolean can_pay_usdc flag, a boolean is_contract flag, and a time object showing when the data was fetched from the live Base chain.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "address"
     ],
     "properties": {
      "address": {
       "type": "string",
       "pattern": "^0x[0-9a-fA-F]{40}$",
       "description": "EVM address on Base (0x + 40 hex chars)"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "time": {
   "source": "live Base JSON-RPC, block tag latest",
   "generated_at": "2026-09-22T12:00:00.000Z"
  },
  "address": "0xe0ce8de9d4c3c493acc5da7b3cc5dd0d74f1f140",
  "verdict": "empty_throwaway",
  "tx_count": 0,
  "eth_balance": "0",
  "is_contract": false,
  "can_pay_usdc": false,
  "usdc_balance": "0"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-pulse-payer-wallet-check-8614f107/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from reactionpulse-production.reactionpulse-x402.workers.dev](https://www.zero.xyz/host/reactionpulse-production.reactionpulse-x402.workers.dev/llms.txt)