# Heurist Mesh USDC Hourly Pair Activity

> Heurist Mesh USDC Hourly Pair Activity is a paid API for AI agents from mesh.heurist.xyz, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-13).

Reports hourly USDC transfer volumes between two specific wallet addresses, broken down by direction (A→B and B→A), to analyze fund flow intensity between potentially related wallets.

## Facts

- Endpoint: POST https://mesh.heurist.xyz/x402/agents/BaseUSDCForensicsAgent/usdc_hourly_pair_activity
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/heurist-mesh-usdc-hourly-pair-activity-8c50f3dd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Baaw8-2X4W_3Sf6_NLs9Z

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 heurist-mesh-usdc-hourly-pair-activity-8c50f3dd -d '<json body>'
```

Example prompt: Can you show me the hourly USDC transfer activity between wallet 0xAbC123... and 0xDeF456..., broken down by direction, so I can see if they're moving funds back and forth?

## When to prefer this

Use this endpoint when you need to forensically examine USDC transfer patterns between exactly two specific wallet addresses on Base, especially to detect reciprocal flows, measure flow intensity over time, or identify whether two wallets are behaving in a coordinated or related manner. Prefer this over general transaction explorers when you need structured hourly time-series data rather than raw transaction lists.

## Known failure modes

- Invalid or malformed wallet address (not starting with 0x) returns an error
- No transfer history between the two addresses returns empty results
- Addresses with no Base chain USDC activity may return zero or null data
- Network or provider downtime may cause timeout or 5xx errors
- Querying the same address for both A and B may produce unexpected results

## How this service works

Report hourly USDC transfer activity between two specific addresses, showing volume in each direction (A→B and B→A) per hour. Use to analyze flow intensity between suspected related wallets.

## Output

A time-series breakdown of USDC transfers between the two addresses, organized by hour, showing the volume transferred in each direction (address A to address B, and address B to address A) per hour, enabling analysis of flow intensity and potential coordination between the wallets.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "address_a",
  "address_b"
 ],
 "properties": {
  "debug": {
   "type": "boolean",
   "description": "Debug mode flag. ALWAYS use false."
  },
  "address_a": {
   "type": "string",
   "description": "First wallet address starting with 0x"
  },
  "address_b": {
   "type": "string",
   "description": "Second wallet address starting with 0x"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/heurist-mesh-usdc-hourly-pair-activity-8c50f3dd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mesh.heurist.xyz](https://www.zero.xyz/host/mesh.heurist.xyz/llms.txt)
