Skip to main content
Not looking for Agents, and just want to connect to your favorite AI models, like ChatGPT?Check out this resource instead: Chatbots
Quick SummaryAI agents in Xano refer to autonomous entities designed to perform tasks by leveraging artificial intelligence. Your Xano Agents can integrate with your database, APIs, tasks, and functions, as well as external systems.These agents can process data, make decisions, and execute actions without human intervention. AI agents in Xano can efficiently handle a variety of applications, from chatbots to data analysis tools, enhancing automation and productivity.
39ea4c72-image

Introduction to AI Agents
5dd2e627-image

Tools for Agents & MCP Servers

​
What are Agents?

AI agents in Xano serve as integral components for building intelligent, automated systems as a part of your backend. These agents are designed to function autonomously, interacting with various elements of your app such as your APIs and database, as well as external systems, to streamline operations and enhance efficiency. AI agents can intelligently interpret inputs, process data, and deliver actionable outputs, all without the need for continuous human oversight. Agents in Xano can leverage any of the most popular AI models once you provide an API key, such as:
  • OpenAI
  • Grok
  • Anthropic / Claude
  • Google Gemini
You can leverage the same visual builder you’re used to using today to create workflows and functions that enable the agents to interact seamlessly with databases and external systems. With these foundational elements in place, AI agents can execute complex tasks, perform data analysis, or even serve as intelligent chatbots, making them versatile tools for a wide range of applications.

​
Building Agents in Xano

1

From the left-hand navigation, click AI, then Agents

2

Click + Add Agent

3

Fill out the necessary information

Please note that not all models support certain features such as:
  • Structured outputs
  • Reasoning
  • Tool calls
In addition, some models may support individual features, but not combinations of features, such as:
  • Structured outputs with tool calls
  • Tool calls with reasoning
This is not an issue with Xano or with your agent builds — this is dictated by the model you’re using. If you encounter errors when testing your Agents, try using a different model and check to make sure that your model supports the feature(s) you have enabled, especially if you are using more than one of these features together.

​
All Agents

Name

Give your agent a name that describes its role or primary function.Example: Order Processing Agent

Description

Internal-only field describing what your agent does.Example: Analyzes incoming orders, decides on fulfillment priority, and triggers shipping workflows.

Agent Settings

Define dynamic inputs the Agent can accept from Function Stack workflows and reference environment variables.Use {{ $args.propertyName }} for workflow inputs and {{ $env.variableName }} for environment variables.

Model Host

Select the AI model host for the agent.Options
  • Anthropic (Claude)
  • OpenAI
  • Google Gemini
Xano offers limited free Gemini credits for development. Choose Xano Test Model (Free Gemini Credits) to use them. Credits do not reset once used.

Max Steps

Define how many steps the Agent can execute to complete its task.Example: 5

System Prompt

Core instructions that define your Agent’s role, capabilities, and behavior.Example
You are a helpful AI Agent that completes tasks accurately. When you need additional information to complete a task, use the available tools. Never make assumptions.

Prompt Type

The type of prompt provided to the Agent.
Either messages (a list of prior conversation messages) or prompt (a single standard prompt).Example: messages or prompt

Prompt

Additional context and instructions sent with each request.Example Please help the customer with their inquiry: {{ $args.customer_message }}. Their account ID is {{ $args.account_id }}.

Structured Outputs

Configure the Agent to return responses in a specific JSON format using your predefined schema.Toggle the checkbox to enable or disable.

Output Schema

Define the JSON structure for structured outputs.Example keys
  • text
  • user_email

Tags

Categories for organizing your Agents.Example tags
  • contact
  • messaging

Request History

Controls logging of requests to Request History.Modes
  • Inherit Settings: Uses the currently defined workspace settings
  • Disabled: No logs recorded
  • Enabled: Logs requests with options for storage limits

​
Anthropic Settings

API Key

Your Anthropic API key.
Get your key here.Example: sk-ant-apixx-xxxxxxxxx-xxxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-xxxxxxxx

Model

The Anthropic model to use.
List of available models here.Examples
  • claude-opus-4-1-20250805
  • claude-3-7-sonnet-latest

Temperature

Controls randomness of the response.Higher values (e.g. 0.8) make output more random; lower values (e.g. 0.2) make it more focused.Examples: 0.1, 0.9

Send Reasoning

For reasoning models, when enabled, Claude creates thinking content blocks showing internal reasoning before the final response.Example: Defaults to true

Thinking

Enables extended thinking and specifies a thinking budget.
More info here.Example JSON
{
  "type": "enabled",
  "budget_tokens": 10000
}

​
Google Generative AI (Gemini) Settings

API Key

Your Gemini API key.
Get your key here.Example: AIzaSyDaGmWKa4JsXZ-HjGw7ISLn_3namBGewQe

Model

The Gemini model to use.
List of available models here.Examples
  • gemini-2.5-pro
  • gemini-2.5-flash-lite

Temperature

Controls randomness of the response (creativity).
Higher = more random, lower = more deterministic.
More info here.Examples: 0.1, 0.9

Use Search Grounding

Grounding with Google Search connects Gemini to real-time web content and enables verifiable sources.
Works with all available languages.
Not all models support search grounding.
More info here.Example: on or off

Thinking

Enables extended thinking and specifies a thinking budget.
More info here.Example JSON
{
  "thinkingBudget": 1024
}

​
OpenAI Settings

API Key

