Your tools. Your agents. OneChain context.

A follow-up list, an invoice review, a freight update: your workflows need the right information. Connect them to the OneChain shipments, documents and data your team needs.

Explore the workflowsAPI, CLI or MCP?
Illustrative example · fictional data
In your tool
Which delivered shipments are still waiting for proof of delivery?
OneChainAuthorized data
Your follow-up list
  • OC-DEMO-1042POD missing
  • OC-DEMO-1086POD missing

References and documents to review before follow-up

Start with a real task.

Three examples connecting a request, the data it needs and the expected result. These scenarios illustrate workflows to define with your team.

Prepare proof-of-delivery follow-up.

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

Your routine reads shipments in the agreed scope and the document types already available. Each result includes a shipment reference so the source can be found.

Explore shipment management
Example output · fictional data

Follow-up list for review

OC-DEMO-1042
Proof of delivery missing
OC-DEMO-1086
Proof of delivery missing
OC-DEMO-1091
Document available · excluded
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.

Your assistant gathers amounts, relevant line items and available documents. The summary separates the numerical discrepancy from the supporting explanation still needed.

Explore invoice control
Example output · fictional data

Review brief

Quote
2 450 €
Invoice
2 550 €
Additional item
€100 · explanation 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.

Your tool uses authorized data within an explicit scope: period, mode and lanes. Incomplete shipments remain identifiable so unlike situations are not mixed.

Explore freight reporting
Example output · fictional data

Summary scope

Period
Selected quarter
Mode
Ocean FCL
Missing data
Shipments separated and referenced
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.

The right access for the way you work.

Business software, script or assistant: the choice depends on the tool running the workflow. Connection methods and available operations are defined with your technical team.

API

Connect your software

Exchange data between your application and OneChain. The interface contract defines the required objects, fields and operations.

Example: bring freight references and statuses into your business tool.

CLI

Integrate a script or routine

Integrate commands into a process run by your technical team. The project defines the available tooling, authentication and error recovery.

Example: prepare a list of shipments to review each morning.

MCP

Give an assistant context

The Model Context Protocol connects an assistant to authorized data and tools. The project defines accessible sources, exposed operations and required approvals.

Example: retrieve shipment documents to prepare an answer.

Explore ERP and partner data flows

From reading to action, with an explicit scope.

An assistant that retrieves information does not necessarily have permission to update a shipment. Each project separates data access, prepared work and executed operations.

Read

Define accessible shipments, documents and fields, together with the identity used to access them.

Prepare

Produce a summary or draft that keeps source references and the information to review.

Execute

Authorize only the agreed operations, with their approvals, traceability and defined error handling.

To get started, bring an example of your workflow.

The initial request, required information and expected result are enough to start the discussion. We then define access, frequency, responsibilities and cases requiring manual follow-up.

Read the security information

Guides to explore this topic with your team.

Tools and agents

Start with the workflow you want to build.

Let’s define the useful data, expected outcome and decisions your team needs to retain.

Discuss my needs