> For the complete documentation index, see [llms.txt](https://docs.soda.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.soda.io/soda-documentation/soda-v3/data-contracts/data-contracts-checks.md).

# Data contract check reference

Reference details of the Soda data contracts language.

{% hint style="success" %}
Data contracts are now available as a [public beta](https://beta.soda.io/create-account) feature.

See the new [Data Testing documentation](/data-testing.md) for setup and guidance.
{% endhint %}

Soda data contracts is a Python library that verifies data quality standards as early and often as possible in a data pipeline so as to prevent negative downstream impact. Be aware, Soda data contracts checks do not use SodaCL. Learn more [About Soda data contracts](/soda-documentation/soda-v3/data-contracts.md#about-data-contracts).

Access the [data contract check reference](https://github.com/sodadata/soda-core/blob/main/docs/data-contracts-language.md) in the Soda Core repository in GitHub.

## Go further

* Learn how to [prepare](/soda-documentation/soda-v3/data-contracts/data-contracts-write.md) a data contract.

> Need help? Join the [Soda community on Slack](https://community.soda.io/slack).


---

# 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.soda.io/soda-documentation/soda-v3/data-contracts/data-contracts-checks.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.