> For the complete documentation index, see [llms.txt](https://cullshot.gitbook.io/cullix/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cullshot.gitbook.io/cullix/reference/pro.md).

# Cullshot Pro

Cullshot can be used for free to review and rate. **Pro** unlocks the features that write files or hand them off:

* Writing XMP files
* Handoff to Lightroom, Capture One, Apple Photos or a folder
* Moving Rejects to the Trash

## Subscription

Pro is a **subscription** for Mac and iPad, **monthly or yearly**. You can try all features free for the first **7 days**.

The subscription renews automatically for the same period. You can cancel at any time in your Apple Account settings under "Subscriptions", at least 24 hours before the period ends; Pro stays active until the end of the paid period. Without a subscription, and after the trial, reviewing and rating remain free and the Pro features listed above are locked.

## Restore purchases

In the Pro window you find **"Restore Purchases"**, for example after a reinstall or on a second device.


---

# 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://cullshot.gitbook.io/cullix/reference/pro.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.
