> 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/merchant-spend.md). # Merchant spend query\_spend, search\_merchants, and compare\_brands. ### query\_spend Aggregate spend for a merchant or a set of merchants over a window. Pass `merchant_id` when you have it. Otherwise pass `merchant` or `names`. `start_date` and `end_date` bound the window. `granularity` is `day`, `week`, or `month`. Omit it for one total. A weekly call covers at most 16 weeks, and a window is at most 366 days. `include_children` rolls a merchant's children into the figure. `growth` compares the window with the one before it. ### search\_merchants Search the merchant directory. `q` is the name. `limit` defaults to 5. Take the row whose name is the brand, then pass that `merchant_id` to the other tools. ### compare\_brands Two brands over the same window. `brand_a` and `brand_b` are name tokens. `start_date` and `end_date` are the window. Each side says which merchant the name resolved to. Show that name with the figure. --- # 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/merchant-spend.md?ask=&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.