# Foliumquay

*/Startups/Foliumquay*

## Startup Overview

Freight brokers and logistics teams handle a relentless daily volume of unstructured shipping documentation, often relying on manual transcription to parse bills of lading and packing lists. An API-driven engine ingests and structures these multi-format inbound freight documents, converting chaotic PDFs, images, and emails directly into standardized data schemas. It removes the data entry barrier entirely, enabling routing and customs systems to execute shipments without human oversight.

Legacy enterprise OCR software like ABBYY Vantage and Kofax trap operations in heavy template training and rigid visual workflow builders. In contrast, the service operates as a developer-first API designed specifically for logistics engineering teams to integrate into existing transportation management systems immediately. It charges exclusively based on verified extraction outcomes, ensuring that supply chain operators pay only for completely accurate, production-ready data rather than raw processing attempts or failed parses.

## Startup Founding Hypothesis

**Approach**: that ingests and structures multi-format inbound freight documents
**Competitors**:
- [ABBYY Vantage](/Competitors/ABBYY_Vantage)
- [Kofax](/Competitors/Kofax)
- [manual broker transcription](/Competitors/manual_broker_transcription)
**Differentiator2x2**: a developer-first API priced exclusively on verified extraction outcomes

## Startup Solution Coordinate

**Solution**: [Manifest Extraction Engine](/Software/Manifest_Extraction_Engine)

## Startup Position2x2

```mermaid
quadrantChart
    title Market Positioning
    x-axis "End-User UI" --> "Developer-First API"
    y-axis "Capacity/Labor Priced" --> "Verified Outcome Priced"
    quadrant-1 "Usage-based APIs"
    quadrant-2 "Outcome-based Apps"
    quadrant-3 "Legacy Platforms"
    quadrant-4 "Traditional APIs"
    Foliumquay: [0.85, 0.85]
    ABBYY Vantage: [0.45, 0.35]
    Kofax: [0.20, 0.25]
    manual broker transcription: [0.05, 0.10]
```

## Startup Offer

**Proof**:
- Targeting 99.5% field-level accuracy on non-standard, low-DPI Bill of Lading scans
- Aiming to reduce manual broker transcription time from 5 minutes to 30 seconds per shipment
- Designed to reliably parse mixed-language commercial invoices for mid-sized freight forwarders
**Tiers**:
- Name: Developer Meter · Price: ~$0.15–$0.25 per verified document · Inclusions: Standard API access for Bills of Lading, commercial invoices, and packing lists with webhooks for verified payload delivery. No minimum volume.
- Name: Volume Commitment · Price: ~$0.08–$0.12 per verified document · Inclusions: Requires a minimum of 10,000 documents per month. Includes priority processing SLA, custom schema definitions, and a dedicated integration support channel.
**Guarantee**: You only pay for payloads that pass your custom schema validation with 99%+ confidence. If a document requires manual broker transcription due to an API failure, the extraction is not billed.
**Business Function**: ProvideService
**Objection Handlers**:
- Objection: Our carriers send terrible, handwritten scans that traditional OCR fails on. Rebuttal: The system is designed with multimodal ingestion that interprets visual context, not just text, and only charges you when the final structured output is verified.
- Objection: We already spent months setting up Kofax templates for our main carriers. Rebuttal: Foliumquay requires zero template maintenance; it adapts dynamically to unexpected or altered carrier formats on day one.
- Objection: How do we know the data is trustworthy enough for customs clearance? Rebuttal: Every API response is designed to include field-level confidence scores and original document bounding boxes so your operators can instantly audit flagged anomalies.
**Pricing Architecture**: UsageMeter
**Agent Checkout Support**:
- agentic-commerce-protocol

## Startup Brand

**Voice**: Technical and direct, emphasizing structural precision and developer utility.
**Tagline**: Structured freight data delivered via an outcome-priced developer API.
**Icon Concept**: container
**Palette Intent**: industrial-safety
**Visual Identity**: A high-contrast industrial aesthetic pairing hazard orange with monospaced typography and stark dark backgrounds to evoke automated freight terminals.
**Archetype Reference**: the-sage

## Startup Buyer Chain

**Chain**: B2B → Freight Tech Developers → 3PL Operations Teams
**Gtm Motion**: Acquires logistics engineering teams through self-serve API access and open sandbox testing environments. Expands accounts through volume-based usage scaling as developers route additional document types like commercial invoices and packing slips through the endpoint.
**Agent Channel**: Designed to target listings in the LangChain tool registry and OpenAI action directory as a structured freight document parser, allowing autonomous supply chain agents to submit raw PDFs and receive verified JSON payloads.
**Primary Channel**: Organic search and technical forums where logistics engineers query terms like 'bill of lading OCR API' or 'freight document parser', leading directly to Foliumquay's interactive documentation.

