# Universal Access Schema (UAS)

The **Universal Access Schema** is a standardized, deterministic URL format that makes any verified on-chain asset instantly reachable — anywhere a link can be placed.

No APIs.\
No SDKs.\
No contracts to deploy.\
Just a link that routes intent through the ONCHAIN® stack.

### The Format

> <https://buy.onchain.money/\\[chain]/\\[address>]

### What the Schema Represents

Each link encodes a **BuyIntent** specifying:

1. **Chain**
2. **Token contract**
3. **Verified metadata (via Smart Guardrails)**
4. **Execution path (via OPN)**

Click → Payment → Deterministic on-chain settlement.

### Supported Chains

| Chain           | Slug     | Status    |
| --------------- | -------- | --------- |
| Ethereum        | ethereum | Supported |
| Base            | base     | Supported |
| BNB Chain       | bnbchain | Supported |
| Polygon         | polygon  | Supported |
| Solana          | solana   | Imminent  |
| Additional EVMs | varies   | Planned   |

### Example Links

**Direct Token**

```html
buy.onchain.money/base/0x1234abcd…
```

**Telegram Bot**

```js
"Buy → https://buy.onchain.money/" + chain + "/" + address
```

**Website CTA**

```html
<a href="https://buy.onchain.money/polygon/0xABC...">Buy with ONCHAIN</a>
```

### What Happens When a User Opens a Link

1. Gateway loads token context
2. User selects payment method
3. Payment is verified
4. Gateway broadcasts a BuyIntent
5. OPN executes deterministically
6. Tokens settle directly to the user’s wallet

No bridges.\
No wrapping.\
No custody.\
No redirects.

Access becomes a primitive.


---

# 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/universal-access-schema-uas.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.