Features explained
Connecting a knowledge source
On a paid plan, GPTree can answer from an outside knowledge base and cite the exact passage it used. The first built-in source is the Scryfall Magic: The Gathering card database.
Most AI tools answer from whatever the model happened to memorize, which is why they sound confident and get specifics wrong. A knowledge source flips that around: GPTree pulls the fact from a connected database and cites the exact passage it used, so you can see why the answer is right and where it came from.
Knowledge sources are available on paid plans (Pro and Team). Once you have one, there is nothing to switch on: when a question matches a connected source, the assistant searches it, answers from what it found, and shows the citation.
The first source: Scryfall
The first built-in source is Scryfall, the public Magic: The Gathering card database. Ask "what does Lightning Bolt do" and the answer comes from the card's own rules text, with a citation you can open, rather than from the model's memory. The card data is refreshed every day, so it stays current on its own.
Cited answers and live lookups
Two kinds of answers come back, and GPTree is clear about which is which:
- Cited. Card rules and text point back to a stored passage you can check. Every claim carries its source.
- Live. Fast-changing data, such as a card's current price, is looked up live and shown as an indicative current value, not a citation, because a price is only true for a moment.
If a source has nothing to say on your question, GPTree tells you it could not find it instead of filling the gap with a guess. That honesty is the point of a cited answer.
Your own documents
Teams can also push their own documents into the knowledge engine through the knowledge API, so the same cited answers work over your internal material. Documents pushed this way stay private to your account and are readable only by the person who added them.
In crew runs, too
Agents working in a crew run can search the same knowledge sources while they work. When an agent's output relies on a passage, it cites it the same way, and each task output in the run view lists its sources underneath. Click a number to read the exact passage. A citation the search never returned is removed before the output is saved, so every source you see is one the agent was actually given.
More sources will follow the same shape: connect it once, then just ask, and the answer arrives grounded in something you can open and read for yourself.