Multi-agent banking chatbot sample

The multi-agent banking chatbot sample project is a demo of a multi-agent chatbot powered by LangGraph, with RAG using Pinecone as a vector database. You can have a conversation with the chatbot, and it will bring back information on your (fictional) credit score, as well as give you details of credit cards available from a fictional bank.

Get the code

Get the code for the sample project. You can find this project by cloning the Splunk Agent Observability Python SDK repo.The code for this project is in the /examples/agent/langgraph-fsi-agent/after folder.

The code for this sample is available in Python, and you can run this code to generate more traces, and experiment with improving the app based off the evaluations. The Python version of this app uses Chainlit to host the chatbot in a web UI.

Evaluate the app

The sample project comes with an Agent Stream pre-populated with a set of traces for some sample interactions with the chatbot - some asking relevant questions, some asking questions unrelated to the banking agents capabilities.

Investigate the Agent Stream

On-premises
SaaS

From the Splunk Agent Observability main menu, select Project > Multi-Agent Banking Chatbot. Select the Default Agent Stream.The Agent Stream is configured with the following evaluators:

For some of the traces, these evaluators are scored at 100%, showing the agents are working well for those inputs. For other traces, these evaluators are reporting lower values, showing the chatbot needs some improvements.

A set of traces with Correctness and Instruction Adherence evaluators with a range of values

Select different rows to see more details, including the input and output data, the evaluator scores, and explanations.

Run the sample app

You can run the sample app to generate more traces, and test out different agent prompts.

Prerequisites

To run the code yourself to generate more traces, you will need:

Access to an OpenAI compatible API, such as
- An OpenAI API key
- Access to an OpenAI compatible API, such as Google Vertex
- Ollama installed locally with a model downloaded
A Pinecone account. The free Starter tier is more than enough for this project. You will need your Pinecone API key.
Either Python 3.10 or later, or Node installed

To get evaluators calculated in Splunk Agent Observability, you will need:

An integration with an LLM configured. If you don’t have an integration configured, then:
- On-premises
- SaaS
1
Navigate to the Integrations page
In the Splunk Agent Observability UI, select your user profile in the upper-right corner and then select Integrations.
2
Add an integration
Locate the LLM provider you are using (or specify a custom integration), then select the +Add Integration button.
3
Add settings
Specify settings for your integration (such as an API key), then select Save changes.
1
Navigate to the Integrations page
In the Splunk Observability Cloud UI, use the main menu to select Agent Observability > Integrations.
2
Add an integration
Locate the LLM provider you are using (or specify a custom integration), then select +Add Integration.
3
Add settings
Specify settings for your integration (such as an API key), then select Save changes.

Get the code

Clone the SDK examples repo

Terminal

git clone https://github.com/splunk/splunk-ao-python

Navigate to the relevant project folder

Start by navigating to the root folder for the programming language you are using:

cd examples/agent/langgraph-fsi-agent/after

If you want to learn more about adding logging with Splunk Agent Observability to a LangGraph app, check out the add evaluations to a multi-agent LangGraph application cookbook.

The full source code for all of our sample projects is available in the Splunk Agent Observability Python SDK Examples GitHub repo.

SDK Examples

Check out sample projects using Splunk Agent Observability

Set up Pinecone

This project uses Pinecone as a vector database to power a RAG agent that retrieves data around the fictional credit cards offered by a bank. Before you can run the app, you will need to upload the documents.

Configure environment variables

In each project folder is a .env.example file. Rename this file to .env and populate the PINECONE_API_KEY value. You can leave the other values for now as you will populate them later

Upload the documents

There is a helper script in the scripts folder. Run this script to create a new index in Pinecone and upload the documents.

python ./scripts/setup_pinecone.py

This will take a few seconds, and a successful run should look like:

Terminal

Loading documents for credit-card-information folder...
...
✅ Document processing and upload complete!

Run the code

Install required dependencies

From the project folder, Install the required dependencies. For Python, make sure to create and activate a virtual environment before installing the dependencies.

pip install -r requirements.txt

Configure environment variables

In your .env file, populate the Splunk Agent Observability values.Environment variables vary depending on your deployment type. For details, see the on-premises and SaaS environment variable references.

You can find these values from the project page for the multi-agent banking chatbot sample page in the Splunk Agent Observability.

Next populate the values for your LLM:

Environment Variable	Value
`OPENAI_API_KEY`	Your OpenAI API key. If you are using Ollama, set this to `ollama`. If you are using another OpenAI compatible API, then set this to the relevant API key.
`OPENAI_BASE_URL`	Optional. The base URL of your OpenAI deployment. Leave this commented out if you are using the default OpenAI API. If you are using Ollama, set this to `http://localhost:11434/v1`. If you are using another OpenAI compatible API, then set this to the relevant URL.
`MODEL_NAME`	The name of the model you are using

Run the project

Run the project with the following command:

chainlit run app.py -w

If you are using the Python version, the app will be running at localhost:8000, so open it in your browser.You can ask the agent questions about:

The different credit cards offered by the bank
Your credit score

Improve the app

The insights you viewed earlier suggested improving how the supervisor agent processes messages, especially with credit scores. You can try this out to see what issues might occur:

Terminal

You: What is my credit score?
Assistant: I cannot answer that question.

Despite there being an agent to get the users credit score, it is not always used. To improve the agent, have a look at the agent prompt defined in the following file:

