# Axiomquay

*/Startups/Axiomquay*

## Startup Overview

A port terminal data infrastructure standardizes multi-party freight manifests into a single unified ledger. It intakes disparate shipping documentation from carriers, freight forwarders, and facility operators, mapping the data into a standardized record. This replaces disjointed email chains and spreadsheet handoffs with a persistent shared state for container movements.

Logistics coordinators and terminal operators frequently resolve discrepancies between carrier bills of lading and local yard records. Rather than relying on manual freight reconciliations or legacy Terminal Operating Systems that isolate data, the ledger automatically correlates inbound manifest files. It eliminates the mismatched cargo records that trigger gate delays and demurrage penalties.

While visibility tools like Project44 focus on geographic tracking, this architecture is schema-agnostic for fragmented inbound data and fully deterministic in its settlement logic. It absorbs varying formats of maritime documentation and produces a rigid financial and logistical ledger for freight handoffs. Terminals and carriers execute transfers of liability based on definitive system-verified cargo states.

## Startup Founding Hypothesis

**Approach**: that standardizes multi-party port terminal manifests into unified ledgers
**Competitors**:
- [Manual freight reconciliations](/Competitors/Manual_freight_reconciliations)
- [Project44](/Competitors/Project44)
- [Legacy Terminal Operating Systems](/Competitors/Legacy_Terminal_Operating_Systems)
**Differentiator2x2**: schema-agnostic for fragmented inbound data and fully deterministic in its settlement logic

## Startup Solution Coordinate

**Solution**: [Terminal Ledger Core](/Software/Terminal_Ledger_Core)

## Startup Position2x2

```mermaid
quadrantChart
  title Axiomquay Position vs. Competitors
  x-axis Rigid Schemas --> Schema-Agnostic Ingestion
  y-axis Manual/Probabilistic Tracking --> Deterministic Settlement Ledger
  quadrant-1 Automated & Deterministic
  quadrant-2 Siloed Automation
  quadrant-3 Legacy & Manual Operations
  quadrant-4 Aggregation & Visibility
  Manual freight reconciliations: [0.15, 0.15]
  Legacy Terminal Operating Systems: [0.25, 0.65]
  Project44: [0.85, 0.40]
  Axiomquay: [0.85, 0.85]
```

## Startup Customer Journey

```mermaid
flowchart LR; A[Maritime Logistics Conference] --> B[OpenAPI Registry]; B --> C[Pilot Ledger]; C --> D[Manifest Reconciliation Engine]; D --> E[Terminal Standard Ledger]; E --> F[Freight Forwarder Network]; F --> G[Port Authority Enterprise];
```

## Startup Proof Points

_Illustrative — target and order-of-magnitude estimate figures, not an achieved track record (this Thing is concept-stage)._

**Pilot Goals**:
- A 30-day single-terminal pilot processing 10,000 inbound manifest records to prove the schema-agnostic ingestion engine normalizes unstructured PDFs into a unified ledger format without manual entry.
- A 60-day multi-party settlement pilot connecting one terminal operator and three forwarders to validate deterministic matching accuracy when container weights contradict.
**Target Metrics**:
- Target: 100% automated parsing rate for unstructured PDF, XML, and EDI manifest records.
- Aim: Reduction in terminal reconciliation cycle times from days to under 60 seconds per vessel.
- Target: 0 incorrect financial settlements via deterministic anomaly flagging.
- Target: 2-hour maximum engineering resolution time for mapping anomalous unstructured freight schemas.
**Target Case Studies**:
- Mid-sized maritime terminal operator (Operations Director): Target transformation from manual PDF manifest data entry taking days per vessel to a unified ledger mapping that enables 60-second settlement across multiple forwarder schemas.
- Regional port authority (Chief Information Officer): Target transformation from fragmented EDI pipelines to a centralized ledger overlay that harmonizes unstructured payloads without replacing existing Terminal Operating Systems.
- Global freight forwarding network (VP of Logistics): Target transformation from high financial dispute rates due to mismatched container weights to zero-error deterministic matching prior to physical asset transfer.
**Testimonial Targets**:
- Terminal Operations Manager: Sentiment confirming that the deterministic matching correctly flags conflicting container seal data instead of forcing incorrect automated settlements.
- Port Authority IT Director: Sentiment verifying that the API-first ledger overlay integrates alongside their existing legacy TOS without requiring a core software replacement.
- Freight Forwarder Billing Specialist: Sentiment validating that automated settlement eliminates end-of-month reconciliation disputes over container transfer payloads.

## Startup Top Risks

**Risks**:
- Severity: existential · Description: Legacy Terminal Operating System vendors block data extraction APIs to prevent third-party ledger integration. · Mitigation Status: in-progress
- Severity: high · Description: The deterministic settlement logic cannot resolve physical cargo disputes automatically, forcing manual rollbacks that break ledger immutability. · Mitigation Status: unmitigated
- Severity: moderate · Description: Freight forwarders resist adopting the unified ledger interface due to heavy reliance on custom internal spreadsheet macros. · Mitigation Status: in-progress
- Severity: low · Description: Incumbents like Project44 deploy AI-based schema parsing, neutralizing the schema-agnostic inbound data advantage. · Mitigation Status: unmitigated

## Startup Competitors

