Upload the files
The refund policy, the tone guide, the product sheet. Up to 5 MB each.
Product · Build
Attach knowledge files to agents and projects. Their text joins every chat, so answers draw on your material.
The agent stopped guessing your refund policy the week the actual document rode into every chat.
The refund policy, the tone guide, the product sheet. Up to 5 MB each.
PDF and Word files are converted to plain text at upload, stored with the file.
Every chat with that agent or project includes the material. No setup per conversation.
A support agent that has read your actual refund policy gives a different answer than one guessing from the internet. Files make the difference.
This is direct file grounding: the leading text of your documents rides along with the conversation. No pipeline to configure, nothing to re-index by hand.
PDF, Word, Markdown, CSV, JSON, and text, up to 5 MB each. We extract the text at upload and store it with the file.
No. The leading text of your documents rides along with the conversation, the same text every turn. Replace the file when the document changes.
Split a context window between system prompt, files, and output.
Test whether a document fits the model you plan to use.
What a small team can run before anyone is hired to run it.