## Startup Customer Journey

```mermaid
flowchart LR; A[Logistics Technical Forum] --> B[Interactive API Documentation]; B --> C[Developer API Sandbox]; C --> D[Verified JSON Payload]; D --> E[Production Webhook]; E --> F[Volume Usage Tier]; F --> G[Developer Community];
```

## Startup Proof Points

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

**Pilot Goals**:
- A 14-day shadow run alongside a mid-sized freight forwarder's existing OCR tool, aiming to prove a higher field-level capture rate on 1,000 low-resolution, handwritten Bills of Lading.
- A 30-day API integration pilot with a customs SaaS platform, processing 5,000 historical commercial invoices to validate the 99%+ confidence scoring threshold and the zero-billing guarantee on failed extractions.
**Target Metrics**:
- Target: 99.5% field-level extraction accuracy on non-standard, low-DPI document scans
- Aim: 5 minutes to 30 seconds reduction in manual transcription time per shipment
- Target: 0 hours required for template setup and maintenance when onboarding new carrier document formats
- Aim: 100% SLA compliance for verified payload delivery via webhooks
**Target Case Studies**:
- Mid-sized freight forwarder processing non-standard ocean Bills of Lading: Transforming operations by shifting from five-minute manual data entry per shipment to instant API extraction with 30-second human verification.
- Regional customs brokerage handling mixed-language commercial invoices: Replacing brittle, legacy OCR templates with a dynamic, zero-maintenance ingestion pipeline that scales document processing without requiring additional data-entry headcount.
- Logistics SaaS platform integrating automated document parsing: Embedding the extraction API to offer automated packing list reconciliation, converting a fixed operational cost into a variable, usage-metered expense where they only pay for verified payloads.
**Testimonial Targets**:
- Customs Brokerage Operations Manager expressing relief that their team now only audits flagged anomalies using exact document bounding boxes rather than re-typing entire handwritten commercial invoices.
- VP of Product at a Logistics Platform praising the usage-metered API design and the specific guarantee that they only pay for payloads passing their custom schema validation.
- Head of Freight Forwarding highlighting how the multimodal ingestion system handles unexpected carrier formatting changes dynamically, eliminating the downtime previously caused by broken templates.

## Startup Top Risks

**Risks**:
- Severity: existential · Description: Compute and operational costs exceed revenue because the outcome-based pricing model fails to cover processing attempts on highly degraded or illegible freight documents. · Mitigation Status: in-progress
- Severity: high · Description: Target 3PLs and freight brokers refuse to rip out deeply entrenched legacy OCR workflows like ABBYY or Kofax due to high switching costs and integration fatigue. · Mitigation Status: unmitigated
- Severity: high · Description: The developer-centric go-to-market strategy misaligns with the logistics industry reality that operations executives, not software engineers, hold the budget for document automation. · Mitigation Status: unmitigated
- Severity: moderate · Description: Extreme layout variability in international customs forms requires manual human-in-the-loop intervention, destroying the unit economics required to maintain competitive API pricing. · Mitigation Status: in-progress

## Startup Competitors

- [ABBYY Vantage](/Competitors/ABBYY_Vantage) — Incumbent
- [Kofax](/Competitors/Kofax) — Legacy Enterprise
- [Manual Broker Transcription](/Competitors/Manual_Broker_Transcription) — Status Quo
- [Rossum](/Competitors/Rossum) — IDP Platform
- [Sensible Instruct](/Competitors/Sensible_Instruct) — Developer API

## Startup Story Brand

