What agents can do
Once connected, an assistant can read your organisation’s supply-chain data through a set of named tools. It chooses which to call; you just ask the question.
What it can read
Section titled “What it can read”Your supply base - farms (suppliers), the people attached to them, plots, and plot geolocations. Look up one by id or by short code, or list and filter them.
Compliance evidence - satellite assessments on plots, and certifications including the list of certification types your organisation uses.
Procurement - collection lots, trades and payments.
Aggregate statistics - farm counts, farms by region, certification coverage, risk breakdowns, non-compliance and trade totals. Ask “how many” or “by region” questions and it will use these rather than counting rows, which is both faster and more accurate.
What it cannot do
Section titled “What it cannot do”- Write anything. Every tool is read-only. There is no tool that creates, edits or deletes, so no instruction - from you or from anything it reads - can cause a change.
- See another organisation. The API key is bound to your organisation. Even if it asked for someone else’s data, the server would refuse.
- See more than you can. Access follows the key’s scopes.
Getting good answers
Section titled “Getting good answers”Ask for the number, then ask to see it. “How many plots are unmapped?” then “show me the list” - the second question confirms the first.
Use your own vocabulary. It knows a farm is a Supplier. Ask about farmers, producers, or suppliers and you’ll get the same place.
Say which organisation if you have access to more than one. If you only have one, it’s used automatically.
Prefer aggregates for totals. “Certification coverage by region” gets a statistics tool. “List every farm and count them” makes it page through thousands of records to get the same answer worse.
Verifying what it tells you
Section titled “Verifying what it tells you”Ask it which tool it used and what the raw numbers were. The tools return real figures with totals attached, and an assistant that can’t show you its source for a number is one you shouldn’t quote to a buyer.
Cross-check anything you’re about to put in a compliance document against the dashboard.
Reading the documentation itself
Section titled “Reading the documentation itself”This documentation is also machine-readable. A connected assistant can search and read these pages, so “how do I run a deforestation check?” is answered from the same source you’re reading now - not from guesswork.
See llms.txt for how any assistant, connected or not, can read these docs.