- [Manual Freight Reconciliations](/Competitors/Manual_Freight_Reconciliations) — Status Quo
- [Project44](/Competitors/Project44) — Visibility Platform
- [Legacy Terminal Operating Systems](/Competitors/Legacy_Terminal_Operating_Systems) — Incumbent
- [Navis N4](/Competitors/Navis_N4) — Specialized TOS
- [E2open Supply Chain](/Competitors/E2open_Supply_Chain) — Enterprise Platform
- [Infor Nexus](/Competitors/Infor_Nexus) — Logistics Network

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: What if terminal data worked as a single source of truth? Axiomquay standardizes multi-party manifests into unified ledgers, eliminating reconciliation delays and demurrage penalties.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: fde4a6a26f05ff64

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: Multi-party port terminal ledger infrastructure for the logistics coordinator at port terminals. Unlike legacy Terminal Operating Systems — settle multi-party freight manifests in under 60 seconds.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: 986b97020fed9d9b

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: Resolving discrepancies between carrier bills of lading and local yard records requires days of manual reconciliation in legacy Terminal Operating Systems.
Solution: What if terminal data worked as a single source of truth? Axiomquay standardizes multi-party manifests into unified ledgers, eliminating reconciliation delays and demurrage penalties.
Customer: the logistics coordinator at port terminals
Unlike: legacy Terminal Operating Systems
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: b1c95d834af3b59a

## Startup Token M E D D P I C C

**Pain**: Resolving discrepancies between carrier bills of lading and local yard records requires days of manual reconciliation in legacy Terminal Operating Systems.
**Metrics**: Target: Container records match perfectly across all parties, enabling vessel-wide settlement in under 60 seconds without gate-blocking errors.
**Rendered**: Pain: Resolving discrepancies between carrier bills of lading and local yard records requires days of manual reconciliation in legacy Terminal Operating Systems.
Economic buyer: Port Terminal Operator
Metrics: Target: Container records match perfectly across all parties, enabling vessel-wide settlement in under 60 seconds without gate-blocking errors.
Competition: legacy Terminal Operating Systems
**Mechanism**: spine-derived-v1
**Competition**: legacy Terminal Operating Systems
**Economic Buyer**: Port Terminal Operator
**Vocab Fingerprint**: 94e6da6df1883d54

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: Multi-party port terminal ledger infrastructure for the logistics coordinator at port terminals

the logistics coordinator at port terminals — Resolving discrepancies between carrier bills of lading and local yard records requires days of manual reconciliation in legacy Terminal Operating Systems. What if terminal data worked as a single source of truth? Axiomquay standardizes multi-party manifests into unified ledgers, eliminating reconciliation delays and demurrage penalties.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: 8904c46c58e1d4f8

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: Multi-party port terminal ledger infrastructure. What if terminal data worked as a single source of truth? Axiomquay standardizes multi-party manifests into unified ledgers, eliminating reconciliation delays and demurrage penalties. Serves the logistics coordinator at port terminals.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: a3bef08a587c8511

## Neighborhood

### Candidate solutions

- [Specialized Floor Staff Recruitment](/Problems/Specialized_Floor_Staff_Recruitment) — candidate solution for · Problems

### Composed of

- [Manifest Reconcile Service](/Services/Manifest_Reconcile_Service) — composes · Services
- [Terminal Ledger Engine](/Agents/Terminal_Ledger_Engine) — composes · Agents
- [Unified Manifest API](/Agents/Unified_Manifest_API) — composes · Agents
- [Deterministic Settlement Agent](/Agents/Deterministic_Settlement_Agent) — composes · Agents
- [Schema Ingestion Agent](/Agents/Schema_Ingestion_Agent) — composes · Agents

### What it offers

- [Terminal Ledger Core](/Software/Terminal_Ledger_Core) — offers · Software

### Competitors

- [Project44](/Competitors/Project44) — competes with · Competitors
- [Legacy Terminal Operating Systems](/Competitors/Legacy_Terminal_Operating_Systems) — competes with · Competitors
- [Navis N4](/Competitors/Navis_N4) — competes with · Competitors
- [E2open Supply Chain](/Competitors/E2open_Supply_Chain) — competes with · Competitors
- [Infor Nexus](/Competitors/Infor_Nexus) — competes with · Competitors
- [Manual Freight Reconciliations](/Competitors/Manual_Freight_Reconciliations) — competes with · Competitors

### Embodies

- [Software](/Theses/Software) — embodies · Theses

### Similar Startups

- [Truewharf](/Startups/Truewharf) — similar · Startups
- [Portyn](/Startups/Portyn) — similar · Startups
- [Conduitharbor](/Startups/Conduitharbor) — similar · Startups
- [Stridewharf](/Startups/Stridewharf) — similar · Startups
- [Cargofield](/Startups/Cargofield) — similar · Startups
- [Cadencewharf](/Startups/Cadencewharf) — similar · Startups
- [Voyagepoint](/Startups/Voyagepoint) — similar · Startups
- [Arrivalguild](/Startups/Arrivalguild) — similar · Startups
- [Valleyrail](/Startups/Valleyrail) — similar · Startups
- [Cargovista](/Startups/Cargovista) — similar · Startups
- [Crossoyage](/Startups/Crossoyage) — similar · Startups
- [Beaconharbor](/Startups/Beaconharbor) — similar · Startups
- [Bloomdock](/Startups/Bloomdock) — similar · Startups
- [Pinnacleship](/Startups/Pinnacleship) — similar · Startups
- [Anchorloft](/Startups/Anchorloft) — similar · Startups
- [Clearquay](/Startups/Clearquay) — similar · Startups
- [Coordinatortower](/Startups/Coordinatortower) — similar · Startups
- [Wholesalequay](/Startups/Wholesalequay) — similar · Startups
- [Planequay](/Startups/Planequay) — similar · Startups
- [Daleharbor](/Startups/Daleharbor) — similar · Startups