# Crossoyage

*/Startups/Crossoyage*

## Startup Overview

This API-first logistics infrastructure normalizes multi-carrier maritime manifests to enable predictive routing. Rather than forcing teams to decipher fragmented supply chain documents, the system ingests raw manifest structures from diverse shipping lines and outputs a standardized, machine-readable format.

Global freight forwarders and supply chain engineers rely on this pipeline to untangle complex electronic data interchanges. Traditional visibility tools demand heavy onboarding and manual mapping to handle carrier-specific quirks. By providing a developer-native interface, engineering teams integrate global shipping data directly into their core routing engines without friction.

Unlike legacy platforms like Project44 or FourKites that lock users into rigid enterprise contracts, this service operates on a strict utility model. Customers pay exclusively for successful payload normalizations. This usage-based approach allows logistics builders to bypass manual integrations entirely and deploy dynamic, multi-carrier routing logic.

## Startup Founding Hypothesis

**Approach**: that normalizes multi-carrier maritime manifests for predictive routing
**Competitors**:
- [Project44](/Competitors/Project44)
- [FourKites](/Competitors/FourKites)
- [Manual EDI Integrations](/Competitors/Manual_EDI_Integrations)
**Differentiator2x2**: developer-native for immediate integration and priced strictly on successful payload normalizations

## Startup Solution Coordinate

**Solution**: [Ocean Manifest Engine](/Software/Ocean_Manifest_Engine)

## Startup Position2x2

```mermaid
quadrantChart
    title Maritime Manifest Normalization
    x-axis Enterprise Sales-Led --> Developer-Native API
    y-axis Rigid Subscription --> Pay-per-Successful Payload
    quadrant-1 Elastic Integrations
    quadrant-2 Managed Usage
    quadrant-3 Enterprise Platforms
    quadrant-4 Premium Developer Tools
    Crossoyage: [0.88, 0.85]
    Project44: [0.20, 0.25]
    FourKites: [0.25, 0.20]
    Manual EDI Integrations: [0.10, 0.50]
```

## Startup Offer

**Proof**:
- Targeting 99.9% schema extraction accuracy across the top 15 global ocean carrier EDI formats
- Aiming to reduce developer integration time for multi-carrier freight tracking from months to under 48 hours
- Designed to process over 1,000,000 maritime manifests monthly for predictive supply chain routing engines
**Tiers**:
- Name: Sandbox · Price: ~$0 · Inclusions: Up to 1,000 API calls per month for developer testing and integration validation against sample and live endpoints
- Name: Standard Volume · Price: ~$0.08–$0.15 per successful normalization · Inclusions: Standard multi-carrier manifest parsing, unlimited endpoints, strictly metered on perfectly normalized JSON payloads returned (HTTP 200)
- Name: Enterprise Routing · Price: ~$0.03–$0.06 per successful normalization · Inclusions: Volumes exceeding 100,000 payloads per month, custom predictive routing webhooks, and priority schema-drift resolution support
**Guarantee**: If Crossoyage returns a failed, incomplete, or malformed manifest schema for a supported carrier, that payload is entirely unbilled, and any API downtime exceeding the 99.9% SLA is automatically compensated with next-month usage credits.
**Business Function**: ProvideService
**Objection Handlers**:
- Objection: Carriers constantly change their proprietary EDI formats without warning. Rebuttal: Crossoyage's extraction layer is designed to monitor schema drift automatically, deploying heuristic fallbacks while instantly flagging definitions for developer updates.
- Objection: We already use a major visibility platform like Project44. Rebuttal: Crossoyage is a headless, developer-native API focused entirely on supplying clean payload data to your internal systems, bypassing expensive dashboard bloat.
- Objection: We cannot afford to pay for failed API requests when carrier portals go down. Rebuttal: The API is metered strictly on successful normalizations; if the carrier fails to return a parseable manifest, you are not charged.
**Pricing Architecture**: UsageMeter
**Agent Checkout Support**:
- agentic-commerce-protocol

