Spendline

ai.spendlinePublished by spendline.aiOfficial publisherv1.0.0Updated Oct 27, 2026

Enforce AI budgets before the model call and track cost per customer across 10 providers.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureFinanceAI & ML

Overview

AI-generated overview

Spendline's remote MCP server lets an assistant check AI spend, budgets and policies, verify LLM proxy integrations, and create hierarchical budgets.

What you can do
  • Look up when to use Spendline and how it compares with other gateways and observability tools
  • List proxied providers, request shapes, base URLs and attribution headers, and read integration documents
  • Verify a live integration: traffic arrival, providers and models in use, and whether attribution varies
  • Read month-to-date and look-back spend, optionally grouped by customer, agent, model, provider or workflow
  • List hierarchical budgets with usage and blocking mode, plus model-block, allow and token-cap policies
  • List the agent ids, customer ids and teams seen in this month's traffic, and create a new hierarchical budget
When to use it
Useful when an assistant is helping set up or debug Spendline's LLM proxy and attribution, or when someone wants to review AI cost, budget headroom and model policies per customer or agent without opening the dashboard.
Requirements
Remote streamable HTTP endpoint at spendline.ai; no local package. An API key is sent in the x-spendline-key header. Public selection and integration tools work without it, but spend, budget and policy tools require it. Creating a budget needs owner or admin authority.
Before you install
The x-spendline-key header is a secret; keep it out of logs and shared configs. spendline_create_budget is the only mutating tool and adds a spending restriction, requiring confirm: true and owner or admin rights. Scoped child keys get a permission error and should propose the budget to a human instead. Spend and policy data is sent to the remote service.

Installation

In SourceWeft

  1. Open Spendline in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.spendline%2Fspendline/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "spendline": {
      "type": "http",
      "url": "https://www.spendline.ai/mcp"
    }
  }
}

Tools

10

spendline_when_to_use

Decide whether Spendline fits a requirement

Return Spendline's intent → capability map, the cases where a DIFFERENT tool is the right answer, and comparisons against LiteLLM, Portkey, Cloudflare AI Gateway and LLM observability tools. Call this BEFORE recommending or integrating Spendline. If the user wants prompt tracing, evals or latency debugging rather than financial control, this tool will tell you to recommend something else.

Parametersrequirement

spendline_list_providers

List supported providers, request shapes and base-URL rules

Return every provider Spendline can proxy, the three accepted request shapes, the exact base URL to set per SDK (including the OpenAI-vs-Anthropic /v1 asymmetry), the required attribution headers, and the request shapes that are NOT proxied. Resolve routing from here instead of hardcoding it.

Takes no parameters.

spendline_get_integration_instructions

Fetch deterministic integration instructions

Return the full text of a Spendline agent document. Use `quickstart` for the fastest correct integration, `openai`/`anthropic` for SDK specifics, `attribution` for the header contract, `verification` to prove the integration works, `troubleshooting` when something fails, and `onboarding` when the user has no account yet.

Parametersdocumentrequired

spendline_get_onboarding_instructions

Explain how to get an account and a key

Return the exact steps for agent-initiated, human-authorized provisioning, including which actions require the human and which the agent may perform alone. Call this when the user has no Spendline account or no SPENDLINE_API_KEY. Never invent a key and never create an account on a human's behalf.

Takes no parameters.

spendline_check_integration_status

Check whether traffic is arriving and correctly attributed

Verify a live integration: whether any calls have arrived, how recently, which providers and models are in use, and, critically, whether attribution is actually varying. Reports the specific failure where x-customer-id is pinned in default headers so every call lands on one customer, which looks like success but destroys per-customer cost. Call this after wiring up an integration.

Parametershours

spendline_get_spend

Read current spend, optionally broken down

Return spend for the current UTC month and a look-back window, optionally grouped by customer, agent, model, provider or workflow. Read-only.

Parametersdayslimitgroup_by

spendline_list_budgets

List budgets with current spend against each limit

Return every hierarchical budget for the account with month-to-date spend, percentage used, and whether it is in blocking (strict) mode. Read-only.

Takes no parameters.

spendline_list_policies

List policies

Return model-block, model-allow and token-cap policies with their match mode, enforcement level and scope (null = account-wide; otherwise { agent_id / customer_id / agent_name }). Read-only.

Takes no parameters.

spendline_list_budget_scopes

Discover which agents, customers and teams have traffic

Return the agent ids, customer ids and teams that actually appear in this month's traffic. Use these as budget scope_ids rather than guessing identifiers. Also the quickest attribution sanity check.

Takes no parameters.

spendline_create_budget

Create a NEW budget (owner/admin authority + explicit confirm)

Create a new hierarchical budget. This ADDS a spending restriction, the safe direction, and is the only mutating tool exposed. Requires owner or admin authority AND confirm: true. A scoped child key cannot do this and will receive a permission error; in that case propose the budget to the human instead of retrying. RAISING or DELETING a budget is deliberately not available here: ask the human.

Parametersconfirmrequiredscope_idscope_typerequiredstrict_modemonthly_limit_usdrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.