# The Integrator Mental Model

The Universal Access Schema (UAS) is not an API.

It is not an SDK.

It is not a widget.

It is a **protocol primitive** — a link format that behaves more like:

* `mailto:`
* `sms:`
* `https://…/pay`
* deep links used in mobile apps

Anywhere a link can be placed, the UAS can be embedded.

It is a **deterministic addressing layer** for on-chain value:

```
https://buy.onchain.money/[chain]/[token]
```

That URL *is* the integration.

### How the mental model works

Think in terms of:

#### **1. You provide context**

The integrator chooses:

* the **chain**
* the **token contract**

#### **2. Gateway interprets the intent**

The *ONCHAIN®* Gateway:

* loads the asset
* checks verification + compliance
* prepares payment routes

#### **3. OPN executes**

OPN fulfills the intent natively on the asset’s home chain:

* no bridges
* no wrapping
* no custody

#### **4. Tokens land directly in the user’s wallet**

Fully settled, verified, final, on-chain.

### What integrators *don’t* need

* No backend server
* No signing
* No API keys
* No auth
* No rate limits
* No RPC calls
* No gas logic
* No ABI knowledge

If you can construct a string, you can integrate the Universal Access Schema.

This is why UAS integrates cleanly into:

* Telegram bots
* Discord bots
* Websites
* Wallets
* Scanners
* Launchpads
* Marketplaces
* Token pages
* Portfolio apps
* CEX off-ramping flows

The entire model collapses into one simple operation:

**Generate the URL → Display the URL → User clicks the URL.**

That’s it.


---

# 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.onchain.money/getting-started/integrating-uas/the-integrator-mental-model.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.