MPP · Tempo
x402 · Base

On-chain spending
history for AI agents.

Pass a wallet address, get a full breakdown of what you spent across MPP and x402 services. No database. Reads directly from Tempo chain and Base via Alchemy.

GET/api/v1/report?wallet=0x…&from=2026-03-01
$0.001 USDC per call · MPP (Tempo)
GET/api/v1/x402/report?wallet=0x…&chain=base
$0.01 USDC per call · x402 (Base mainnet)

Quick Start

Up and running in 3 steps.

1. Install Tempo CLI
curl -L https://tempo.xyz/install | bash
2. Login
tempo wallet login
3. Run
tempo request -L -X GET \
  "https://paylog.dev/api/v1/report?wallet=YOUR_WALLET&from=2026-03-01"
Or use mppx
npx mppx https://paylog.dev/api/v1/report?wallet=YOUR_WALLET&from=2026-03-01

Quick Start · x402 (Base)

Get started with x402 (Base).

1. Install
npm install @x402/fetch @x402/evm @x402/core viem
2. Fetch a report
import { wrapFetchWithPayment } from '@x402/fetch'
import { privateKeyToAccount } from 'viem/accounts'
import { registerExactEvmScheme } from '@x402/evm/exact/client'
import { x402Client } from '@x402/core/client'

const account = privateKeyToAccount(process.env.PRIVATE_KEY)
const client = new x402Client()
registerExactEvmScheme(client, { signer: account })
const fetchWithPayment = wrapFetchWithPayment(fetch, client)

const res = await fetchWithPayment(
  'https://www.paylog.dev/api/v1/x402/report?wallet=YOUR_WALLET&chain=base'
)
const report = await res.json()
console.log(report)
$0.01 USDC per request (Base mainnet) · use chain=all to combine MPP + Base

AI Agents

Call paylog from an AI agent.

Drop one of these prompts into Claude or ChatGPT and the agent will automatically call paylog and return your spending report.

MPPTempo
Use the paylog.dev API to get a spending report for wallet [YOUR_WALLET].
Endpoint: https://www.paylog.dev/api/v1/report
This endpoint requires MPP payment ($0.001 USDC on Tempo).
Use mppx or the Tempo wallet to pay and retrieve the report.
Show me a breakdown of spending by service.
x402Base
Use the paylog.dev API to get a spending report for wallet [YOUR_WALLET].
Endpoint: https://www.paylog.dev/api/v1/x402/report?wallet=[YOUR_WALLET]&chain=base
This endpoint requires x402 payment ($0.01 USDC on Base mainnet).
Use an x402-compatible client to pay and retrieve the report.
Show me total spent, breakdown by service, and daily spending.
x402chain=all (MPP + Base combined)
Use the paylog.dev API to get a combined spending report across MPP and Base.
Endpoint: https://www.paylog.dev/api/v1/x402/report?wallet=[YOUR_WALLET]&chain=all
This endpoint requires x402 payment ($0.01 USDC on Base mainnet).
Show me total spent across all protocols, breakdown by service.

CLI Tool

npx @kakedashi/paylogBeta

Get spending insights directly from the terminal, with local history enrichment for Locus gateway payments.

Install
npx @kakedashi/paylog report --days 7
With Locus service detection
npx @kakedashi/paylog report --days 7 --enrich

--enrich reads your local shell history (~/.zsh_history) and Claude Code logs to identify which services were called through the Locus payment gateway.

Example output
Locus gateway $0.048 4 calls Estimated breakdown: ✓ Brave Search $0.010 (confidence: high) ✓ Perplexity $0.010 (confidence: high) ? DeepSeek $0.020 (confidence: medium) * based on local history correlation
Wallet auto-detected from
1.~/.agentcash/wallet.json
2.~/.mppx/wallet.json
3.~/.tempo/wallet/keys.toml
GitHub: kakedashi3/paylog-cli

Sample Response

See exactly where your money went.

Total spent · Mar 2026
$1.184
across 3 services
Transactions
16
Mar 1 – Mar 23
ServiceSpent (USD)Txns
Anthropic$1.0001
StableEmail$0.0804
Exa / fal / Modal$0.05511
How It Works

Stateless by design.

01
Resolve block range
Converts your from / to dates into Tempo block numbers using the chain's current head.
02
Fetch transfer logs
Pulls USDC transfer events from the Tempo chain via eth_getLogs, filtered by your wallet address.
03
Match & aggregate
Each recipient address is resolved against a registry of 54 known MPP services, then grouped and summed.
Manual

