# EVM Address Activity Summary API

> EVM Address Activity Summary API is a paid API for AI agents from x402-safe-upgrade-api.onrender.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-11).

Returns a summary of transaction count and token transfer activity for an EVM address over a specified block window on Base or Base Sepolia.

## Facts

- Endpoint: POST https://x402-safe-upgrade-api.onrender.com/v1/address-activity-summary?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-address-activity-summary-api-dfff7b17
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mKNQXb0wqJyogjWc_tC2t

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 evm-address-activity-summary-api-dfff7b17 -d '<json body>'
```

Example prompt: Can you pull the activity summary for 0x1234...abcd on Base mainnet over the last 500 blocks — I want to see how many transactions it's made and how many token transfers came in or out?

## When to prefer this

Choose this endpoint when you need a quick, cost-effective on-chain activity snapshot for a specific EVM address on Base or Base Sepolia without querying a full blockchain explorer. It is ideal for agents performing wallet due diligence, detecting dormant or highly active addresses, or enriching address metadata prior to a transaction or interaction. Prefer this over general-purpose blockchain RPCs when you want a structured summary (transaction count + transfer log breakdown) in a single call.

## Known failure modes

- Invalid or malformed 0x address returns an error response
- Unsupported chain value (not 'base' or 'base-sepolia') causes a validation error
- windowBlocks exceeding 5000 or below 1 is rejected
- Payment not provided or insufficient USDC results in a 402 Payment Required response
- Address with zero activity returns counts of 0 (not an error but may be unexpected)
- Node or indexer unavailability on the specified chain causes a service error

## How this service works

Evidence-backed npm package upgrade decisions for coding agents.

## Output

Returns a JSON object containing the total transaction count for the address within the specified block window, plus a breakdown of incoming and outgoing standard token transfer log counts.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "enum": [
    "base",
    "base-sepolia"
   ],
   "type": "string"
  },
  "address": {
   "type": "string",
   "description": "Public 0x-prefixed EVM address."
  },
  "windowBlocks": {
   "type": "integer",
   "default": 1000,
   "maximum": 5000,
   "minimum": 1
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "transactionCount": "0",
  "standardTransferLogCounts": {
   "incoming": 0,
   "outgoing": 0
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evm-address-activity-summary-api-dfff7b17/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-safe-upgrade-api.onrender.com](https://www.zero.xyz/host/x402-safe-upgrade-api.onrender.com/llms.txt)