# mcpfax-intel /movers — x402 Payment Activity Spike Detector

> mcpfax-intel /movers — x402 Payment Activity Spike Detector is a paid API for AI agents from mcpfax-intel.bowling-anthony.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-20).

Detects sudden daily inflow spikes and first-window large-payer signals across x402 services to surface abrupt changes in payment activity.

## Facts

- Endpoint: GET https://mcpfax-intel.bowling-anthony.workers.dev/movers?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mcpfax-intel-movers-x402-payment-activity-spike-detector-d11d05de
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_WLebc7rTIYtVDIO-8AL8l

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 mcpfax-intel-movers-x402-payment-activity-spike-detector-d11d05de
```

Example prompt: Show me any x402 services that had a sudden spike in daily USDC inflows today, and flag any first-time large payers showing up for the first time — I want the early-warning feed with baseline coverage details.

## When to prefer this

Use this endpoint when you need early-warning signals about abrupt, day-level changes in x402 payment activity — especially sudden inflow spikes or first-appearance large payers — rather than gradual growth trends (use the growth/movers sibling for that) or overall leaderboard rankings. Best when you want anomaly detection rather than cumulative ranking.

## Known failure modes

- Insufficient payment history data results in low baseline coverage fraction, reducing signal reliability
- No spikes detected returns an empty feed (not an error)
- Payment amount thresholds may not surface small-scale but meaningful activity changes
- Data recency lag may mean very recent inflows are not yet reflected
- POST body misconfiguration may return validation errors

## How this service works

Sudden inflow spikes and first-seen large payers, before they show up in a ranking.

## Output

Returns a feed of x402 services that experienced sudden daily inflow spikes, along with strictly qualified first-window large-payer signals. Each result includes the nominal baseline window, the fraction of that window actually covered by data, and the magnitude of the detected spike — letting the caller assess data confidence alongside the signal.

## 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"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mcpfax-intel-movers-x402-payment-activity-spike-detector-d11d05de/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mcpfax-intel.bowling-anthony.workers.dev](https://www.zero.xyz/host/mcpfax-intel.bowling-anthony.workers.dev/llms.txt)