# How This is Different from Web2 Systems Today

Today, connectivity between vacation rental applications occurs through thousands of APIs. API and data structures differ widely between applications. The result is that connecting to a new application is costly. The cost manifests in lengthy development cycles, maintenance to keep APIs functioning, and ultimately less connectivity between applications. In an ideal world, vacation rental applications would align around a single data standard everyone can benefit from. This can be realized through the Nite Protocol.

<figure><img src="https://lh7-us.googleusercontent.com/vHDXk5iH73xoAtYWZDlg1ItIaF7FjW_FxW2aJT7j_RVb0ExyMwZ3yEsn8YzYUzlNqNVmjcCKGlK7TYsfUGvCK3XZJZrIHCl7ARyQ3_4kPGvcTglDa28gPvIx3kr3fjeu6b7_447_onrcEPeR0IwGH88" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh7-us.googleusercontent.com/dKwoKHvHTPsuIEn9NVWmxJLwR-Pua3oDPahzoUG47pBsb7Auyh3CHQHRTk7kuWMy7_QVnYAZ2SATbtOz5wCsLDpg5WzMMVaSxb4f2BOBUimDTOqN5qs5j1vQB2Cco8eHHWfufToXsVMRvuEshol85tY" alt=""><figcaption></figcaption></figure>


---

# 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.dtravel.com/papers/nite-protocol-litepaper/protocol-design/how-this-is-different-from-web2-systems-today.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.