# Interoperable Identity

**Partners**

<div align="left"><figure><img src="/files/HL3Q7ifkA7mJDeAQrg1f" alt=""><figcaption></figcaption></figure></div>

* **Innerworks**: Validates initial user requests and provides user authentication.&#x20;
* **Trident3**: Manages identity requirement verification between platforms.&#x20;
* **Privado ID**: Provides secure credentialing and identity verification services.
* **Space & Time**: Coordinates the identity verification process and handles on-chain record keeping.&#x20;

**Example Use Case**\
\
An IRA retirement provider project (ETZ) is using Privado ID to verify users credentials and wants to interact with Franklin Templeton’s (FT) Benji platform which uses its own credentialing process. In this instance a ETZ user initiates a request to use USDC from its IRA to purchase Benji.

**Benefits**

* Seamless integration between different identity verification systems
* Maintains regulatory compliance across platforms
* Provides complete audit trail of identity verification
* Enables secure cross-platform transactions
* Preserves user privacy while ensuring compliance

**Sequence**

{% stepper %}
{% step %}
ETZ user initiates request - (assume user balances are verified).

{% endstep %}

{% step %}
Innerworks validates that the request comes from a known user.

{% endstep %}

{% step %}
Innerworks sends that validation to SxT.

{% endstep %}

{% step %}
SxT triggers a request asking Trident3 for FT’s Identity Requirements.

{% endstep %}

{% step %}
Trident3 sends the FT requirements to SxT and SxT verifies it has received them.

{% endstep %}

{% step %}
SxT triggers a request for Privado ID to provide the required credentialing.

{% endstep %}

{% step %}
Privado ID sends the required credentials to Trident3.

{% endstep %}

{% step %}
Trident 3 sends the required credentials to FT.

{% endstep %}

{% step %}
A summary of all of these actions, along with the verifications is batched and put on chain.

{% endstep %}

{% step %}
The ETZ user can now purchase Benji.

{% endstep %}
{% endstepper %}


---

# 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://learn.w3.io/cookbook/identity-and-compliance/interoperable-identity.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.