> For the complete documentation index, see [llms.txt](https://docs.predicthq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.predicthq.com/getting-started/predicthq-data/data-accuracy.md).

# Data accuracy

We have a rigorous set of models and algorithms to ensure we’re providing a clean and verified data set. Our machine learning models are working day-in and day-out, which is especially crucial for event data, which is changing all of the time.

Every event in our API goes through multiple steps to ensure quality and accuracy. Some example steps are:

**Standardization:** All events follow the same schema for ease of ingestion, comparability, and compatibility.

**Aggregation:** We pull in events and entities from hundreds of different sources and compare them for quality and accuracy.

**Enrichment:** We categorize, label, and add entities to all events to help reduce noise. We also ensure all events have a date, time, and location.

**Spam Filtering:** Bad data is worse than no data at all. We ensure you only have access to events that are actually happening.

30% to 40% of events we receive are spam, add-ons, or duplicates. After filtering, our spam rate is below 0.1% - our quality-control checks consistently measure it at 0%.

**Geocoding:** Every event has a lat/long, allowing for precise mapping. Events also follow identification patterns from the open source Geonames database. For instance, all events in California have multiple IDs, of which 5332921 (the ID for California) is always included. We also provide venue name and formatted address whenever possible.

**De-duplicating:** We combine duplicate records into one reliable event. E.g. Our system may find a football game with 30,000 expected attendees. It finds eight listings of this game from five different sources. Our unique model kicks in and keeps a single event with the aggregated detail from all of the listings.

**Ranking:** See [PHQ Rank](/getting-started/predicthq-data/ranks/phq-rank.md) and [Local Rank](/getting-started/predicthq-data/ranks/local-rank.md) for what goes into our rankings. We track accuracy with a variety of metrics and we’re refining daily. The top metrics we track are: Spam rates, number of duplicated events, location, and competitive comparison.


---

# 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.predicthq.com/getting-started/predicthq-data/data-accuracy.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.