# x402 Pulse Client Self-Test

> x402 Pulse Client Self-Test is a paid API for AI agents from reactionpulse-production.reactionpulse-x402.workers.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-02).

Verifies that a client's x402 payment flow is working correctly by confirming payment receipt, server time, and protocol conformance in a single cheap GET call

## Facts

- Endpoint: GET https://reactionpulse-production.reactionpulse-x402.workers.dev/v1/x402/selftest?utm_source=zero.xyz
- Price: $0.002/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-client-self-test-c4dfa762
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CnofgzsHNLdE1Mg81dmMU

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-client-self-test-c4dfa762
```

Example prompt: Run the x402 self-test to confirm my payment client is set up correctly and show me the conformance results, server time, and which wallet address was recognized.

## When to prefer this

Use this endpoint when you need to verify that an x402 client, agent, or wallet integration is correctly set up before running more expensive calls. It is the cheapest and fastest way to confirm end-to-end payment flow, check server time synchronization, and validate protocol conformance on the Base/USDC x402 network. Prefer it over other x402 endpoints when the goal is diagnostic or integration testing rather than fetching market data or running simulations.

## Known failure modes

- Payment not included or malformed — returns 402 Payment Required
- Expired authorization — authorization_seconds_left reaches 0
- Network mismatch — payment on wrong chain not recognized
- Insufficient payment amount — USDC amount below $0.002 threshold
- Conformance failures — passed count less than total indicates protocol issues

## 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: ok (boolean), server_time_utc and authorization_seconds_left under time, a conformance object with total and passed test counts, and verified_payment details including asset (USDC), payer wallet address, network (eip155:8453 / Base), and price_usd paid.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "time": {
   "server_time_utc": "2026-09-22T12:00:00.000Z",
   "authorization_seconds_left": 117
  },
  "conformance": {
   "total": 8,
   "passed": 8
  },
  "verified_payment": {
   "asset": "USDC",
   "payer": "0x4354b2a2301eeeeab9f4d6833644593b514ce324",
   "network": "eip155:8453",
   "price_usd": "0.002"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-pulse-client-self-test-c4dfa762/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)