# Heurist Mesh – USDC Net Counterparties (BaseUSDCForensicsAgent)

> Heurist Mesh – USDC Net Counterparties (BaseUSDCForensicsAgent) 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).

Computes per-counterparty net USDC flow metrics for a wallet, showing whether it is a net payer or receiver relative to each connected address on Base.

## Facts

- Endpoint: POST https://mesh.heurist.xyz/x402/agents/BaseUSDCForensicsAgent/usdc_net_counterparties
- 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-net-counterparties-baseusdcforensicsagent-2aeaea05
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_e_EdLFsUUXI62kdtdtups

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-net-counterparties-baseusdcforensicsagent-2aeaea05 -d '<json body>'
```

Example prompt: Show me the net USDC flow breakdown for wallet 0x1234...abcd on Base — rank all its counterparties by economic importance and flag which ones it's a net payer versus receiver to, returning up to 50 counterparties.

## When to prefer this

Use this endpoint when you need to understand the economic relationships between a specific wallet and all of its USDC counterparties on Base — particularly for forensic analysis, compliance checks, whale tracking, or identifying which addresses are the dominant economic partners of a target wallet. Prefer this over generic transaction history endpoints when the goal is net flow ranking and payer/receiver classification rather than raw transaction lists.

## Known failure modes

- Invalid or malformed wallet address (non-0x prefix or wrong length) returns an error
- Wallet with no USDC transaction history returns empty counterparty list
- Limit parameter set to 0 or negative value may cause unexpected results
- Payment failure (insufficient USDC balance for the $0.005 per-call fee) blocks the request
- Network or upstream indexer downtime causes timeout or 5xx error

## How this service works

Compute per-counterparty net flow metrics showing whether the wallet is a net payer or receiver for each connected address. Use to rank counterparties by economic importance and spot asymmetric relationships.

## Output

A ranked list of counterparties for the given wallet, each with net USDC flow metrics indicating whether the wallet is a net payer or net receiver relative to that address, enabling identification of economically significant and asymmetric relationships.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "address"
 ],
 "properties": {
  "debug": {
   "type": "boolean",
   "description": "Debug mode flag. ALWAYS use false."
  },
  "limit": {
   "type": "integer",
   "description": "Maximum number of counterparties to return (default 100)"
  },
  "address": {
   "type": "string",
   "description": "Wallet address starting with 0x"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/heurist-mesh-usdc-net-counterparties-baseusdcforensicsagent-2aeaea05/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)