API Reference & CLI Guide

GET /api/v1/report

Returns a full USDC spending breakdown for a wallet address and date range. Reads transfer logs directly from the Tempo chain — no database, no cache. Costs $0.001 USDC per call, paid automatically via MPP.
Parameters
NameRequiredDescription
walletrequiredTempo wallet address (0x…). Must match the paying wallet.
fromrequiredStart date in YYYY-MM-DD format (UTC midnight).
tooptionalEnd date in YYYY-MM-DD format. Defaults to today.
resolveoptionalSet true to enable 1-hop resolution for unknown recipient addresses.
Response fields
FieldTypeDescription
total_spent_usdnumberTotal USDC spent on services and fees (excludes session deposits).
by_servicearraySpending broken down by service, sorted by amount descending. Each entry: name, url, spent, txns.
session_depositsobjectUSDC sent to session escrow contracts (deposited_usd, txns). Not included in total_spent_usd.
network_feesobjectTempo transaction fees (total_usd, txns).
daily_breakdownarraySpending grouped by UTC date. Each entry: date, total_usd, by_service.
tempo request -L -X GET \
  "https://paylog.dev/api/v1/report?wallet=0x…&from=2026-03-01"

GET /api/v1/insights

Analyzes your spending history and returns optimization suggestions — cost savings, usage patterns, and your top service. Uses the same $0.001 USDC MPP billing flow as /api/v1/report.
Parameters
NameRequiredDescription
walletrequiredTempo wallet address (0x…). Must match the paying wallet.
fromrequiredStart date in YYYY-MM-DD format.
tooptionalEnd date in YYYY-MM-DD format. Defaults to today.
Insight types
typeDescriptionExtra fields
cost_optimizationA cheaper alternative exists in the same category (search / LLM / data).service, current_spend, txns, alternative, alternative_price, potential_saving
usage_patternA single service category accounts for ≥50% of your spend.message
top_serviceThe service with the highest spend in the period.service, spend, txns
tempo request -L -X GET \
  "https://paylog.dev/api/v1/insights?wallet=0x…&from=2026-03-01"

GET /api/v1/x402/report

Returns a full x402 USDC spending breakdown for a wallet address on Base mainnet. Fetches all-time transfer history via Alchemy alchemy_getAssetTransfers and resolves recipient addresses against a registry of 104 x402 services. Costs $0.01 USDC per call, paid automatically via x402.
Parameters
NameRequiredDescription
walletrequiredBase wallet address (0x…). Must match the paying wallet.
chainoptionalbase (default): Base only. all: Combine Base + MPP (Tempo).
Endpoints
EndpointProtocolPrice
/api/v1/reportMPP (Tempo)$0.001 USDC
/api/v1/x402/reportx402 (Base)$0.01 USDC
/api/v1/x402/report?chain=allx402 (Base)$0.01 USDC
Response fields (chain=base)
FieldTypeDescription
total_spent_usdnumberTotal USDC spent on Base.
by_servicearraySpending broken down by service, sorted by amount descending. Each entry: name, url, spent, txns.
otherobjectUnresolved addresses — total amount and per-address breakdown.
daily_breakdownarraySpending grouped by UTC date. Each entry: date, total_usd, by_service.
# Base only
GET https://www.paylog.dev/api/v1/x402/report?wallet=0x…&chain=base

# MPP + Base combined
GET https://www.paylog.dev/api/v1/x402/report?wallet=0x…&chain=all

CLI Commands

All commands auto-detect your wallet from ~/.agentcash/wallet.json, ~/.mppx/wallet.json, or ~/.tempo/wallet/keys.toml. Override with --wallet 0x….
CommandDescription
paylog report
--days <n> --from <date> --to <date> --enrich
Show spending report. --days defaults to 7. Add --enrich to identify individual services behind the Locus gateway using local shell and Claude Code history.
paylog insights
--days <n> --from <date>
Show cost optimization tips, usage patterns, and top service for the given period.
paylog walletDisplay the auto-detected wallet address and its source file.
paylog balanceShow Tempo wallet balance. Requires the Tempo CLI to be installed.
# Last 7 days report
npx @kakedashi/paylog report

# With Locus enrichment
npx @kakedashi/paylog report --days 14 --enrich

# Insights for a specific date range
npx @kakedashi/paylog insights --from 2026-03-01

Is your site ready for AI agents?

Check your robots.txt, llms.txt, and .well-known/x402 configuration — and get a score.

Scan your site →

Terms of Use