**Hero**:
- **Need**: to be the architect of a touchless logistics pipeline, not a manager of manual transcription teams
- **Want**: to automate the ingestion of multi-format carrier documents into their TMS
- **Identity**: the technical lead at a mid-sized freight forwarder
**Plan**:
- Step: Define Schema · Detail: Post your required JSON structure for Bills of Lading and invoices to our API endpoint.
- Step: Review Payloads · Detail: Verify the structured data against your original scans using our provided bounding box coordinates.
- Step: Pay Success · Detail: Only clear the usage meter for documents that pass your validation and 99% confidence threshold.
**Guide**:
- **Empathy**: Revenue and cargo-flow are won in minutes — but brittle ABBYY templates and handwritten scans keep your shipments stuck at the dock.
**Problem**:
- **Villain**: template-locked OCR
- **External**: Processing Bills of Lading in Kofax requires constant manual template adjustments for every carrier change and low-DPI scan
- **Internal**: You feel like you are babysitting brittle software instead of building scalable logistics infrastructure
- **Philosophical**: Logistics software was built for movement, not for managing the failures of 20th-century optical character recognition.
**Success**: Your freight data flows instantly from messy scans to structured JSON, letting you clear shipments in seconds without touching a template.
**One Liner**: What if carrier documents were structured JSON by default? Foliumquay ingests messy Bills of Lading and invoices, delivering verified data via an outcome-priced API so your shipments never stall.
**Positioning**:
- **So That**: automate inbound document ingestion without template maintenance
- **Unlike**: manual broker transcription
- **For Whom**: technical leads at freight forwarders
- **Category**: Outcome-priced freight data API
**Call To Action**:
- **Direct**: Generate API Key
- **Transitional**: View Schema Documentation
**Failure Stakes**:
- Stalled customs clearances
- Burnout from manual transcription
- High error rates in TMS data
**Transformation**:
- **To**: the engineer who builds fully autonomous freight pipelines
- **From**: the lead managing a manual transcription queue
**Controlling Idea**: Freight data should be a utility, not a manual transcription burden.

## Startup Token Bindings

**Vocab Fingerprint**: 731b5fab4fbaf49a

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: What if carrier documents were structured JSON by default? Foliumquay ingests messy Bills of Lading and invoices, delivering verified data via an outcome-priced API so your shipments never stall.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: c9ee8bf1e8fc1fd6

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: Outcome-priced freight data API for technical leads at freight forwarders. Unlike manual broker transcription — automate inbound document ingestion without template maintenance.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: 4c21d9cb4cc3d659

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: Processing Bills of Lading in Kofax requires constant manual template adjustments for every carrier change and low-DPI scan
Solution: What if carrier documents were structured JSON by default? Foliumquay ingests messy Bills of Lading and invoices, delivering verified data via an outcome-priced API so your shipments never stall.
Customer: technical leads at freight forwarders
Unlike: manual broker transcription
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: 0287f7bfbc6024c7

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

**Pain**: Processing Bills of Lading in Kofax requires constant manual template adjustments for every carrier change and low-DPI scan
**Metrics**: Target: Your freight data flows instantly from messy scans to structured JSON, letting you clear shipments in seconds without touching a template.
**Rendered**: Pain: Processing Bills of Lading in Kofax requires constant manual template adjustments for every carrier change and low-DPI scan
Economic buyer: Freight Tech Developers
Metrics: Target: Your freight data flows instantly from messy scans to structured JSON, letting you clear shipments in seconds without touching a template.
Competition: manual broker transcription
**Mechanism**: spine-derived-v1
**Competition**: manual broker transcription
**Economic Buyer**: Freight Tech Developers
**Vocab Fingerprint**: a7bcaf18c9bd168d

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: Outcome-priced freight data API for technical leads at freight forwarders

technical leads at freight forwarders — Processing Bills of Lading in Kofax requires constant manual template adjustments for every carrier change and low-DPI scan What if carrier documents were structured JSON by default? Foliumquay ingests messy Bills of Lading and invoices, delivering verified data via an outcome-priced API so your shipments never stall.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: d3e5f6fa29c04e86

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: Outcome-priced freight data API. What if carrier documents were structured JSON by default? Foliumquay ingests messy Bills of Lading and invoices, delivering verified data via an outcome-priced API so your shipments never stall. Serves technical leads at freight forwarders.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: c14c398dadddf40a

## Neighborhood

### Candidate solutions

- [Accounting Automation](/Problems/Accounting_Automation) — candidate solution for · Problems

### Composed of