## Startup Brand

**Voice**: Direct technical register emphasizing structural precision and data certainty
**Tagline**: Unified maritime manifests for immediate predictive cargo routing
**Icon Concept**: container
**Palette Intent**: electric-signal
**Visual Identity**: The visual identity pairs deep ocean navy with terminal neon cyan and strict monospace typography to emphasize developer-grade precision within complex maritime logistics.
**Archetype Reference**: the-sage

## Startup Buyer Chain

**Chain**: B2B → Logistics Software Engineer → Freight Forwarding Operations
**Gtm Motion**: Acquires users through self-serve sandbox access that allows logistics developers to test manifest normalization immediately. Expands accounts via a usage-based pricing model triggered solely by the volume of successfully processed maritime payloads.
**Agent Channel**: Designed to publish a structured OpenAPI specification to tool registries like LlamaHub and LangChain, allowing autonomous supply chain orchestration agents to discover and call the manifest normalization endpoints.
**Primary Channel**: Organic search and technical documentation hubs targeting developers actively querying for terms like 'maritime EDI parser API' and 'multi-carrier ocean freight API'.

## Startup Customer Journey

```mermaid
flowchart LR; A[Search Engine] --> B[Documentation Hub]; C[OpenAPI Registry] --> B; B --> D[Sandbox Environment]; D --> E[Manifest Parser]; E --> F[Production API]; F --> G[Metering Engine]; G --> H[Enterprise Webhook];
```

## Startup Proof Points

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

**Pilot Goals**:
- 30-day proof-of-concept running in parallel with an existing legacy EDI processor, aiming to successfully normalize 50,000 live maritime manifests with zero downtime.
- 14-day Sandbox integration sprint targeting a successful connection to 5 distinct global ocean carriers, proving total developer integration time under 48 hours.
**Target Metrics**:
- Target: Under 48 hours developer integration time for multi-carrier freight tracking.
- Aim: 99.9 percent schema extraction accuracy across the top 15 global ocean carrier EDI formats.
- Target: 0 billable charges for failed, incomplete, or malformed carrier manifest schemas.
- Aim: 100 percent automated fallback deployment upon detected carrier schema drift.
**Target Case Studies**:
- Mid-market supply chain visibility software CTO replacing a brittle in-house carrier integration maintenance team with a single API, reducing developer time spent on EDI schema drift from 40 hours a week to zero.
- Enterprise freight forwarding VP of Product launching a new predictive routing engine using clean, normalized JSON from 10 different ocean carriers, achieving rollout in under 3 weeks rather than 6 months.
- Third-party logistics Lead Developer switching from dashboard-heavy visibility tools to a headless API, cutting payload data costs by 60 percent while maintaining full data fidelity for internal systems.
**Testimonial Targets**:
- Lead Integration Engineer praising the strict usage-metered pricing that ensures they never pay for malformed carrier endpoints or failed API requests.
- Supply Chain Product Manager confirming the headless API seamlessly feeds their internal predictive routing engine without forcing them to buy redundant UI dashboards.
- VP of Engineering highlighting the relief of offloading automated schema drift resolution and heuristic fallbacks to a dedicated normalization layer.

## Startup Top Risks

**Risks**:
- Severity: existential · Description: Major ocean carriers block or rate-limit third-party data access to force shippers into proprietary tracking portals. · Mitigation Status: unmitigated
- Severity: high · Description: Frequent undocumented changes to carrier EDI formats cause failed normalizations, burning compute costs under the success-only pricing model. · Mitigation Status: in-progress
- Severity: high · Description: Incumbents like Project44 commoditize the maritime manifest feature by bundling it at zero cost within broader enterprise supply chain contracts. · Mitigation Status: unmitigated
- Severity: moderate · Description: Logistics buyers at mid-market freight forwarders lack in-house developer resources to implement a headless API solution. · Mitigation Status: in-progress

## Startup Competitors

