> For the complete documentation index, see [llms.txt](https://gitbook.lizh.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.lizh.ai/pricing-cost-checks.md). # Pricing and Cost Checks Before testing long-context or agent workflows, check the current model price at: ## Basic cost habits * Start with a short prompt. * Set a small output limit. * Review usage logs after the first request. * Compare input tokens, output tokens, and cache-hit tokens separately. * Increase prompt size only after the small request works. ## Why this matters Coding agents and long-context prompts can send large inputs. A small cURL or SDK test tells you whether the configuration works before you spend tokens on a full workflow. ## Recommended first test ``` Explain what this function does in 5 bullets. ``` Then move to larger tasks such as: * repository summaries, * file-by-file review, * test generation, * error-log analysis, * refactoring plans. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://gitbook.lizh.ai/pricing-cost-checks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.