# Overview

![](/files/5CbT3qJW4zv5XxWkqO28)

### Why do you want to integrate with Kleros services?

* If you are looking for pure **Arbitration-as-a-Service**, we can help you integrate with our core service [Kleros Court](https://kleros.gitbook.io/docs/products/court).
* If you want an oracle that can provide rulings about events, connect to [Kleros Oracle](https://kleros.gitbook.io/docs/products/oracle) and get **Truth-as-a-Service** capabilities.
* If you are searching for **Data-Curation-as-a-Service**, use our [Kleros Curate](https://kleros.gitbook.io/docs/products/curate) generalized TCR product to build open community-curated lists and read from them.
* If you want to manage crypto-vs-crypto transactions or service-vs-crypto transactions in your app, have a look at [Kleros Escrow](https://kleros.gitbook.io/docs/products/escrow) contract (+ Widget & SDK) for **Escrow-as-a-Service** features.
* If you are a DAO looking to fully decentralize your governance (even the enforcement of proposal votes), check out [Kleros Governor](https://kleros.gitbook.io/docs/products/governor) and use it as **Supreme-Court-as-a-Service**.

![](/files/eM11e8uZrf5NlcmpS8pt)

### What about Kleros products built on top of those services?

* Your DeFi application can source its token data directly from[ Kleros Tokens](https://kleros.gitbook.io/docs/products/tokens) registry and even curate the tokens using badges (e.g. filtering them using preset criteria) or indirectly through [TokenLists.org](https://tokenlists.org/token-list?url=t2crtokens.eth)
* Your product can use Sybil-resistance properties of [Proof of Humanity](https://kleros.gitbook.io/docs/products/proof-of-humanity) to protect against Sybil attacks or identify your users.
* You can apply to or benefit from decentralized translation jobs in [Linguo](https://kleros.gitbook.io/docs/products/linguo) to handle the internationalization of your products.

{% content-ref url="/pages/-MTewstJdyJJK\_Kn0Jca" %}
[Types of Integrations](/integrations/types-of-integrations.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MSY1Ji1VU\_FQv8E31qI" %}
[Integrations FAQ](/integrations/integrations-faq.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MQqjOgHc9UhwJ4CDp9T" %}
[Use Cases](/integrations/types-of-integrations/1.-dispute-resolution-integration-plan/use-cases.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MR5YS1eoIeBVjP9GQF5" %}
[Integration Tools](/integrations/types-of-integrations/1.-dispute-resolution-integration-plan/integration-tools.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MXgYsxGh4ldxDVmkh6B" %}
[Live & Upcoming Integrations](/integrations/live-and-upcoming-integrations.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MRQDv347QIv5xQernH4" %}
[Scalability & Cross-chain](/integrations/scalability-and-crosschain.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MRL30KQRi7iuE9-VQKM" %}
[Kleros Analytics](/integrations/analytics.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kleros.io/integrations/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.