# Interoperability
One of the greatest challenges in complying with the Travel Rule for VASP-to-VASP transactions is ensuring interoperability across various protocols. As businesses and financial institutions adopt different Travel Rule solutions, the ability to exchange information seamlessly across these platforms becomes essential for efficient and secure transactions.
## **Ospree-to-Ospree Transfer**
When an Ospree client initiates a transfer to another Ospree client, the platform will default to using the Ospree Flow unless the client specifies otherwise.
{% hint style="success" %}
Note: Ospree is actively expanding support for additional Travel Rule protocol. Some integrations are already available, and others are on the roadmap. For the latest updates or specific requests, please contact .
{% endhint %}
## **Multi-Protocol Transfer**
When an Ospree client sends or receives a transfer from a non-Ospree client using a travel rule solution connected through a shared protocol, the platform automatically selects that protocol. If multiple protocols are available, and unless the client specifies otherwise, the platform will default to the fastest, most cost-effective, and highly compatible option.
---
# 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.ospree.io/dashboard/travel-rule/interoperability.md?ask=
```
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.