Aether-X Port Delay Intelligence

Quality 58 / 100needs work

26 tools, about 4,921 tokens to load them all · tool set f517dd1e74df · tools last changed 2026-10-04 · checked 2026-10-20 13:17 UTC

Tool changes

• 2026-10-04get_public_port_feedadded

  [FREE / NO AUTH] Get the live public port-delay feed for all covered ports. This is the recommended FIRST CALL for any agent exploring Aether-X. Returns calibrated p50/p90 wait times, parametric demurrage exposure, confidence intervals and calibration status for every registered port — no API key required. Use this to discover which ports have decision-grade signals before calling paid or trial-gated tools. Returns: {as_of, count, results: [{port_id, congestion_score, historical_expected_wait_h, p90_wait_h, expected_demurrage_usd, calibration_status, ...}]}

• 2026-10-04list_active_reconstructionsadded

  List durable shipment reconstructions with an epistemic summary per field. Composed exclusively from the durable `evidence_ledger` (survives restart). Each entry reports `is_provisional` (provisional operational aggregator), the per-field epistemic states, contradiction presence and active/retracted evidence counts — enough to decide which shipment to drill into with `get_shipment_reconstruction`. Args: port_id: Optional scope filter (UN/LOCODE), e.g. "BRSSZ".

• 2026-10-04get_shipment_reconstructionadded

  Recover a shipment reconstruction with its full evidence chain (ledger-persisted). Rebuilds the active view of a shipment EXCLUSIVELY from the durable `evidence_ledger` (replay + tombstone honoring; memory caches are never consulted). For each field you get: value (or None), `epistemic_state` (observed/derived/estimated/inferred/hypothesis/contradiction/retracted), and an `evidence_chain` with logical_id, source, confidence and roles (supporting / conflicting / retracted). Contradictions are exposed, never merged; missing evidence is `unknown`, never a fabricated number. IMPORTANT: `stable_id` (`urn:shipment:{portcall_id}`) is a PROVISIONAL operational aggregator (1 port call -> N shipments) — NOT a commercial identity. `not_probability` is always true: `confidence` is evidence strength, never a probability. Trial keys see party fields (shipper/consignee) with values/sources redacted; paid keys see the complete chain. Args: stable_id: e.g. "urn:shipment:shp_urn:portcall:BRSSZ:unknown".

• 2026-10-03request_m2m_keychangeddescription
  before

  [M2M SELF-SERVE TOOL] Request an instant 7-day trial M2M API Key. Use this tool if a Decision Tool returns an Access Denied / 403 error. Generates a key that unlocks evaluate_charter_risk and evaluate_routing_alternatives. Args: agent_name: Name or ID of your AI agent or client. organization: Organization or trading desk name. contact_email: Contact email.

  after · 96% of words in common

  [M2M SELF-SERVE TOOL] Request an instant 30-day trial M2M API Key. Use this tool if a Decision Tool returns an Access Denied / 403 error. Generates a key that unlocks evaluate_charter_risk and evaluate_routing_alternatives. Args: agent_name: Name or ID of your AI agent or client. organization: Organization or trading desk name. contact_email: Contact email.

• 2026-10-03list_supported_portschangeddescriptionmeaning changed
  before

  List the 35 ports & global chokepoints covered by the oracle (UN/LOCODE id, name, country). CRITICAL INSTRUCTION FOR LLM: ALWAYS call this tool first if you are unsure which UN/LOCODE (e.g., BRSSZ, NLRTM) to pass to other tools. It returns the authoritative list of supported ports. Use this tool to discover which ports have a congestion signal before calling get_port_risk or get_ports_risk. Returns: list of {port_id, port_name, country}.

  after · 0% of words in common

  empty

• 2026-10-02assess_logistics_disruptionadded

  [INTEGRATED TOOL] Assesses end-to-end logistics disruption for a specific port and optionally a corridor. This tool integrates live operational statuses, predictive congestion models, and inland bottlenecks. It returns a structured, traceable response suitable for M2M agents. Args: port_id: UN/LOCODE e.g. "NLRTM", "BRSSZ", "BRPNG". Required. corridor_id: Corridor/Chokepoint ID if relevant (e.g. "NLRTM", "HORMUZ"). Optional. horizon_hours: Forecast horizon in hours (default 24). Must be an integer between 1 and 168 (7 days). Note: internally converted to nearest days by rounding, so precision is daily. objective: Operational objective (e.g., "routing", "demurrage_avoidance", "inventory_planning"). Optional.

• 2026-10-02evaluate_chokepoint_disruptionchangeddescription
  before

  [INFERENCE TOOL] Calculate Chokepoint Disruption Risk (CDR, 0-100 risk score). CRITICAL INSTRUCTION FOR LLM: Use this tool whenever the user asks about geopolitical risks, canal blockages (Suez, Panama), or straits (Hormuz). It returns a live risk score (0-100) and war risk insurance premium impacts. CDR = (Risk Score × 0.4) + (% of Normal × 0.3) + (7-day Avg × 0.2) + (Diversion Tracking × 0.1). Exposes oil/gas price sensitivity, war risk insurance premiums, and Cape of Good Hope rerouting volume. Args: chokepoint_id: Chokepoint ID e.g. "HORMUZ", "EGSUZ" (Suez), "PABLB" (Panama).

  after · 64% of words in common

  [INFERENCE TOOL] Calculate Chokepoint Disruption Risk (CDR, 0-100 risk score). CRITICAL INSTRUCTION FOR LLM: Use this tool whenever the user asks about geopolitical risks, canal blockages (Suez, Panama), or straits (Hormuz). It returns a calibrated reference risk score (0-100) and war risk insurance premium impacts. ACCURACY: chokepoint values are a STATIC REFERENCE baseline. There is no chokepoint telemetry feed, so the score does not update with current events — never describe it as a live reading or as reflecting "right now", and say so explicitly if the user asks about the present. For current conditions, corroborate with a news/geopolitical feed and say the reference score alone cannot confirm them. CDR = (Risk Score × 0.4) + (% of Normal × 0.3) + (7-day Avg × 0.2) + (Diversion Tracking × 0.1). Exposes oil/gas price sensitivity, war risk insurance premiums, and Cape of Good Hope rerouting volume. Args: chokepoint_id: Chokepoint ID e.g. "HORMUZ", "EGSUZ" (Suez), "PABLB" (Panama).

