> 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/july.md).

# July

### API Updates

#### `parse_json` now available in the API Playground

You can now test `parse_json` directly in the [API Playground](https://gaffa.dev/dashboard/playground) using either the visual editor or the raw JSON request view. Two ready-to-run templates are available: [extract structured data from an HTML form](https://gaffa.dev/dashboard/playground?templateId=parse_html_form_to_structured_json) and [parse an academic paper PDF](https://gaffa.dev/dashboard/playground?templateId=parse_academic_paper_pdf).

### Samples, Blog & Tutorials

#### How Gaffa gives Chayn's Survivor AI access to platform policies other AI tools can't reach

[Chayn](https://www.chayn.co/) built [Survivor AI](https://tools.chayn.co/) to help people affected by image-based abuse generate takedown letters that cite the exact platform policies being violated. We published a case study on how Gaffa provides Chayn with reliable access to terms of service and community guidelines on platforms that block AI agents from reading those pages directly — all through a single API call. [Read the blog](https://gaffa.dev/blog/how-gaffa-gives-chayns-survivor-ai-access-to-platform-policies-other-ai-tools-cant-reach).


---

# 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://gaffa.dev/docs/changelog/2026/july.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.