> For the complete documentation index, see [llms.txt](https://gaffa.dev/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gaffa.dev/docs/changelog/2026/june.md). # June ### Pricing & Billing #### AI credit pricing cut for `gpt-4o-mini` Input token costs are down 50% (1 credit per 20,000 tokens, previously 10,000), and output token costs are down 75% (1 credit per 10,000 tokens, previously 4 credits per 10,000). AI-powered extraction just got significantly cheaper. #### Browser bandwidth pricing cut by 50% Residential proxy bandwidth is now billed at 750 credits per GB, down from 1,500. This applies automatically to all requests using a `proxy_location` parameter — no changes needed on your end. #### 500 free credits for all accounts Every account now includes 500 free credits, including accounts created before this change. If you signed up previously and didn't receive free credits, they've been automatically added to your account. --- # 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://gaffa.dev/docs/changelog/2026/june.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.