Low-code studio

Design an agent in plain language, then inspect the Agno shape underneath.

Start with a template, describe the job in your own words, then shape the brain, tools, live connections, and specialist paths directly from this workspace.

Modes

Beginner first

Natural-language planning and plain words lead the experience, with Agno details shown alongside.

Runtime target

Agno on Cloud Run

Every hosted build is shaped around the DataFluid Agno runtime and an A2A-facing surface.

Publishing stance

Private by default

Builders can explore safely first, then choose public or unlisted visibility after testing tools and connections.

Starter templates

Pick a direction

Creator share: 70% of each successful charge. The rest stays with DataFluid for platform costs, payment operations, and support.

Selected template: Country service guide. You can keep the starter prompt or rewrite it in your own words.

Choose the brain

How should this agent think?

Long context keeper

Name and promise

Make the draft understandable

People who need clear local guidance without reading technical policy language

Give it arms

Skills, MCPs, and specialist agents

2 selected
1 specialists0 live connections1 reusable skills

Saving turns on after you sign in and create your organization.

Draft overview

Specialist-ready helper

Explains country-specific processes clearly and hands edge cases to a specialist. It starts with reference library and country specialist.

Audience

People who need clear local guidance without reading technical policy language

Who this first draft is designed to serve.

Brain

Long context keeper

A better fit when the agent should read policies, FAQs, manuals, or a large knowledge base.

Price setup

$0.015 / 1K tokens

Begin with a fixed credit price per call, then introduce token-based pricing once real usage patterns are stable. Creator share: 70%.

Launch

private

This stays inside your workspace until you feel comfortable sharing it more broadly.

Unsaved draftGuest session
BrainModel | datafluid/long-context-keeper

A better fit when the agent should read policies, FAQs, manuals, or a large knowledge base.

Personality and rulesInstructions

Be calm, clear, and beginner-friendly in every answer. Escalate when the request becomes sensitive, high-risk, or policy-dependent.

ArmsTools, skills, MCP, live agents

Lets the agent answer from FAQs, policies, manuals, and company documents. Handles cases that depend on local rules, documents, or country-specific edge cases.

TeamworkTeams, routers, loops, and parallel work

Start with one main helper and only call specialists when the request is outside the safe default lane. Use a decision gate so difficult edge cases move to a specialist instead of stretching one giant prompt.

Workflow preview

How the draft works

Decision gaterouter
Decision gate

Checks whether the main helper can finish safely or should call a specialist.

Main helperagent
Specialist-ready helper

Handles the main conversation and keeps the experience friendly for non-technical users.

Reference libraryskill
Reference library pack

Lets the agent answer from FAQs, policies, manuals, and company documents.

Country specialistagent
Country specialist agent

Handles cases that depend on local rules, documents, or country-specific edge cases.

Saved drafts

Workspace history

Draft history appears here after you sign in, create an organization, and save your first builder draft.

Capabilities

Recommended arms and specialists

Reference libraryDataFluid curated
Reference library pack

Lets the agent answer from FAQs, policies, manuals, and company documents.

Official or curated source | easy
Country specialistDataFluid live agent
Country specialist agent

Handles cases that depend on local rules, documents, or country-specific edge cases.

Official or curated source | guided
4 starter brains7 starter capabilities6 editable templates

Agno preview

What this means underneath

Runtime model key

datafluid/long-context-keeper

Instructions

  • Act as Specialist-ready helper.
  • Answer in plain language first and keep technical details optional.
  • State what you can do now, what needs a connected system, and when a human or specialist should step in.
  • Prefer the attached reference library before guessing.

Tools and connections

  • Reference library pack
  • Country specialist agent

Orchestration

  • Start with one main helper and only call specialists when the request is outside the safe default lane.
  • Use a decision gate so difficult edge cases move to a specialist instead of stretching one giant prompt.

Launch advice

What to do next

  • Start private until your connections and guardrails behave the way you expect.
  • Use fixed price per call first, then refine token pricing once usage data is real.
  • Load your FAQs, policies, or operating notes early so the agent answers with your real language.