Build agent dispute evidence API

Package caller-supplied agent and operator records into a chronological evidence timeline for financial disputes. Balance transitions are checked against intervening signed amounts. Conflicting references, unexplained balance changes, and missing records for declared dispute categories are labeled separately from verified supplied facts. No liability outcome is assigned and no compensating transactions are invented.

The Build agent dispute evidence operation is part of the Agent Network Float API on BRAINIAC.software. Package caller-supplied agent and operator records into a chronological evidence timeline for financial disputes. Balance transitions are checked against intervening signed amounts. Conflicting references, unexplained balance changes, and missing records for declared dispute categories are labeled separately from verified supplied facts. No liability outcome is assigned and no compensating transactions are invented. It is exposed as POST /api/v1/agent-networks/agent-dispute-evidence and priced at $0.04 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-supplied agent balances, cash transactions, demand, schedules, replenishment, fee rules, operating costs, dated agreements, commission rules, commission payments, transfer costs, transfer limits, redistribution budgets, float balances, funding costs, idle periods, cost-of-capital rates, outlet operating metrics, denomination systems, outlet capacity constraints, concentration volumes, outlet activity histories, depot and outlet coordinates, vehicle capacities, optional distance matrices, settlement statements, shift handovers, dispute lifecycle events, terminal outages, and agent dispute records processed locally Limitations: Amounts are safe integers in one minor unit. They are not converted between currencies. Cash in and commission increase cash. Cash out and fee decrease cash. An adjustment uses its signed amount. A reversal applies its own amount with the opposite sign of an earlier transaction. The original row stays in the calculation. Every supplied transaction for an agent with a difference is listed. None are dropped as suspicious. A history day with no transactions is skipped, not counted as zero. Weekday averages use only the days that were supplied. When a day has no expected demand, cash out follows that historical average. An outlet with neither is projected flat apart from replenishment. The minimum replenishment is the amount added at the start of the period so the balance stays at the outlet minimum. Terminal fees may be fixed, a basis-point rate, or count tiers. Percent parts use integer floor division. Terminal ranking compares net profit only among terminals that share a currency code. Commission uses the agreement in force on the transaction date. Type-specific rules beat general ones, then the latest effective_from wins. Tiered commission counts transactions under the same agreement in date order. A payment without a transaction id applies FIFO to unpaid expected amounts. Float rebalancing is a proposal only. Transfers are not initiated. Corridors come from transfer_costs; currencies are never mixed. Rebalancing uses successive shortest-path min-cost flow. feasibility explains when shortages remain under the supplied limits and budget. Liquidity funding, replenishment, collection, and transfer fees are actual expenses. Idle capital is an opportunity cost. Rate accruals use floor(balance * rate_bps * days / (10000 * annualization_days)). annualization_days defaults to 365. Outlet benchmarks use only the supplied outlets. Peer groups are category:currency. No industry or market benchmark is invented. When active_days or operating_hours are supplied, ranking uses per-day and per-hour metrics instead of raw totals. Cash denomination planning uses only the supplied denomination system. No currency or note set is assumed. Dispense and change use largest-first greedy composition. Recommended acquisitions are capped by replenishment limits and are not initiated. Capacity allocation uses only caller-supplied locations, intervals, and capacities. No map or demand database is queried. Demand is assigned in demand id order to the eligible outlet with the most remaining capacity, then by outlet id. Concentration uses caller-supplied volumes, values, and revenue only. HHI and top-n ratios carry no invented industry threshold. Outage exposure compares unavailable entities with remaining replacement_capacity from the request. Dormant outlet detection uses only supplied schedules, status records, and transaction dates. Evidence is returned for every classification. Temporary versus permanent inactivity follows inactive_days_threshold and permanent_days_threshold on open days without activity. Replenishment routing uses only supplied coordinates and distances[]. Supplied directed distances override rounded haversine meters. Route construction is local nearest-neighbor plus 2-opt and insertion. No mapping or external solver is called. Settlement reconciliation never confirms an ambiguous match. Amount and fee deltas stay in the supplied currency. Shift handover audits compare expected balances with counts and consecutive handover records only. Failed-transaction dispute assessments never invent a successful payment without a supplied settled fact. Terminal downtime measured_* values come from history; estimated_lost_* values come only from supplied averages. Agent dispute evidence packages label verified supplied facts, inconsistencies, and missing evidence without assigning liability. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Attribute agent float loss, Analyze agent cash shortage, Score terminal profitability, Find commission leakage. Open the group documentation for the full request schema, field notes, and response examples before integrating.