Your OpenAI API key.
Get your key here.Example: sk-Am1rLw7xUwGxGuBasGsNt3BlbkFjdBgBUgBBK5BuG9y6oWWB

Model

The OpenAI model to use.
List of available models here.Examples
  • gpt-4.1-mini
  • gpt-5

Temperature

Controls randomness of the response.Higher values (e.g. 0.8) make output more random; lower values (e.g. 0.2) make it more focused.Examples: 0.1, 0.9

Reasoning Effort

For reasoning models, sets how much effort the model spends thinking during generation.Examples: low, medium, high
4

Add some tools to your Agent

An Agent needs tools to function — the tools are essentially single functions that the Agent can perform, such as looking up user data or cancelling a subscription.

​
Using Existing Function Stacks as Tools

1

In the existing function stack, click the ⋮ settings icon in the upper-right corner of another function stack, and click Use As AI Tool

2

Choose the Agent or MCP Server you'd like to add the tool to, and give it a name. This name is what the command will be, so make sure it's understandable

3

A new tool will be created in your chosen destination with a function to call the function stack

Xano will not make a copy of your existing function stack; instead, it will use a Run Endpoint function and call that function stack internally. This is ideal, so you only have to maintain one function stack.

A tool created from an existing API endpoint

4

Head to your tool's settings and add instructions

Instructions are important to have so the AI models and clients interacting with this tool understand how to use it.

​
Creating Tools from Scratch

1

From the left-hand navigation menu, click Tools, then + Add Tool

2

Fill out the required information

  • Name
    • Give your tool a recognizable name. This is also the command that will be used to execute your tool.
  • Description
    • This is an internal-only field just for you to describe the purpose of the tool.
  • Allow Connections
    • Enable or diffsable connection to this specific tool
  • Add Tag
    • Tag your tools for easier search across your Xano workspace
  • Authentication
    • Determine if this tool requires an authentication token
  • Tool Instructions
    • These instructions are what your clients will use to understand how to send requests to the tool, and what the expected result will be. Markdown format is recommended.
3

Build your tool's function stack

If you haven’t already, make sure you’re familiar with Building with Visual Development
4

Add the tool to an Agent or MCP Server

From the Agent or MCP Server, choose + Add Tool and select the tool you just created.

​
Structured Outputs

Structured Outputs are used for providing a specific format that you need your agent to return its result as. This is especially useful when you are calling agents from other agents and want to ensure that the output from Agent 1 is clear and easy to understand for Agent 2. You can add structured outputs to your Agent in the settings by checking the Structured Outputs checkbox, and then clicking + Add Output Schema to build your output schema.

​
Example Agents

​
🤖 Customer Support Agent

Purpose This Agent is designed to handle customer inquiries that don’t typically need human interaction. Tools An Agent designed for this purpose might have the following tools available:
  • Get User Information
    • Retrieves user information from the database
  • Update User Information
    • Retrieves existing user information from the database, and updates it per a user’s request, such as changing their phone number or address
  • Send Verification Code
    • This tool could be used as a secondary security measure to verify that the request is coming from the user that the data belongs to
  • Change Subscription
    • Based on the user’s request, this could be used to stop an upcoming renewal, or cancel a subscription immediately. Because Agents excel at ‘fuzzy logic’ depending on certain circumstances, this could also be used for things like churn prevention — dynamically offering the user a discount to stay, for example
  • Search Documentation
    • Calls an external API from your chosen documentation platform to search your product documentation in an attempt to solve the user’s query without human intervention
  • Create Support Ticket
    • In the case that the Agent does not have the necessary tools to solve the user’s concerns, create a support ticket for human intervention

​
Agent Configuration

Parameter NamePurposeExample
NameGive your agent a name that describes its role or primary functionCustomer Support Agent
DescriptionInternal only field for describing what your agent doesHandles customer inquiries that don’t typically need human interaction. Can retrieve user information, update accounts, send verification codes, manage subscriptions, search documentation, and escalate to human support when needed.
Agent SettingsDefine dynamic inputs the Agent can accept from Function Stack workflows and reference environment variables{{ $args.customer_message }}, {{ $args.user_id }}, {{ $args.ticket_priority }}, {{ $env.SUPPORT_API_KEY }}
Model HostSelect the AI model host for the agentClaude Sonnet 4
Max StepsDefine how many AI requests the Agent can execute to complete a task8
System PromptThe core instructions that define your Agent’s role, capabilities, and behaviorYou are a helpful Customer Support Agent that resolves customer inquiries efficiently. Always verify user identity before making account changes. Use available tools to gather information and resolve issues. If you cannot resolve an issue, create a support ticket for human intervention. Be polite, professional, and solution-oriented.
PromptAdditional context and instructions sent with each requestCustomer inquiry: {{ $args.customer_message }}. User ID: {{ $args.user_id }}. Account status: {{ $args.account_status }}. Please help resolve this customer’s issue while following security protocols.
Structured OutputsConfigure your Agent to return responses in JSON format using structured outputs and your predefined schema✅ Enabled
Output SchemaDefine the JSON structure for agent responsesresponse_message, action_taken, ticket_created, follow_up_required
TagsCategories for organizing your Agentscustomer-service, support, automation
Request HistoryControls logging of tool requestsEnabled: Logs requests with options for storage limits

​
Example Interaction Flowcharts

​
1. Account Information Request

“What’s my current subscription plan?“

​
2. Address Change Request

“I need to update my shipping address”

​
3. Billing Question

“Why was I charged twice this month?“

​
4. Technical Issue

“The app keeps crashing on my phone”