- [Project44](/Competitors/Project44) — Incumbent
- [FourKites](/Competitors/FourKites) — Incumbent
- [Manual EDI Integrations](/Competitors/Manual_EDI_Integrations) — Status Quo
- [Vizion API](/Competitors/Vizion_API) — Maritime API
- [Terminal49](/Competitors/Terminal49) — Maritime API

## Startup Solution Stack

- [Predictive Routing Service](/Services/Predictive_Routing_Service) — Service-as-Software
- [Carrier Parsing Agent](/Agents/Carrier_Parsing_Agent) — Agent
- [Manifest Normalization Worker](/Agents/Manifest_Normalization_Worker) — Agent
- [Ocean Manifest API](/Software/Ocean_Manifest_API) — Software
- [Payload Ingestion SDK](/Software/Payload_Ingestion_SDK) — Software

## Startup Story Brand

**Hero**:
- **Need**: to be the architect of intelligent supply chains, not a manual parser of carrier-specific XML
- **Want**: to build predictive routing engines without wrestling with non-standard maritime EDI files
- **Identity**: the logistics software developer at a global freight forwarder
**Plan**:
- Step: Input API key · Detail: Generate your Sandbox credentials to begin testing against live carrier manifest endpoints.
- Step: Check payload schema · Detail: Validate the perfectly normalized JSON responses against your internal routing engine requirements.
- Step: Scale production calls · Detail: Go live with usage-based pricing that only bills for successfully parsed cargo manifests.
**Guide**:
- **Empathy**: When a carrier updates their manifest format without notice, your entire visibility dashboard breaks and triggers emergency developer hotfixes.
**Problem**:
- **Villain**: schema drift
- **External**: Integrating fragmented manifests from Maersk, MSC, and COSCO into internal tracking systems requires months of manual EDI mapping and constant maintenance.
- **Internal**: You feel like a data janitor cleaning up messy carrier payloads instead of building advanced routing logic.
- **Philosophical**: Why should logistics engineers accept proprietary data silos when unified cargo visibility is technically possible?
**Success**: Your routing engine receives clean, unified maritime data from every major carrier through a single API endpoint.
**One Liner**: Every shipment cycle, logistics developers struggle with broken EDI files. Crossoyage normalizes multi-carrier maritime manifests into unified JSON so you can build predictive routing instantly.
**Positioning**:
- **So That**: get clean manifest data without paying for expensive dashboard bloat
- **Unlike**: Project44 and FourKites
- **For Whom**: Logistics developers at global freight forwarders
- **Category**: Maritime Data Normalization API
**Call To Action**:
- **Direct**: Launch Sandbox API
- **Transitional**: View JSON Schema Docs
**Failure Stakes**:
- Months of integration delay
- Unreliable cargo tracking data
- High maintenance overhead costs
**Transformation**:
- **To**: free to build predictive routing logic, no longer stuck fixing broken carrier integrations
- **From**: a developer buried in manual EDI mapping
**Controlling Idea**: Shipping data should be developer-ready and unified across every global ocean carrier.

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: Every shipment cycle, logistics developers struggle with broken EDI files. Crossoyage normalizes multi-carrier maritime manifests into unified JSON so you can build predictive routing instantly.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: 75939ddb2d8614de

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: Maritime Data Normalization API for Logistics developers at global freight forwarders. Unlike Project44 and FourKites — get clean manifest data without paying for expensive dashboard bloat.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: 744408e3dfca049b

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: Integrating fragmented manifests from Maersk, MSC, and COSCO into internal tracking systems requires months of manual EDI mapping and constant maintenance.
Solution: Every shipment cycle, logistics developers struggle with broken EDI files. Crossoyage normalizes multi-carrier maritime manifests into unified JSON so you can build predictive routing instantly.
Customer: Logistics developers at global freight forwarders
Unlike: Project44 and FourKites
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: 25c04310f30153a6

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

