> For the complete documentation index, see [llms.txt](https://developer.ballotpedia.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.ballotpedia.org/dictionaries-and-terms/terms-of-use.md).

# Terms of Use

Ballotpedia content is copyrighted by Ballotpedia's editors and contributors. Licensed data sets are the proprietary and confidential property of Ballotpedia.

Licensee shall take all reasonable precautions to preserve the confidentiality of Licensor's Software and Data and shall assume responsibility that its employees and assignees will similarly preserve this information against third parties.

No right or license is being conveyed to Licensee to use or share the full data sets provided by Ballotpedia with any other company or individual. Data may be used in Licensee’s internal or external products as long as precautions are taken to protect Ballotpedia’s assets by preventing bulk downloads of the data set by third parties.

The purchase of Ballotpedia data by Licensee constitutes acceptance of these terms.


---

# 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://developer.ballotpedia.org/dictionaries-and-terms/terms-of-use.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.
