AI Operators · Market rates & pricing intelligence
Bring Freightos Terminal benchmarks into quotation and tender reviews. Explore FBX data access, market context, comparison rules and controlled pricing workflows.
Configured for your environment. Available data interfaces, subscribed datasets and permitted retrieval actions depend on your account entitlements and agreed pricing workflow.
Discuss your Freightos workflowConfigured around your environment. Governed by your SOPs.
Where integration creates value
A pricing team needs more than a number. It needs to know whether a rate is current, which charges it includes and how closely it matches the customer’s requirements. Market-rate data can add context to a quotation, a tender response or a review of existing rates, but only when the comparison is meaningful.
The role of a Shipflow AI Operator in this workflow is to connect an authorized rate source to the work around it: understand the request, gather relevant data, highlight differences and prepare the next pricing decision under your SOPs. Your team defines the source, comparison rules and commercial authority before implementation.
Workflow opportunities
Bring relevant market context alongside accessible carrier offers and contract rates. Flag where a price looks out of step with the comparison basis, and prepare the evidence for review. Your markup, margin and customer-specific pricing rules remain separate from the benchmark.
Explore this workflowMatch tender lanes and requirements to the available rate coverage. Identify gaps, inconsistent assumptions and differences between the tender period and the source data. A short-term market observation should not silently become a commitment for the full contract term.
Explore this workflowCompare a carrier’s response with the agreed reference and highlight unclear surcharges, validity or service conditions. Prepare a focused clarification when needed. Market context supports the conversation; it does not replace the carrier’s actual offer or confirm capacity.
Explore this workflowIllustrative workflow · subject to agreed scope
Illustrative workflow, subject to confirmed data access: a team has a customer request and a proposed buy rate. It wants relevant market context before preparing its selling price.
Identify the mode, origin, destination, dates and cargo requirements. Establish whether the task needs a market benchmark, a shipment-specific rate or both.
Use the agreed source and permitted access method. Retain the dataset, observation date, retrieval time and coverage so the reviewer can understand what the comparison actually represents.
Check geography, currency, units, equipment or weight basis, charge coverage and timing as applicable. Flag an imperfect match instead of presenting a broad index as an exact lane price.
Show the reference alongside the proposed rate, explain material differences and apply only the approved pricing rules. Route exceptions to the responsible person before any customer quote is sent.
Connection approach
Freightos Terminal provides market intelligence, including the Freightos Baltic Index (FBX) for container shipping and the Freightos Air Index (FAX) for air cargo. These benchmarks provide market context; they are not an executable offer for a particular shipment.
Freightos documents an FBX Data API using date ranges, ticker selection and a daily or weekly version, with API-key and secret-key access. The permitted dataset and frequency depend on the account. Keep credentials on the server and retain the returned observation date and index identity with each comparison.
Market Updates is a separate endpoint for events, not the FBX rate series. Its permissions distinguish FBX, FAX and custom tradelane products. Confirm the subscribed coverage and permitted use before combining data. WebCargo shipment-specific rate inputs are covered in their own guide; Terminal access does not establish access to that platform.
Setup requirements
Identify the provider account, dataset, available interface and approved use. Confirm whether data may be retained, used internally or included in a customer-facing response under your agreement.
Agree the modes, lanes, dates, units and charge definitions relevant to the workflow. Define how to handle partial coverage or a benchmark that is broader than the customer’s request.
Set the acceptable age for each source and the response when access fails, an observation is unavailable or a rate expires. Do not promise one refresh frequency across different products.
Provide margin rules, review thresholds and ownership of pricing exceptions. Test mismatched units, missing charges, stale observations and changed requests before relying on the output.
Control and rollout
Keep benchmark observations, contract rates, carrier offers and selling prices distinguishable. Record any conversion or adjustment so a reviewer can trace the comparison.
Missing coverage, stale data or incompatible charge definitions should produce an explicit exception. Avoid false precision when the source cannot answer the pricing question.
A rate-data connection does not authorize changing margins, accepting carrier terms or sending customer commitments. Configure those decisions separately, with human review where required.
Common questions
No. Terminal’s market benchmarks describe market pricing context, while live or contract-rate inputs relate to available options or commercial agreements. They can inform the same workflow, but should remain clearly labeled and should only be compared on a suitable basis.
Not automatically. A quote needs the applicable buy rate, charge coverage, service conditions, validity and your commercial rules. A benchmark can help assess that information; it should not silently replace missing costs or establish a guaranteed offer.
The exact connection has not yet been confirmed for this page. Shipflow and the account owner must verify the product, access method, entitlements and supported data before implementation. This describes the workflow to scope, not a native connector or partnership announcement.
Keep the gap visible and route it to the responsible pricing team. Depending on the agreed workflow, the next step may be a carrier inquiry, a different approved source or manual review. Do not fabricate a rate or treat a mismatched index as a substitute.
Product names identify the systems discussed. This page does not imply vendor certification, partnership or endorsement. Supported actions and the implementation scope are confirmed with your team.
Start with a defined scope
Map the inputs, system access and approval boundaries with Shipflow. Agree on a useful first integration and how to verify its result.
Book a working session