harbor-expense-agent
The expense desk of Harbor Mutual, a fictitious insurer: a small, event-driven back-office AI agent (no chat)
that reviews employee expense reports through MCP tools over a SQLite system of record and writes notices. It is a
demo system under test, made for practising AI agent testing, for example with TruVelocity's practice project
(tv practice-project). It is not a product. Every name and record in it is invented.
The package carries its tool server, its seed data and an LLM factory (Anthropic, OpenAI, Azure OpenAI, Ollama, any OpenAI-compatible endpoint, AWS Bedrock, Google Gemini and Vertex AI), plus an offline rule-based stand-in for the model.
Install and run
pip install "harbor-expense-agent[all]"
harbor-expense-agent
That starts the agent on http://127.0.0.1:8700 and its MCP tools on http://127.0.0.1:9700/mcp, with the
records in ./data (expense.db, out/notices/). Ctrl+C stops both. harbor-expense-agent --help lists the
options, among them --tools-url to put a recording proxy between the agent and its tools.
Settings come from the environment and from .env in the current folder:
| Setting | Purpose |
|---|---|
DEFAULT_LLM_PROVIDER |
ANTHROPIC, AZURE, OPENAI, OLLAMA, OPENAI_COMPATIBLE, BEDROCK, GEMINI, VERTEX, or SCRIPTED, plus that provider's key and model settings |
DEFAULT_LLM_PROVIDER=SCRIPTED with LLM_SCRIPT=expense_agent.policy:factory |
No LLM and no key: a deterministic rule-based policy follows the written procedures. Nothing to install beyond pip install harbor-expense-agent |
EXPENSE_SANDBOX_TOKEN |
Enables POST /sandbox/reset (restore the seed data) for a test harness |
EXPENSE_DEFECTS |
A "buggy build" for test practice: loose_meal_limit, phantom_notice, silent_write, auto_reimburse, trace_omits_read |
Try one event
curl -X POST http://127.0.0.1:8700/events -H "X-Principal: expense-bot" -H "Content-Type: application/json" -d "{\"event\": {\"type\": \"expense.submitted\", \"report_id\": \"ER-3001\"}}"
The reply is the agent's own account of the episode: the route it chose, every tool call, its output and token use.
Source, procedures, tools and seed data: https://github.com/ShanKonduru/SystemsUnderTest/tree/main/expense-agent
Metadata
Release files for harbor-expense-agent 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| harbor_expense_agent-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for harbor_expense_agent-0.1.0-py3-none-any.whl |
Release files / harbor_expense_agent-0.1.0-py3-none-any.whl
| Download URL | harbor_expense_agent-0.1.0-py3-none-any.whl |
|---|---|
| Size | 43.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d8000c35f4dbc1ed85682c3a98d2d891e20c9e9b0910bd5cb4ed6ec090df5404
|
|
BLAKE2b-256 checksum How to use checksums |
0b2edf1366e1c5d3f072fc979e4e7c2519007d1a320a13c83e63623e50c924f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 20, 2026.
Transparency logSecurity for harbor-expense-agent 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
1 file in this release has been uploaded with provenance metadata.
Attestation for harbor_expense_agent-0.1.0-py3-none-any.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 20, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.