src/splunk_ao_langgraph_fsi_agent/agents/supervisor_agent.py

In this file is the current agent prompt:

bank_supervisor_agent = create_supervisor(
    model=ChatOpenAI(model=os.environ["MODEL_NAME"], name="Supervisor"),
    agents=[credit_card_information_agent, credit_score_agent],
    prompt=(
        """
        You are a supervisor managing the following agents:
        - a credit card information agent. Assign any tasks related to
          information about credit cards to this agent
        Otherwise, only respond with 'I don't know' or 'I cannot answer
        that question'.
        If you need to ask the user for more information, do so in a
        concise manner.
        """
    ),
    add_handoff_back_messages=True,
    output_mode="full_history",
    supervisor_name="brahe-bank-supervisor-agent",
).compile()

This supervisor agent prompt explicitly mentions the credit card agent, but not the credit score agent. You can encourage the supervisor agent to use the credit score agent to get better results:

"""
You are a supervisor managing the following agents:
- a credit card information agent. Assign any tasks related to
    information about credit cards to this agent
- a credit score agent. Use this to get the users credit score.
Otherwise, only respond with 'I don't know' or 'I cannot answer
that question'.
If you need to ask the user for more information, do so in a
concise manner.
"""

Try this new prompt out and see how the agent responds.

Terminal

You: what is my credit score
Assistant: Your credit score is 550. If you have any other questions or
need further assistance, please let me know.

Once you have asked a few questions, head back to the Splunk Agent Observability UI and examine the new traces. You should see the evaluators improving.

Run the sample app as an experiment

Splunk Agent Observability allows you to run experiments against datasets of known data, generating traces in an experiment Agent Stream and evaluating these for different evaluators. Experiments allow you to take a known set of inputs and evaluate different prompts, LLMs, or versions of your apps. This sample project has a unit test that runs the chatbot against a pre-defined dataset, containing a mixture of sensible and irrelevant questions:

dataset.json

[
    {"input": "What are the cashback rewards offered by the Orbit Credit Card?"},
    {"input": "What is my credit score?"},
    {"input": "What is the APR for balance transfers on the Orbit Credit Card?"},
    {"input": "What credit cards am I eligible for?"},
    {"input": "What can I do with my credit score?"},
    {"input": "Recommend me a good book."}
    ...
]

You can use this unit test to evaluate different supervisor agent prompts for your app.

Run the unit test

Use the following command to run the unit test:

python -m pytest test.py

Evaluate the experiment

The unit test will output a link to the experiment in the Splunk Agent Observability UI:

Terminal

Experiment multi-agent-chatbot-experiment 2025-07-15 at 00:48:11.842 has
completed and results are available at
<your-splunk-ao-deployment-url>/<id>/experiments/<id>

Follow this link to see the evaluators for the experiment Agent Stream.

Try different supervisor agent prompts

Experiment with different supervisor agent prompts. Edit the supervisor agent prompt in the app, then re-run the experiment through the unit test to see how different supervisor agent prompts affect the evaluators.

Compare experiments

If you navigate back to the experiments list using the breadcrumb, you can select Compare Experiments, then select multiple rows to compare the experiments in detail.

Next steps

Logging with the SDKs

Learn how to log experiments

Learn how to run experiments with multiple data points using datasets and prompt templates

Splunk Agent Observability logger

Log with full control over sessions, traces, and spans using the Splunk Agent Observability logger.

Log decorator

Quickly add logging to your code with the log decorator and wrapper.

Splunk Agent Observability context

Manage logging using the Splunk Agent Observability context manager.

How-to guides

Log Using the OpenAI Wrapper

Learn how to integrate and use OpenAI’s API with Splunk Agent Observability’s wrapper client.
Python

Log Using the @log Decorator

Learn how to use the Splunk Agent Observability @log decorator to log functions to traces
Python

Overview

SaaS deployments

Get Started

Observability

Evaluators

Tokenomics

Signals

AI Assistant

Luna Studio

Experiments

Agent Control

Annotations

Integrations

Security

References

Get the code

Evaluate the app

Investigate the Agent Stream

Run the sample app

Prerequisites

Get the code

SDK Examples

Set up Pinecone

Run the code

Improve the app

Run the sample app as an experiment

Next steps

Logging with the SDKs

Learn how to log experiments

Splunk Agent Observability logger

Log decorator

Splunk Agent Observability context

How-to guides

Log Using the OpenAI Wrapper

Log Using the @log Decorator

Create Traces and Spans

SDK reference

Python SDK Reference

Get the code

​Evaluate the app

​Investigate the Agent Stream

​Run the sample app

​Prerequisites

​Get the code

SDK Examples

​Set up Pinecone

​Run the code

​Improve the app

​Run the sample app as an experiment

​Next steps

​Logging with the SDKs

Learn how to log experiments

Splunk Agent Observability logger

Log decorator

Splunk Agent Observability context

​How-to guides

Log Using the OpenAI Wrapper

Log Using the @log Decorator

Create Traces and Spans

​SDK reference

Python SDK Reference

Evaluate the app

Investigate the Agent Stream

Run the sample app

Prerequisites

Get the code

Set up Pinecone

Run the code

Improve the app

Run the sample app as an experiment

Next steps

Logging with the SDKs

How-to guides

SDK reference