- [Ledger Allocation Service](/Services/Ledger_Allocation_Service) — composes · Services
- [Semantic Extraction API](/Software/Semantic_Extraction_API) — composes · Software
- [Probabilistic Mapping Engine](/Software/Probabilistic_Mapping_Engine) — composes · Software
- [Variance Resolution Worker](/Agents/Variance_Resolution_Worker) — composes · Agents
- [Voucher Triage Agent](/Agents/Voucher_Triage_Agent) — composes · Agents
- [Invoice Triage Worker](/Agents/Invoice_Triage_Worker) — composes · Agents
- [Probabilistic Mapping API](/Software/Probabilistic_Mapping_API) — composes · Software
- [Ledger Reconciliation Agent](/Agents/Ledger_Reconciliation_Agent) — composes · Agents
- [Semantic Extraction Engine](/Software/Semantic_Extraction_Engine) — composes · Software
- [Ledger Integration SDK](/Software/Ledger_Integration_SDK) — composes · Software
- [Multimodal Extraction Engine](/Software/Multimodal_Extraction_Engine) — composes · Software
- [Suspense Resolution Worker](/Agents/Suspense_Resolution_Worker) — composes · Agents
- [Contextual Routing Agent](/Agents/Contextual_Routing_Agent) — composes · Agents
- [Ledger Classification Service](/Services/Ledger_Classification_Service) — composes · Services
- [Ledger Mapping Agent](/Agents/Ledger_Mapping_Agent) — composes · Agents
- [Voucher Allocation Service](/Services/Voucher_Allocation_Service) — composes · Services
- [General Ledger Routing API](/Software/General_Ledger_Routing_API) — composes · Software
- [Multimodal Vision Engine](/Software/Multimodal_Vision_Engine) — composes · Software
- [Invoice Split Worker](/Agents/Invoice_Split_Worker) — composes · Agents
- [Freight Extraction SDK](/Agents/Freight_Extraction_SDK) — composes · Agents
- [Manifest Structuring Service](/Services/Manifest_Structuring_Service) — composes · Services
- [Freight Verification Worker](/Agents/Freight_Verification_Worker) — composes · Agents
- [Document Ingestion API](/Agents/Document_Ingestion_API) — composes · Agents
- [Waybill Parser Agent](/Agents/Waybill_Parser_Agent) — composes · Agents

### Embodies

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

### What it offers

- [Ledger Transit](/Software/Ledger_Transit) — offers · Software
- [Manifest Extraction Engine](/Software/Manifest_Extraction_Engine) — offers · Software
- [Voucher Prism](/Software/Voucher_Prism) — offers · Software

### Competitors

- [Oracle NetSuite](/Competitors/Oracle_NetSuite) — competes with · Competitors
- [ABBYY FlexiCapture](/Competitors/ABBYY_FlexiCapture) — competes with · Competitors
- [Offshore Data Entry](/Competitors/Offshore_Data_Entry) — competes with · Competitors
- [Rossum](/Competitors/Rossum) — competes with · Competitors
- [Manual Broker Transcription](/Competitors/Manual_Broker_Transcription) — competes with · Competitors
- [ABBYY Vantage](/Competitors/ABBYY_Vantage) — competes with · Competitors
- [Sensible Instruct](/Competitors/Sensible_Instruct) — competes with · Competitors
- [Kofax](/Competitors/Kofax) — competes with · Competitors
- [Microsoft Excel](/Competitors/Microsoft_Excel) — competes with · Competitors
- [Offshore FTE data entry](/Competitors/Offshore_FTE_data_entry) — competes with · Competitors
- [Offshore Bookkeeping](/Competitors/Offshore_Bookkeeping) — competes with · Competitors
- [Manual Spreadsheet Reconciliation](/Competitors/Manual_Spreadsheet_Reconciliation) — competes with · Competitors
- [Offshore Bookkeepers](/Competitors/Offshore_Bookkeepers) — competes with · Competitors

### What it addresses

- [entering the same 1099 data into the state portal and the federal portal separately](/Problems/entering_the_same_1099_data_into_the_state_portal_and_the_federal_portal_separately) — addresses · Problems

### Who it serves

- [boutique marble operations teams](/CompanyTypes/boutique_marble_operations_teams) — serves · CompanyTypes

### Similar Startups

- [Dematter](/Startups/Dematter) — similar · Startups
- [Bridgack](/Startups/Bridgack) — similar · Startups
- [Carvauge](/Startups/Carvauge) — similar · Startups
- [Voyagefield](/Startups/Voyagefield) — similar · Startups
- [Dalyard](/Startups/Dalyard) — similar · Startups
- [Valleymanifest](/Startups/Valleymanifest) — similar · Startups
- [Cratefield](/Startups/Cratefield) — similar · Startups
- [Kerforder](/Startups/Kerforder) — similar · Startups
- [Daleharbor](/Startups/Daleharbor) — similar · Startups
- [Pinnacleship](/Startups/Pinnacleship) — similar · Startups
- [Brokeragedome](/Startups/Brokeragedome) — similar · Startups
- [Tracelane](/Startups/Tracelane) — similar · Startups
- [Challengequay](/Startups/Challengequay) — similar · Startups
- [Clearancewing](/Startups/Clearancewing) — similar · Startups
- [Accocument](/Startups/Accocument) — similar · Startups
- [Napot](/Startups/Napot) — similar · Startups
- [Problata](/Startups/Problata) — similar · Startups
- [M](/Startups/M) — similar · Startups
- [Paperinsight](/Startups/Paperinsight) — similar · Startups
- [Chemicalport](/Startups/Chemicalport) — similar · Startups