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

# June 2026

- [ScraperAPI Zapier Integration](https://docs.scraperapi.com/resources/release-notes/june-2026/scraperapi-zapier-integration.md): The official ScraperAPI app for Zapier is now live in the Zapier App Directory. Bring ScraperAPI's extraction, structured-data, and crawling capabilities directly into your Zaps — no code required.
- [New n8n Templates for ScraperAPI](https://docs.scraperapi.com/resources/release-notes/june-2026/new-n8n-templates-for-scraperapi.md): We've expanded our n8n integration with new ready-to-use workflow templates, so you can start automating with ScraperAPI in minutes — no setup from scratch needed.
- [ScraperAPI Plugin for AI Agents](https://docs.scraperapi.com/resources/release-notes/june-2026/scraperapi-plugin-for-ai-agents.md): We're launching Agent Skills: a collection of 18 pre-built capability files that teach AI agents how to use ScraperAPI effectively. Skills cover everything from onboarding and product primitives to SD
- [New: Domain Credit Cost Estimator](https://docs.scraperapi.com/resources/release-notes/june-2026/new-domain-credit-cost-estimator.md)
- [Introducing AI Parser: Turn Any Web Page Into Structured Data with AI](https://docs.scraperapi.com/resources/release-notes/june-2026/introducing-ai-parser-turn-any-web-page-into-structured-data-with-ai.md): We're excited to launch AI Parser, a new API that automatically converts raw HTML pages into clean, structured JSON without requiring CSS selectors, XPath rules, or manual parser maintenance.


---

# 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.scraperapi.com/resources/release-notes/june-2026.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.
