> 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/account.md). # Account Plan, balance, upgrade, top-up, and reporting a wrong answer. None of these read the spending record. They cost nothing, and they stay callable when the balance is gone. Arguments never name an account. The key that is signed in is the account. ### get\_plan The plan on this key. `tier` is `free`, `pro`, or `month`. Pro is live data. `month` is a purchased key with no portal account: its credits are the grant that came with the key, and it cannot upgrade or buy a pack. `unlimited` means the key skips the credit cap. It does not change the tier. ### get\_credit\_balance Credits left, and the same tier. `credits_remaining` is null when `unlimited` is true. `resets_at` is when the included monthly allowance returns. A grant does not refill then. Included credits are spent before grants. ### create\_upgrade\_checkout Opens a Stripe Checkout to start Pro. Free keys only. `interval` is `month` ($100) or `year` ($1,000). The default is month. Pro takes effect after the subscription is recorded. Call `get_plan` again to see it. A key that is already Pro should buy credits instead. ### create\_topup\_checkout Opens a Stripe Checkout to buy a credit pack. Pro keys only. `credits` is 10000, 20000, 50000, or 100000, at $1 per 1,000 credits. The default is 10,000 ($10). Returns a Checkout URL and a session id. ### get\_topup\_status Whether that Checkout has been paid. `session_id` is the `cs_…` id from `create_topup_checkout`. `paid` means the grant is on the account. `open` means the buyer has not finished. `processing` means Stripe has the payment and the grant is not written yet. `expired` means the Checkout closed unpaid. ### report\_issue Report an answer from this server that looks wrong. `what_looks_wrong` is what the user says is wrong, in their words. `request_id`, `tool`, `arguments`, and `response` identify the call. `expected` is what they expected and where that comes from. Returns a `report_id`. ### about\_american\_spend What American Spend publishes about itself: how to cite it, what the model covers, and how the data is handled. `topic` is `attribution`, `coverage`, `compliance`, `methodology`, or `all`. The default is `all`. For the dates the model covers, call `coverage`. For how many accounts it reaches, call `panel`. --- # 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/account.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.