# Validation

Each record can be validated by the corresponding counterpart. That is:

* **Work experiences**: can be validated by companies or clients.
* **Educational experiences**: can be validated by educational institutions.

The professional will determine who the corresponding counterpart is, and they can perform the validation on-chain. In more technical terms: the user with their address registers an experience and determines an address that can (or cannot) validate that record, and anyone could verify who made the validation and whether they trust that this address is who they claim to be. For example:

> * Luciano Padovani
> * lucianito.eth (address: 0x936ed6f327b2d6fb9cdaf3ddfc9d5a4eb203cf93)
> * Record: worked at Prutopia
> * Reference to the organization: prutopia.eth (0xaa7B0ccb69E2Be14a2b19c3D265E5Cc2F18b1200)

On the other hand, prutopia.eth can validate or not this experience on-chain.

Any other party could verify that this address is the one validating, and whether they trust that prutopia.eth is indeed the organization Prutopia.

{% hint style="info" %}
The integration with ENS will be implemented in the very near future.
{% endhint %}


---

# 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.prutopia.io/core-concepts/validation.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.