> For the complete documentation index, see [llms.txt](https://docs.americanspend.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.americanspend.com/mcp-methods.md).

# MCP Methods

The MCP methods an agent can call, and which one answers which question.

These are the methods on the American Spend MCP server. A call that fails costs nothing.

| Question                                                  | Where to read it                                               |
| --------------------------------------------------------- | -------------------------------------------------------------- |
| What did this merchant do, and how do two brands compare? | [Merchant spend](/mcp-methods/merchant-spend.md)               |
| Split spend, or follow a category                         | [Breakdowns and trends](/mcp-methods/breakdowns-and-trends.md) |
| Place, audience, and where spend went                     | [Place and audience](/mcp-methods/place-and-audience.md)       |
| Public series beside the model                            | [Benchmarks](/mcp-methods/benchmarks.md)                       |
| Which days are complete, and how big the model is         | [Model facts](/mcp-methods/model-facts.md)                     |
| Plan, credits, and a wrong answer                         | [Account](/mcp-methods/account.md)                             |

Prefer `merchant_id` once you have it. A name search is a lookup, not the first step of a spend question you can already name.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.americanspend.com/mcp-methods.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.