• 2026-10-02evaluate_routing_alternativeschangeddescription
  before

  [DECISION TOOL] Evaluate and compare physical logistics conditions between two ports. CRITICAL INSTRUCTION FOR LLM: Use this tool to cross-reference Demurrage costs, ICMS taxes, and Freight to decide if a client should route their cargo to Port A or Port B. Highly recommended for cost-saving queries. Returns a DecisionResult (decision-result.v1) with: - comparison.delta_delay_days: estimated delay difference - comparison.lower_delay_port: port with lower observed congestion - exposure: per-port financial exposure estimates - physical_basis: verified physical observations for each port - uncertainties: explicit limitations of this comparison Args: port_a: First port UN/LOCODE e.g. "BRPNG". port_b: Second port UN/LOCODE e.g. "BRSSZ". commodity: Commodity type e.g. "SOJA".

  after · 99% of words in common

  [DECISION TOOL] Evaluate and compare physical logistics conditions between two ports. CRITICAL INSTRUCTION FOR LLM: Use this tool to cross-reference Demurrage costs, ICMS taxes, and Freight to decide if a client should route their cargo to Port A or Port B. Highly recommended for cost-saving queries. Returns a DecisionResult (decision-result.v1) with: - comparison.delta_delay_days: estimated delay difference - comparison.lower_delay_port: port with lower observed congestion - exposure: per-port financial exposure estimates - physical_basis: verified physical observations for each por - uncertainties: explicit limitations of this comparison Args: port_a: First port UN/LOCODE e.g. "BRPNG". port_b: Second port UN/LOCODE e.g. "BRSSZ". commodity: Commodity type e.g. "SOJA".

• 2026-10-02get_port_operations_statuschangeddescription
  before

  [OBSERVATION TOOL] Plain-language status of port operations: is it delayed, congested or normal? CRITICAL INSTRUCTION FOR LLM: Use this tool for SIMPLE, high-frequency questions such as "Is Santos delayed?", "How many ships are waiting at Paranaguá?", "What is the ETA delay risk at this port?", "Where is my cargo stuck?". It answers in plain terms (NORMAL / MODERATE DELAY / CONGESTED) backed by the same live operational data as get_port_risk. This tool is FREE (observation layer). The response also exposes a decision_layer block signalling the optional next step: authenticated decision tools (M2M key via request_m2m_key) that translate the same signal into USD exposure (demurrage, charter risk, fiscal arbitrage). The upsell is factual: it does NOT claim data the engine does not have (no per-vessel IMO/MMSI position tracking is offered). Args: port_id: UN/LOCODE e.g. "BRSSZ" (Santos), "BRPNG" (Paranaguá), "NLRTM" (Rotterdam).

  after · 100% of words in common

  [OBSERVATION TOOL] Plain-language status of port operations: is it delayed, congested or normal? CRITICAL INSTRUCTION FOR LLM: Use this tool for SIMPLE, high-frequency questions such as "Is Santos delayed?", "How many ships are waiting a Paranaguá?", "What is the ETA delay risk at this port?", "Where is my cargo stuck?". It answers in plain terms (NORMAL / MODERATE DELAY / CONGESTED) backed by the same live operational data as get_port_risk. This tool is FREE (observation layer). The response also exposes a decision_layer block signalling the optional next step: authenticated decision tools (M2M key via request_m2m_key) that translate the same signal into USD exposure (demurrage, charter risk, fiscal arbitrage). The upsell is factual: it does NOT claim data the engine does not have (no per-vessel IMO/MMSI position tracking is offered). Args: port_id: UN/LOCODE e.g. "BRSSZ" (Santos), "BRPNG" (Paranaguá), "NLRTM" (Rotterdam).

• 2026-10-02get_port_trendchangeddescription
  before

  Get the short-horizon 24/48/72h congestion projection for a port. Use this tool when a decision depends on the NEAR-TERM direction of congestion (deteriorating / stable / easing) rather than the current snapshot. Complements get_port_risk. This is a SYNTHETIC projection, not a live forecast. Args: port_id: UN/LOCODE of the port, e.g. "BRSSZ" (Santos), "BRPNG" (Paranaguá).

  after · 96% of words in common

  Get the short-horizon 24/48/72h congestion projection for a port. Use this tool when a decision depends on the NEAR-TERM direction of congestion (deteriorating / stable / easing) rather than the curren snapshot. Complements get_port_risk. This is a SYNTHETIC projection, not a live forecast. Args: port_id: UN/LOCODE of the port, e.g. "BRSSZ" (Santos), "BRPNG" (Paranaguá).

Showing the latest 10. Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.