Connect your tools and agents to freight operations.

IT and freight teams: prepare follow-ups, reviews and summaries with authorized OneChain data. Define the access method, sources and human decisions for your workflow.

Illustrative example · fictional data
Your request
Which delivered shipments need proof of delivery?
OneChainAuthorized sources

Shipment references · delivery statuses · available documents

A list prepared for your review
  • OC-DEMO-1042Proof missing
  • OC-DEMO-1086Proof missing

You review the documents and decide on follow-ups.

API, CLI, MCP: choose access around the task.

Your tool needs to find a document, compare amounts or prepare a list. Start with the required data, then define the suitable interface and authorized operations.

API

Access data from your application

An application programming interface lets software read data or request an operation. For OneChain, the accessible shipments, fields and operations are defined for each project.

Define: which references and statuses does your application need to read?

CLI

Prepare a routine with your technical team

A command-line interface lets a script run a process. We assess the tooling for your project, its authentication and error recovery.

Define: when should the routine run, and who handles incomplete shipments?

MCP

Scope the tools an assistant can use

The Model Context Protocol describes how an assistant accesses tools and their data. The connection method to OneChain is chosen with your technical team for the workflow.

Define: which sources can be read, and which actions require approval?

Connect your ERP, WMS or partners One AI access point to your forwarder network

A prepared result. A named decision-maker.

Each project defines your assistants’ read and action permissions: data accessed, work prepared and authorised operations.

Read

Limit the shipments, documents and fields accessible to the identity used. Identify missing or outdated data.

Prepare

Gather references, documents and discrepancies in a list or draft for review.

Approve

Name the person who reviews the sources and decides on a follow-up, dispute or shared report.

Execute

Define authorized actions separately, together with approval, the expected record and error handling.

Bring a task and an example output.

During scoping, your IT and operations teams define frequency, accessible sources and the approval owner. Incomplete shipments need a clear review process.

Read the security information

From a request to a result for review.

Explore three workflows: missing documents, an invoice discrepancy and a freight review. Each fictional example sets out the request, required sources and human decision.

Prepare proof-of-delivery follow-up.

Each morning, identify delivered shipments without proof of delivery and prepare a follow-up list.

The proposed routine compares delivery status with documents in authorized shipments. An unknown status needs review: it does not prove delivery.

Explore shipment management
Example output · fictional data

Follow-up list for review

OC-DEMO-1042
Delivered · proof missing
OC-DEMO-1086
Delivered · proof missing
OC-DEMO-1091
Status unknown · review needed
Sources to connect
  • Shipments and references
  • Delivery statuses
  • Available documents

Your team’s decisionThe team reviews the selected shipments and decides which follow-ups to send. Automatic sending is a separate action to define in the workflow.

Gather the evidence before disputing a charge.

Retrieve the quote and invoice for shipment OC-DEMO-1042 to explain the €100 discrepancy.

The proposed workflow gathers the quote, invoice and their references. An extra handling charge accounts for the discrepancy; its supporting evidence is still needed.

Explore invoice control
Example output · fictional data

Review brief

Quote · QUOTE-DEMO-1042
€2,450
Invoice · INV-DEMO-1042
€2,550
Extra handling
€100 · evidence needed
Sources to connect
  • Selected quote
  • Shipment invoice
  • Line items and amounts

Your team’s decisionThe finance team reviews the evidence and decides whether to approve or dispute. The summary prepares that decision; it is not payment approval.

Bring context to your reporting.

Prepare the quarterly ocean-freight review, keeping incomplete data separate.

The proposed workflow selects a common period, mode and set of lanes. In this example, 10 of 12 shipments have cost data; the other two stay outside the comparison.

Explore freight reporting
Example output · fictional data

Summary scope

Scope
12 shipments · quarter · ocean FCL
Comparable costs
10 shipments with cost data
Identified exclusions
2 shipments without costs · to complete
Sources to connect
  • Shipments and lanes
  • Available costs
  • Dates and milestones

Your team’s decisionThe freight manager reviews the scope, exclusions and interpretation before sharing the summary.

Tools and agents

Which freight workflow do you want to build?

Describe the task, required data and expected result. We will scope access and approvals with your IT and freight teams.

Scope my workflow