record_performance
Record shipment actuals—transit days, on-time, damage, discrepancies—to build a private carrier or supplier scorecard with running KPIs.
Instructions
Log a shipment's REAL outcome into your private supplier/carrier/lane SCORECARD — the tool that makes freight-pulse RECURRING (you feed it, it accumulates a history no single source hands you). Give the SUBJECT (a carrier like 'Maersk', a supplier, or a lane) and the outcome — promised vs actual transit days, on-time, damage, documentary discrepancy, rollover — and it appends the event to your log, PERSISTED SERVER-SIDE per your key, then returns the subject's running KPIs (OTP %, reliability score, damage/discrepancy/roll rates). Pair with get_scorecard to rank and trend your network over time. Links to iter8 (structural carrier intel) — this is the EMPIRICAL counterpart. Honest (regla 7): it's YOUR own log — KPIs reflect only what you record, small samples flagged. PREMIUM: pay per call with x402 (USDC on Base) or a prepaid key.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| subject | Yes | Carrier / supplier / lane name to record against. REQUIRED. | |
| subject_type | No | 'carrier' (default), 'supplier' or 'lane'. | |
| lane | No | Lane label for context (e.g. 'Shanghai → Los Angeles'). Optional. | |
| promised_days | No | Promised transit/delivery in days. | |
| actual_days | No | Actual transit/delivery in days. | |
| on_time | No | Explicit on-time flag (else derived from promised+actual). | |
| damaged | No | Were goods damaged? | |
| discrepancy | No | Was there a documentary discrepancy? | |
| rolled | No | Was the container rolled / shut out? | |
| note | No | Free-text note. Optional. |