CommodityAI is moving beyond document ingestion into a Commodity Operating System: a structured operating layer for commodity businesses. Documents, emails, and files still matter, but they are inputs into a durable business model instead of the final destination. The core system is built around standard objects that represent how commodity teams actually work: contracts, counterparties, shipments, allocations, costs, payments, and trade finance workflows. Extracted source records provide automation and evidence for those objects.Documentation Index
Fetch the complete documentation index at: https://docs.commodityai.io/llms.txt
Use this file to discover all available pages before exploring further.
Operating Model
Commodity workflows usually span commercial terms, logistics, finance, and compliance. CommodityAI connects those pieces into one object graph:| Area | Standard objects |
|---|---|
| Commercial | Purchase contracts, sale contracts, contract legs or tranches, allocations |
| Counterparty | Customers, vendors, brokers, carriers, freight forwarders, banks, surveyors, insurers |
| Logistics | Shipments, containers, ports, schedules, shipment allocations, tracking milestones |
| Product and quality | Products, grades, packaging, quality specifications, sampling results |
| Finance | Cost items, cost templates, invoices, payments, payment allocations |
| Trade finance | Letters of credit, versions, document requirements, reviews, discrepancies, presentations |
| Reference data | Countries, ports, currencies, units of measure, futures contracts, market indices |
Standard Objects
Standard objects are first-class business records with typed fields, relationships, audit history, and tenant isolation. They are different from generic extracted records because they encode commodity-specific behavior. For example:- A contract stores purchase or sale terms: counterparty, product, quantity, pricing, delivery, payment terms, and status.
- A leg represents a shipment tranche or delivery slice with overrides for quantity, pricing, delivery, product, or payment details.
- An allocation links a purchase leg to a sale leg and tracks how much bought quantity is committed to a sale.
- A shipment represents the physical movement of goods and can be linked to allocations, containers, carriers, ports, and milestone dates.
- A counterparty represents companies across roles such as customer, vendor, broker, bank, carrier, freight forwarder, surveyor, insurer, and customs broker.
Documents as Source Material
Document ingestion remains part of the platform, but it supports the operating model:- Documents and emails are classified into source types.
- Source records are extracted with field-level provenance.
- Source records can create, update, or link to standard objects.
- Standard objects retain links back to supporting documents, files, emails, and source records.
Workflow Examples
Common workflows include:- Create a purchase or sale contract from a trade confirmation.
- Split a contract into legs for multiple shipment periods.
- Allocate purchase quantity to sale demand.
- Create a shipment from a bill of lading or booking confirmation.
- Link the shipment back to the relevant allocation.
- Add freight, insurance, inspection, handling, or finance costs.
- Track payments against cost items.
- Review a letter of credit against contract, shipment, and document requirements.
API Context
The public API exposes definitions, records, documents, and source provenance. Some teams use the API to retrieve extracted source records. Others use it to integrate CommodityAI with their system of record while CommodityAI manages the operational model in the dashboard. When reading these docs, use this mental model:- Source definitions describe document and email-derived records.
- Object definitions describe configurable business records.
- Standard objects are the commodity-specific operating objects that model contracts, logistics, counterparties, finance, and trade workflows.
- Sources connect the operational record back to the documents, files, and source records that produced or support it.