# Paylog MPP Spending History

> Paylog MPP Spending History is a paid API for AI agents from www.paylog.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Returns a breakdown of on-chain spending history across MPP (micropayment protocol) services for a given wallet address and date range

## Facts

- Endpoint: POST https://www.paylog.dev/api/v1/x402/services
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/paylog-mpp-spending-history-9b4ef4fc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ncbx7I-cWP__oKtSErJbn

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 paylog-mpp-spending-history-9b4ef4fc -d '<json body>'
```

Example prompt: Show me a breakdown of my x402 MPP spending for wallet 0xAbC123...def456 from January 1 to January 31, 2025 — I want to see which services I paid and what assets were used.

## When to prefer this

Use this endpoint when you need to audit or review on-chain micropayment spending tied to a specific wallet address across x402/MPP services. It is the only dedicated endpoint for retrieving per-service spending breakdowns from on-chain payment history in the x402 ecosystem. Prefer this over general blockchain explorers when you want structured, service-labeled spend data rather than raw transaction logs.

## Known failure modes

- Invalid or malformed wallet address returns an error or empty results
- Date range too broad may result in slow response or truncated results
- Wallet with no MPP transaction history returns count:0 and empty services array
- Unsupported network or chain ID may yield partial results
- Missing required parameters (wallet address or date range) returns a 400 or validation error

## How this service works

x402 service registry

## Output

Returns a JSON object with a count of services found, a timestamp of when the data was last updated, and an array of service objects each containing the service URL, name, payment asset, recipient wallet address (payTo), network identifier (e.g. eip155:8453 for Base), and a description of the service.

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "updated_at",
  "count",
  "services"
 ],
 "properties": {
  "count": {
   "type": "integer",
   "example": 105
  },
  "services": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "url": {
      "type": "string"
     },
     "name": {
      "type": "string"
     },
     "asset": {
      "type": "string"
     },
     "payTo": {
      "type": "string"
     },
     "network": {
      "type": "string",
      "example": "eip155:8453"
     },
     "description": {
      "type": "string"
     }
    }
   }
  },
  "updated_at": {
   "type": "string",
   "format": "date-time"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/paylog-mpp-spending-history-9b4ef4fc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.paylog.dev](https://www.zero.xyz/host/www.paylog.dev/llms.txt)