FarmTempo Global
Match what was shipped against what was received.
A person makes every final call.
Our reconciliation engine links a supplier’s shipment records to a buyer’s receiving records, lists what is missing or does not agree, and shows the evidence behind every link. It never marks a match “confirmed” — that word is reserved for a person. Built in Korea; so far measured only on synthetic records derived from Korean auction lots, with no real customer pairs yet.
Pilot
A 30-day pilot on your own records, free of charge
This is about the matching your team does by hand today — shipments against receipts, one document at a time. FSMA 204 traceability records become mandatory on July 20, 2028; that is a side effect here, not the reason.
Two sets of records, 30 days each
Shipping records and receiving records for one trading pair. Five columns are enough: date · document number (invoice, BOL or PO) · item code or name · quantity and unit · counterparty. We do not take prices, margins or customer lists, and counterparty names can be replaced with codes.
The same four deliverables we run today
A link table · an exception list showing who needs to resend what · the evidence for every row · an export file for your existing system.
Free · under NDA · files returned or deleted
Your files are returned or deleted when the pilot ends. Results are cited only as an anonymous case unless you agree otherwise.
How it is judged — agreed before we see your data: the share of lines closed without a person, the share a person overturned, and whether the exception list led to real re-requests. We do not present accuracy figures from synthetic sets as performance.
The form opens in Korean; writing in English is fine. You can also email agriynd@farmtempo.com.
Where it runs today · Korea
Fresh produce is still bought by phone call. We are building the record layer underneath.
FarmTempo is a produce price and ordering infrastructure in Korea. Buyers — grocery stores, restaurants, school kitchens — check wholesale prices and repeat past orders. Sellers — growers and distributors — collect incoming orders by delivery date and share shipping status. FarmTempo does not take a transaction fee and does not handle payments.
Small buyers and growers settle price, quantity and delivery date deal by deal. The agreement exists, but it lives in phone calls and notebooks. FarmTempo turns each agreement into a structured record that both sides can see.
Price, in one place
Wholesale market auction prices, KAMIS reference prices and egg farm-gate prices on one screen, refreshed daily.
The agreement, as a record
Buyers post conditions, sellers propose a unit price, a person confirms the award. Confirmation, statement and receipt documents are generated from that record.
Delivery, as a status
Drivers tap depart and arrive from a link without signing up. Buyers confirm receipt. Delays carry a reason.
Status board
What runs today, and what does not yet
We list the gaps next to the working parts. Prediction performance figures are not published on this page.
● Live in Korea
- ●Produce price board130 items listed (KAMIS wholesale) — 100 with a price in the last 30 days; items with no price for 30+ days are shown separately · 34 items auctioned across 31 public wholesale markets nationwide · 5 egg size classes
- ●7-day forecast ranges for 27 itemsCount as shown on the Tempo Ticker, which follows the server’s forecast list · public time-series models (Chronos-2 · TimesFM-2.5) · past back-test score shown · no weather data · for reference
- ●Repeat orders · order collection · delivery statusBuyer and seller screens
- ●Public MCP endpoint, read-only40 tools · no authentication
- ●Item & lot API · v1Korean market codes and USDA Market News commodities resolve to one canonical item · no prices returned
- Every value carries two axes: how it was made — source text, rule, model estimate or person-provided — and how far it is verified — confirmed, provisional, conflict or insufficient evidence.
match_evidencestates what the rule saw. Exact matches only; an unregistered or ambiguous input comes backmatched: falsewith verificationinsufficient. The API does not guess.- “Confirmed” is human-only, enforced at the database — a confirmer name and timestamp are required, and draft or engine names are rejected.
- Lot identity is resolved only within one jurisdiction. Across borders, records are linked at the item level and no further.
- ●Shipment ↔ receipt reconciliation engine · v1File-based deliverables: links, exceptions, evidence and export files
- Four outcomes per pair: rule match, provisional, conflict, insufficient evidence. The engine never writes “confirmed” — that word is reserved for a person.
- Item, lot and transaction are judged as three separate columns, never merged into one score.
- Split receipts are not treated as errors.
- Tolerances live in per-item domain packs, not in engine code.
- Measured so far on synthetic contrast sets only — see “Not yet”.
- ●US terminal market prices (USDA AMS Market News)Terminal market reports FV010 / FV020 / FV030 from eleven US cities — New York, Los Angeles, Chicago, Philadelphia, Boston, Atlanta, Baltimore, Detroit, Miami, Columbia and Asheville — for apples, tomatoes, Chinese cabbage, onions and potatoes, plus Asian pears — including Korean Singo pears quoted in New York, Chicago and Los Angeles. Cities are never merged or averaged. Shown on this page, in the app under Prices → US prices, in the public REST API and as MCP tools. Quoted ranges reproduced as published, with the report number and report date on every row. Reuse and attribution confirmed by USDA AMS on September 29, 2026.
- ●US shipping point prices (USDA)FOB prices as produce leaves the growing area — Yakima, Idaho Falls, Inwood and Benton Harbor for apples; Idaho Falls for potatoes and onions; Phoenix and Orlando for tomatoes; Phoenix for Chinese cabbage. Seven reports. A different level of the trade from terminal market prices — we never merge the two or subtract one from the other.
- ●US arrival volumes (USDA Movement reports)Daily arrivals at US terminal markets and ports of entry — commodity, country of origin, port of entry, transport mode and volume in pounds, across 14 reports. Reuse confirmed by USDA AMS on September 29, 2026. These are arrivals, not sales and not transaction-level records.
- ●Two patent applications filed in Korea10-2026-0098735 · 10-2026-0151392
○ Not yet
- ○Real customer shipment and receipt records — 0 pairsThe reconciliation engine has been measured on synthetic contrast sets derived from Korean auction lots. Those figures are internal and are not published here.
- ○FDA traceability (FSMA 204) event recordsRecord schema drafted; no shipping or receiving events are collected yet
- ○Unit conversion APIDesign stage — not live
- ○Reviewer-facing queue and dashboard for the reconciliation engineReview is recorded from the command line today, and a person’s review never overwrites the engine’s own outcome
- ○PaymentsFarmTempo does not collect or settle transaction payments
- ○Tempo Orbit (satellite field observation)A separate service, under validation — observations are marked “before validation” until the hypothesis verdict on January 10, 2027. It does not predict price or yield.
As of November 8, 2026. Counts re-measured against the live API on that date.
US context
Why the record layer travels
Produce records only line up across systems when two things agree: what the item is and what unit it was sold in. A 10 kg box in Seoul and a 50 lb carton in Los Angeles need a shared identity before any price or traceability record can be compared.
We have separated item identity from Korea-specific data sources. Korean auction and survey codes and USDA Market News commodities now resolve to the same canonical item, and each mapping carries both how it was made and how far it is verified — a person’s confirmation and a rule’s output are never recorded as the same thing. Korean and US lots stay separate records — they are linked only at the item level, never lot to lot.
Unit conversion between package types and FDA traceability event records are not built yet.
Compliance date of the FDA Food Traceability Rule, which requires records for foods on the Food Traceability List. Of the items we cover, fresh tomatoes are on the list; onions and potatoes are not. Korean lot records are not presented as evidence of US compliance.
US market data
US terminal market prices, as reported
USDA AMS Market News publishes quoted wholesale price ranges for US terminal markets. We carry eleven cities; the table below shows New York, and every city is available in the app and the API. Korean-origin quotes can be picked out on their own — in the app with Korean origin only, in the API with origin=South Korea. We reproduce them exactly as published — no averaging, no rounding, no currency or weight conversion — and every row carries the report number and the report date it came from. These are US wholesale quotes in USD; they are never mixed into the Korean price board.
Loading the latest published report…
In the app these sit under Prices → US prices, kept apart from the Korean price board — the currency, the unit and the nature of the price all differ, so we never convert or merge them. The same screen has a Shipping point view — FOB prices as produce leaves the growing area, a different level of the trade that we never merge with or subtract from terminal prices — and an Arrivals view built on USDA Movement reports: what arrived at US terminal markets and ports of entry, by commodity, country of origin, port and transport mode, in pounds as reported. Arrivals are not sales and not transaction-level records, and totals shown there are added up by FarmTempo, not published by USDA.
Source: USDA AMS Market News · Specialty Crops Market News Division, USDA Agricultural Marketing Service · mymarketnews.ams.usda.gov. Reuse and attribution confirmed by USDA AMS on September 29, 2026. USDA does not endorse FarmTempo. The same values are available at /api/usda/latest and as public MCP tools.
For developers
API
What you can call today, and what is designed but not built. They are marked separately.
MCP · public
● LiveRead-only tools for Korean produce prices, auction markets, seasonal patterns and event signals. Korean-language data, KRW prices.
# tool list GET https://api.farmtempo.com/mcp/info # MCP endpoint · no auth · 40 tools https://api.farmtempo.com/mcp/public # partner endpoint · X-API-Key · 2 tools https://api.farmtempo.com/mcp/private
See the API docs (Korean, with an example call and a trimmed live response per endpoint), the OpenAPI spec and terms for the REST endpoints behind these tools.
Item & lot API · v1
● LiveResolves item names and source codes to a canonical item, and checks whether identifiers from different record systems refer to the same item or the same lot. Every value carries two axes — how it was made and how far it is verified — plus the evidence string the rule used. An unregistered or ambiguous input comes back matched: false; the API does not guess. Lot identity stays inside one jurisdiction; across borders the link stops at the item level. No prices, internal lot IDs or confirmer names are returned. Also available as MCP tools.
# https://api.farmtempo.com GET /api/v1/items GET /api/v1/items/resolve?q= GET /api/v1/items/{id} POST /api/v1/lots/reconcile # ── free text to a canonical item ── GET /api/v1/items/resolve?q=tomato { "matched": true, "canonical_item_id": "tomato", "matched_by": "name_en", "confidence": "confirmed", "value_state": { "value_origin": "rule_computed", "verification": "provisional", "usable_scope": "with_provisional_label" } } # ── do two source codes mean one item? ── POST /api/v1/lots/reconcile { "identifiers": [ { "kind": "item", "jurisdiction": "KR", "source": "garak_kat_std", "code": "08/03/01" }, { "kind": "item", "jurisdiction": "US", "source": "fda_ftl", "code": "tomatoes_fresh" } ] } { "summary": { "requested": 2, "matched": 2, "unmatched": 0 }, "groups": { "same_lot": [], "same_item": [ { "canonical_item_id": "tomato", "indexes": [0, 1], "jurisdictions": ["KR", "US"] } ] } } # ── an unknown code is not guessed ── { "matched": false, "reason": "'garak_kat_std' has no code '99/99/99' registered (not matched by inference)" }
Responses above are trimmed from live calls on September 28, 2026. Reason strings are returned in Korean; the English above is a gloss. Full schema: OpenAPI spec.
Reconciliation engine · v1
● Live · file-basedMatches a supplier’s shipment records against a buyer’s receiving records and returns links, exceptions, evidence and export files. It runs as a deliverable generator, not as an HTTP endpoint; a reviewer-facing queue and dashboard are deliberately not built yet.
# links · exceptions · evidence · exports make deliver SET=<set> # per pair · three separate judgments item_judgment same | different | unknown lot_judgment same | different | unknown trade_status rule_matched | provisional | conflict | insufficient
Tolerances come from per-item domain packs, not from engine code. Measured on synthetic contrast sets only.
US prices, shipping point & arrivals · USDA
● LiveQuoted wholesale price ranges from USDA AMS Market News terminal reports in eleven US cities (33 reports), reproduced as published. Each city is its own market — we never merge or average across cities. No averaging, rounding, currency or weight conversion. Every row carries the report number and the report date. Also available as MCP tools (usda_catalog, usda_prices, usda_latest, usda_sp_catalog, usda_sp_latest, usda_sp_prices, usda_movement, usda_movement_catalog, usda_movement_summary).
# https://api.farmtempo.com GET /api/usda/catalog GET /api/usda/latest?market=HC&commodity=Tomatoes # HC = Los Angeles GET /api/usda/latest?market=NX&commodity=Apple%20Pears&origin=South%20Korea GET /api/usda/prices?commodity=Apples&from=2026-09-01 # one row, trimmed { "report": { "slug": "NX_FV020", "slug_id": 2315 }, "report_date": "2026-09-25", "commodity": "Tomatoes", "package": "5 kg/11 lb flats", "origin": "Canada", "currency": "USD", "price_basis": "quoted_range", "price_low": 22.0, "price_high": 24.0, "attribution": "Source: USDA AMS Market News" }
# shipping point (FOB, a different level from terminal) GET /api/usda/shipping-point/latest?commodity=Apples GET /api/usda/shipping-point/catalog # arrivals (USDA Movement reports) GET /api/usda/movement?origin=South%20Korea GET /api/usda/movement/catalog GET /api/usda/movement/summary?group_by=commodity
Source: USDA AMS Market News. Reuse and attribution confirmed by USDA AMS on September 29, 2026 for the terminal price reports and, in a second reply the same day, for the movement, shipping point and other-city terminal reports we cited; USDA does not endorse FarmTempo. Arrivals are not sales and not transaction-level records; totals from /summary are added up by FarmTempo, not published by USDA.
Unit API · v1
○ Design · not livePlanned endpoint for converting between package units (for example a 10 kg box and a 50 lb carton). Calls to this path do not work today.
POST /api/v1/units/convert
Published so partners can comment on the design before it is built.
Access & pricing
● LivePublic endpoints: no key. Prices, auctions, canonical items, lot reconciliation and the public MCP endpoint are open — nothing to sign up for.
Partner key (X-API-Key): request via Contact. Send a message from the contact form and pick the “API” type; you will get a reference number. Partner keys unlock the write tools on /mcp/private.
Pricing: not yet set. We have not priced the API. Nothing is billed today, and we will publish terms here before that changes.
# rate limits public 10 req/s per IP, bursts to 30 → 429 partner 1,000 calls/day per key → 429 # machine-readable GET /api/spec/public # OpenAPI GET /api/spec/terms # limits · sources GET /api/keys/me # your key status
Read the terms and data sources before you build on it — some KAMIS series stopped updating after March 31, 2026, so every response carries its own as-of date.
Talk to us
Investors, partners and developers — send a message and you will get a reference number. We reply by email.