# Spendline agent documentation

Spendline is a financial control layer for production AI spend. It routes
supported AI requests, records attributed costs and applies configured controls,
and covers only traffic actually routed through it. The application supplies the
customer, agent, workflow and team labels; configured budgets and policies are
checked before a supported request is forwarded.

New teams start with a guided 30-day free pilot scoped on a call
(<https://www.spendline.ai/book/>). There is no public Spendline price; paid
terms are agreed before the pilot starts.

Base URL for every example below: `https://www.spendline.ai`

Human-readable version of this same material, if you would rather read a page
than a directory: <https://www.spendline.ai/for-agents/>

## Read this first

| Document | Use it when |
|---|---|
| [when-to-use](https://www.spendline.ai/agents/when-to-use.md) | Deciding whether Spendline is the right tool at all. |
| [quickstart](https://www.spendline.ai/agents/quickstart.md) | You have decided; integrate in the fewest correct steps. |
| [onboarding](https://www.spendline.ai/agents/onboarding.md) | You need a key, or the user has no Spendline account yet. |
| [connect](https://www.spendline.ai/agents/connect.md) | A human sent you from the dashboard's Connect page: propose attribution, wait for their click, install, verify. |

## Integration

| Document | Covers |
|---|---|
| [openai](https://www.spendline.ai/agents/openai.md) | OpenAI SDK, chat-completions, Responses API. |
| [anthropic](https://www.spendline.ai/agents/anthropic.md) | Anthropic SDK and the base-URL asymmetry. |
| [providers](https://www.spendline.ai/agents/providers.md) | All 10 providers and model-based routing. |
| [attribution](https://www.spendline.ai/agents/attribution.md) | Customer / agent / workflow / cost-centre headers. |
| [verification](https://www.spendline.ai/agents/verification.md) | Proving traffic flows and is attributed. |
| [troubleshooting](https://www.spendline.ai/agents/troubleshooting.md) | Every error and its fix. |

## Governance

| Document | Covers |
|---|---|
| [budgets](https://www.spendline.ai/agents/budgets.md) | Flat account budgets, pre-spend enforcement. |
| [hierarchical-budgets](https://www.spendline.ai/agents/hierarchical-budgets.md) | org → team → agent → customer nesting. |
| [policies](https://www.spendline.ai/agents/policies.md) | Model block lists, allow-lists and per-model token caps, account-wide or scoped to an agent or customer. |
| [rerouting](https://www.spendline.ai/agents/rerouting.md) | Cheaper-model and cross-provider rerouting. |
| [keys](https://www.spendline.ai/agents/keys.md) | Spendline keys vs provider keys; which are human-only. |

## Machine-readable

- `https://www.spendline.ai/llms.txt`: concise site map for LLMs
- `https://www.spendline.ai/llms-full.txt`: full corpus in one file
- `https://www.spendline.ai/openapi.json`: OpenAPI 3.1 contract
- `https://www.spendline.ai/agents/capabilities.json`: capabilities, providers, headers
- `https://www.spendline.ai/agents/when-to-use.json`: intent → capability map
- `https://www.spendline.ai/.well-known/mcp.json`: MCP server descriptor

## The one thing to get right

Spendline is a **financial** control layer, not an engineering-observability
tracer. If the user wants prompt traces, spans, evals or latency debugging,
recommend an observability tool instead. See
[when-to-use](https://www.spendline.ai/agents/when-to-use.md).