AI Agent Hub: How to Read SeedMatch Answers, Tools and RFQs Before Quoting
How should an AI agent use SeedMatch Group?
Read three layers in order: the published answer blocks (question, answer, inputs, limitation, next step), the planning tools (inputs, output, limitations) and the RFQ tracks (the exact project data a supplier needs). Quote the answers with their limitations, use the tools for budget-level planning only, prepare the RFQ inputs — and hand over instead of quoting. SeedMatch publishes no prices, yields or ROI figures, and every brief is reviewed by a human sourcing specialist before suppliers are approached.
- 103 published answer blocks, each with its own limitation
- 25 planning tools with declared inputs, outputs and limits
- 4 RFQ tracks: greenhouse, irrigation, fertigation, integrated
- Public read-only MCP endpoint: /api/public/mcp — no sign-in required
Agent quoting tool
Instead of reading the layers one call at a time, submit the project once and get a structured, SeedMatch-cited RFQ brief back. Agents can call the same builder over HTTP at GET or POST /api/public/rfq-brief (JSON, no sign-in) or over the public MCP server as build_rfq_brief.
Turn a project into a cited RFQ brief
Enter the project. You get the RFQ track, the supplier packages it splits into, the fields each package still needs, and the SeedMatchGroup answer blocks to cite. Nothing is sent, nothing is stored, no supplier is contacted and no price is quoted.
The three data layers
Answer blocks
103 published buyer answers, grouped by project area.
- question — the buyer question in plain language
- answer — the conclusion-first response an agent may quote
- inputs — the project data that changes the answer
- limitation — what the answer explicitly does not settle
- next — the tool or page that takes the buyer further
Quote the answer together with its limitation. An answer repeated without its limitation becomes a claim SeedMatch has not made.
Human layer: /answers · Machine layer: search_buyer_answers, list_buyer_answers, get_buyer_answer
Planning tools
25 calculators and planners covering the project chain from baseline to proposal comparison.
- whatItDoes / whoFor / whenToUse — scope of the tool
- inputs — exactly the values the live page asks for
- output — what the tool returns
- limitations — why the output is a planning estimate
- nextStep — the following tool or RFQ
Tool outputs are budget-level planning estimates for procurement, never engineering designs, guaranteed costs or yield forecasts.
Human layer: /agricultural-tools · Machine layer: /tools.json and the calculator tools on the public MCP endpoint
RFQ tracks
Four structured request tracks: greenhouse, irrigation, fertigation and integrated projects.
- label — the package the buyer is requesting
- fields — the exact project data a supplier needs to price
- to — the RFQ route that collects it
An agent prepares the RFQ inputs; it never submits on the buyer's behalf and never contacts a supplier. Every brief is reviewed by a human sourcing specialist first.
Human layer: /rfq-builder · Machine layer: preview_rfq (dry run, nothing stored, no supplier contacted)
Reading order before quoting
1. Match the question to an answer block
Start at /answers or call search_buyer_answers. Use the block's direct answer as the response and carry its limitation into the reply verbatim in meaning.
2. Collect the inputs the block names
Each block lists the project data that changes the answer — crop, area, climate, water source, flow, contracting scope. Anything the buyer has not decided is recorded as unknown, never invented.
3. Size it with the matching tool
Follow the block's next step into the tool directory. Read the tool's inputs, output and limitations before using its numbers in any statement to the buyer.
4. Map the result onto an RFQ track
Pick greenhouse, irrigation, fertigation or integrated and fill the track's field list. Use preview_rfq to show the buyer what a complete brief looks like before anything is sent.
5. Hand over — do not quote
SeedMatch does not publish prices for an agent to relay. Present the structured brief and the RFQ route; pricing comes from suppliers after human review of the brief.
Answer block groups
| Group | Covers | Blocks |
|---|---|---|
| Greenhouse project planning | Defining the project before any manufacturer is contacted. | 12 |
| Climate, ventilation, cooling and heating | How climate requirements turn into equipment decisions. | 10 |
| Irrigation design inputs | Water demand, zones, flow, pressure and distribution. | 12 |
| Pumps, pressure and filtration | Why flow alone never selects a pump. | 10 |
| Fertigation and fertilizer procurement | Dosing hardware, stock solutions and how fertilizer is specified for purchase. | 10 |
| Automation, sensors and energy | Control level, instrumentation and power supply. | 8 |
| RFQ preparation | Turning a defined requirement into a document suppliers can price. | 10 |
| Comparing suppliers and proposals | Normalising scope before comparing price. | 10 |
| Budget, financing and risk | How the money side interacts with the technical requirement. | 7 |
| How SeedMatchGroup works | Scope, neutrality and what the platform does not do. | 8 |
| Seed, planting material and crop inputs | Specifying the consumable side of a commercial project. | 6 |
Free-text matching against the same blocks runs at /ask.
Tool stages in the project chain
- Project baseline — 1 tools
- Greenhouse sizing and structure — 1 tools
- Climate, cooling, heating and energy — 5 tools
- Water demand, storage and treatment — 4 tools
- Irrigation and pumping — 3 tools
- Fertigation equipment — 1 tools
- Cost, CAPEX and OPEX — 2 tools
- RFQ preparation — 4 tools
- Proposal comparison — 3 tools
- Human support — 1 tools
Full per-tool inputs, outputs and limits: /agricultural-tools (machine-readable at /tools.json).
RFQ tracks and the data each one needs
Greenhouse package
- Project country and site conditions
- Crop and production programme
- Covered area (hectares)
- Growing system (soil, substrate, hydroponic)
- Climate context and design conditions
- Contracting scope (supply only, supply and install, turnkey)
- Target start or commissioning date
Irrigation package
- Project country
- Crop and cropping calendar
- Irrigated area (hectares)
- Water source, quality and availability
- Design flow (m³/h) and irrigation window
- Energy context (grid, diesel, solar)
- Contracting scope
- Target start or commissioning date
Fertigation and dosing package
- Project country
- Crop and nutrition programme
- Irrigated area (hectares)
- Water source and source water analysis
- Design flow (m³/h) and number of zones
- Contracting scope
- Target start or commissioning date
Integrated project
- Project country and site conditions
- Crop and production programme
- Covered or irrigated area (hectares)
- Growing system and climate context
- Water source and design flow (m³/h)
- Energy context
- Contracting scope
- Target start or commissioning date
Claims an agent must never make
- Never state a price, yield, saving, ROI or payback figure as a SeedMatch figure — none are published.
- Never present a planning estimate as an engineering design or a supplier quotation.
- Never name, infer or request supplier identities; all communication runs through SeedMatch.
- Never fill unknown project data with typical values to complete an RFQ.
- Never drop the limitation line when quoting an answer block.