large-transaction-monitoring

Reads all incoming ERC-20 transfers of one token to one address within a block or time window and matches them against the receipts you supply. Matching runs first over the transaction hash, which is the strongest link, and otherwise over amount plus payer plus a stated time tolerance; the method used is named for every single match, so a weak match is never mistaken for a strong one. The answer lists matched pairs, receipts without a payment, payments without a receipt, amount mismatches with e

Verify a Base transaction actually did what a counterparty says it did: confirmation depth, success or revert, value, token, sender and recipient. Use it to confirm an inbound payment before releasing goods or data.

Resolve a token symbol or contract address to the canonical Base contract, so an agent swapping or accepting 'USDC' gets the real one. Catches lookalike and impostor contracts sharing a symbol.

Validate Bitcoin-base58 alphabet membership for local address hygiene — call when checking Bitcoin-base58 alphabet membership locally. Use for chain input hygiene without live RPC—adjacent to OneSource-class small chain reads, but static/local only so rights and margin stay clear. Returns deterministic machine-readable JSON for $0.003 USDC via x402 on Base. Execution is first-party, local-only, stateless, and memory-only with no paid upstream, no input retention, and no claim of live chain tip, web search, or media generation. Results are advisory; the caller owns authorization and production controls.

Profile of a Base address before you transact with it: EOA or contract, first and last seen, transaction and counterparty counts, contract-verification status, and any flags raised. Behavioural signals only — they describe activity, not intent.

Paid agent-facing brief on merchant-side adoption decision procedure for card-network-backed crypto settlement standards (Visa/Mastercard/Google/Stripe backed standard vs existing x402 and card rails): fee economics, settlement rails, dispute/chargeback coverage, integration cost, counterparty scope. Blunt decision procedure, not marketing.

Cryptographically SIGNED WALLET TRACK-RECORD attestation (path param: 0x… wallet address; optional query param: window = 7d|30d, default 30d). Returns the wallet's RESOLVED-market-only record — win_rate, Wilson 95% lower bound, edge over entry price, conviction_score, volume, and a verdict (verified_smart_money | positive_edge | no_proven_edge) — as an ed25519-signed envelope verifiable OFFLINE against the SAME published key as /v1/attest. Every other tool shows a self-reported or scraped win rate you must trust; this SIGNS it, so a copy-trading platform, a fund proving a track record to an allocator, or an agent sizing a copy can verify the record without trusting this endpoint. Win rate is computed from resolved markets only (a trade wins when its side equals the market's eventual resolution). 404 (not charged) when the wallet has no resolved trades in the window.

Decision procedure for agents that must provision a payment wallet. Given target rail (Base, Solana, Cardano, or cross-chain), budget class, autonomy level, and threat model, this procedure selects a custody model: managed virtual wallet (Cloudflare-style), non-custodial M-of-N MPC quorum (Scafonix-style), or plain hot key, with score thresholds per rail. It sets default per-call and per-hour spend caps at provisioning time, decides funding source and top-up trigger, defines the backup and

Verifies whether a specific spender address has approval to transfer tokens on behalf of a user on the Base blockchain.

Evaluates whether a transaction can be safely executed on the Base blockchain.

Constructs a safe token swap transaction on the Base blockchain.

Bitcoin address AML/compliance risk score 0-100 with signals

Paid agent-facing brief on merchant-side adoption decision procedure for card-network-backed crypto settlement standards (Visa/Mastercard/Google/Stripe backed standard vs existing x402 and card rails): fee economics, settlement rails, dispute/chargeback coverage, integration cost, counterparty scope. Blunt decision procedure, not marketing.

Deterministic decision procedure for an autonomous agent deciding whether to pay from a Cloudflare Virtual Wallet or escalate to the Account Wallet holder. Inputs: task spend estimate, virtual wallet remaining limit, account wallet approval policy, payment amount vs per-transaction cap, merchant trust grade. Procedure: (1) classify the payment as routine (under virtual limit, known merchant, deterministic deliverable) and pay autonomously, (2) classify as boundary (over 80% of remaining virtual limit, new merchant, first-time rail, or refund-sensitive) and escalate for human authorization, (3) verify the virtual wallet is actually bound to the account wallet by checking the delegation record and issuer signature before trusting it as a payment source, (4) reconcile the virtual wallet ledger against the account wallet after settlement, (5) freeze the virtual wallet when spend anomalies exceed thresholds. Failure modes: unbound virtual wallet impersonation, limit drift between wallet and ledger, account wallet revocation not propagating to the virtual wallet. Output: PAY_AUTONOMOUS / ESCALATE / VERIFY_BOUND / ABORT verdict with evidence. Falsifier: free Cloudflare docs already describing the two-layer design, which this procedure extends with payment-specific thresholds.

SOL spot price via Pyth

Operational procedure for multi-agent fleets sharing one capped virtual wallet: reserving spend before payment, detecting race conditions when two agents claim the same remaining cap, applying priority tiers for arbitration, and reconciling settled, failed, and swept-back funds within the same wallet cycle.

Liquidity Volatility Watchlist by SourceStrand Crypto Workbench Pack. Precomputed crypto liquidity, volatility, data-quality, review-priority, lineage, and limitations for AI agent triage.

Buyer-side MOVE/HOLD decision for ETH liquid staking (Ethereum mainnet) — same contract as the lending decision routes, for ETH staking. Verified per-asset accuracy is free at /accuracy.json; raw on-chain attestations at /track-record.

Solana wallet holdings via Helius DAS

Base Daily: AgentLayer adds Uniswap pool lookup. AgentLayer Wallet v0.1.95 adds Uniswap V3/V4 pool discovery on Base and V3 LP-position inspection before an agent creates, changes, or claims a position.

Comprehensive premium audit of any Base wallet — score + all 18+ identity proofs (Virtuals/Farcaster/CB1/Basename/Clawd/Aerodrome/Morpho/etc.) + token launch history + trader tier + active-rater status + alive endpoint + ERC-8004 feedback + peer receipts. One paid call replaces 8 free ones. Use before paying any significant amount onchain.

Wallet clustering and entity resolution via Neo4j graph analysis. Returns related addresses, common-input heuristic clusters, and known-entity tags.

News Gurus Intel API — dormant/Satoshi-era BTC wallet movement feed: on-chain moves with BTC amount, years dormant and transaction timestamps (public on-chain — no upstream-license restriction). Optional ?limit= (default 25, cap 50). Educational data, not financial advice.

Provides blockchain transaction analysis and tracking for smart money wallet activities and movements.