---
name: agent-revenue-monitor
description: Verify revenue progress across crypto wallets, marketplace invoices, saved payment evidence, and payout thresholds. Use when an AI agent, seller, or operator needs to monitor USD goals, separate confirmed funds from pending rewards, check EVM/Solana wallets, or report whether targets such as $5, $10, or $100 have been reached without double-counting.
---

# Agent Revenue Monitor

Use this skill when an agent, seller, or operator asks to verify revenue progress across crypto wallets, marketplace invoices, and saved payment evidence.

## What This Skill Does

- Checks EVM wallet balances on Base, Polygon, and Ethereum.
- Checks Solana wallet balance.
- Separates confirmed funds from pending, rejected, unpaid, or speculative revenue.
- Reads saved settlement evidence, such as a transfer hash to an exchange wallet.
- Produces a concise JSON evidence snapshot and a human-readable status summary.
- Flags when a target such as USD 5, USD 10, or USD 100 has been met.

## Inputs To Request

- Target amount in USD.
- EVM wallet address, if any.
- Solana wallet address, if any.
- Destination wallet or exchange deposit address for sweeping confirmed funds, if sweeping is in scope.
- Marketplace API keys or exported JSON evidence, if marketplace balances should be counted.
- Counting rules for native tokens, if they differ from live USD estimates.

Never ask for private keys or seed phrases.

## Counting Rules

Count only:

- Confirmed stablecoin balances.
- Confirmed native-token balances when a price source and timestamp are recorded.
- Verified paid invoices.
- Withdrawable platform balances.
- Saved transfer evidence with transaction hash and recipient.

Do not count:

- Pending invoices.
- Accepted but unpaid work.
- Rejected invoices.
- Promised rewards.
- Affiliate clicks without confirmed conversion.
- Tournament or bounty entries before settlement.

## Workflow

1. Load existing monitor configuration and previous evidence, if present.
2. Query wallet balances and marketplace state.
3. Normalize all confirmed amounts to USD.
4. Save a timestamped evidence snapshot.
5. Compare confirmed total against the target.
6. If funds are present and the user has explicitly approved sweeping, transfer only when the balance is confirmed and fees are safe.
7. Report amount, network, transaction hash, and evidence file only when a threshold is met or a transfer is made.

## Output Template

```text
Confirmed total: USD {amount}
Target: USD {target}
Status: {met|not met}

Evidence:
- Wallet: {network/address}
- Transfer hash: {hash if applicable}
- Marketplace invoice: {invoice id/status if applicable}
- Snapshot: {evidence file}

Not counted:
- {pending or rejected item and reason}
```

## Safety Boundaries

- Do not fabricate payments or invoice status.
- Do not mark a goal complete from pending rewards.
- Do not sweep funds unless the destination address is explicitly provided by the operator.
- Do not use social accounts as proof unless the operator specifically provided a generated account for that purpose and the platform terms allow it.
- Prefer quiet monitoring when nothing changed.