Quickstart
Create an agent, test it in Fluo, then choose whether to embed it or call it from your application.
This quickstart gets an agent ready for a production path without forcing you to learn every platform object first.
1. Create a Project
Open platform.fluo.one, sign in, and create a project. A project contains your agents, knowledge bases, contexts, keys, and usage.
2. Create an Agent
In your project, create an agent and give it:
- A clear name, such as
Support Assistant. - A short purpose, such as answering product and account questions.
- Instructions that define tone, boundaries, and escalation behavior.
Keep the first agent narrow. It is easier to sell, test, and improve a specific assistant than a broad one.
3. Add Knowledge
Create a knowledge base and upload the content the agent should use. Good first sources are:
- Public help-center articles.
- Product FAQs.
- Policies the assistant is allowed to quote.
- Short implementation guides.
Avoid uploading private internal planning docs unless they are intended to influence public answers.
4. Test in Fluo
Ask the same questions your users will ask:
- What can this product do?
- How do I set it up?
- What happens when something fails?
- When should I talk to a human?
Update the agent instructions and knowledge until the answer quality is consistent.
5. Choose a Release Path
| Goal | Recommended path |
|---|---|
| Add chat to a website quickly | Embed a Chatbot |
| Use the agent from your backend | Call the API |
| Build a custom streaming UI | Streaming Threads |
6. Review Security
Before you ship, check:
- Browser embeds use publishable embed keys, not full secret API keys.
- Allowed domains are configured for public widgets.
- Rate limits and spend caps are set.
- Tools that perform writes are intentionally enabled for public users.
See the Production Checklist for a concise launch review.