**Pain**: Integrating fragmented manifests from Maersk, MSC, and COSCO into internal tracking systems requires months of manual EDI mapping and constant maintenance.
**Metrics**: Target: Your routing engine receives clean, unified maritime data from every major carrier through a single API endpoint.
**Rendered**: Pain: Integrating fragmented manifests from Maersk, MSC, and COSCO into internal tracking systems requires months of manual EDI mapping and constant maintenance.
Economic buyer: Logistics Software Engineer
Metrics: Target: Your routing engine receives clean, unified maritime data from every major carrier through a single API endpoint.
Competition: Project44 and FourKites
**Mechanism**: spine-derived-v1
**Competition**: Project44 and FourKites
**Economic Buyer**: Logistics Software Engineer
**Vocab Fingerprint**: 8f9683ffd967cac6

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: Maritime Data Normalization API for Logistics developers at global freight forwarders

Logistics developers at global freight forwarders — Integrating fragmented manifests from Maersk, MSC, and COSCO into internal tracking systems requires months of manual EDI mapping and constant maintenance. Every shipment cycle, logistics developers struggle with broken EDI files. Crossoyage normalizes multi-carrier maritime manifests into unified JSON so you can build predictive routing instantly.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: 37385191dc65cee2

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: Maritime Data Normalization API. Every shipment cycle, logistics developers struggle with broken EDI files. Crossoyage normalizes multi-carrier maritime manifests into unified JSON so you can build predictive routing instantly. Serves Logistics developers at global freight forwarders.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: 2befb641fd3f2345

## Neighborhood

### Candidate solutions

- [Defect Reporting Latency](/Problems/Defect_Reporting_Latency) — candidate solution for · Problems

### What it offers

- [Ocean Manifest Engine](/Software/Ocean_Manifest_Engine) — offers · Software

### Composed of

- [Payload Ingestion SDK](/Software/Payload_Ingestion_SDK) — composes · Software
- [Carrier Parsing Agent](/Agents/Carrier_Parsing_Agent) — composes · Agents
- [Ocean Manifest API](/Software/Ocean_Manifest_API) — composes · Software
- [Predictive Routing Service](/Services/Predictive_Routing_Service) — composes · Services
- [Manifest Normalization Worker](/Agents/Manifest_Normalization_Worker) — composes · Agents

### Embodies

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

### Competitors

- [Vizion API](/Competitors/Vizion_API) — competes with · Competitors
- [FourKites](/Competitors/FourKites) — competes with · Competitors
- [Manual EDI Integrations](/Competitors/Manual_EDI_Integrations) — competes with · Competitors
- [Project44](/Competitors/Project44) — competes with · Competitors
- [Terminal49](/Competitors/Terminal49) — competes with · Competitors

### Similar Startups

- [Conduitharbor](/Startups/Conduitharbor) — similar · Startups
- [Coordinatortower](/Startups/Coordinatortower) — similar · Startups
- [Freighter](/Startups/Freighter) — similar · Startups
- [Beamlane](/Startups/Beamlane) — similar · Startups
- [Valleymanifest](/Startups/Valleymanifest) — similar · Startups
- [Pinnacleship](/Startups/Pinnacleship) — similar · Startups
- [Kerforder](/Startups/Kerforder) — similar · Startups
- [Clearancewing](/Startups/Clearancewing) — similar · Startups
- [Cadencewharf](/Startups/Cadencewharf) — similar · Startups
- [Dalyard](/Startups/Dalyard) — similar · Startups
- [Tracelane](/Startups/Tracelane) — similar · Startups
- [Daleharbor](/Startups/Daleharbor) — similar · Startups
- [Challengequay](/Startups/Challengequay) — similar · Startups
- [Carvauge](/Startups/Carvauge) — similar · Startups
- [Foliumquay](/Startups/Foliumquay) — similar · Startups
- [Truewharf](/Startups/Truewharf) — similar · Startups
- [Cargovista](/Startups/Cargovista) — similar · Startups
- [Cratefield](/Startups/Cratefield) — similar · Startups
- [Portyn](/Startups/Portyn) — similar · Startups
- [Voyagefield](/Startups/Voyagefield) — similar · Startups