> For the complete documentation index, see [llms.txt](https://docs.onchain.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onchain.money/getting-started/integrating-uas/dynamic-link-generation/examples.md).

# Examples

This page provides copy-paste examples of Universal Access Schema (UAS) links across common integration surfaces.

All examples follow the same base format:

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

Attribution parameters are optional and do not affect execution behavior.

***

### Minimal UAS Link

The smallest valid execution link:

```
https://buy.onchain.money/ethereum/0xabc123...
```

Use this format when attribution is not required.

***

### Wallet Integration

Example: Wallet “Buy” button

```
https://buy.onchain.money/base/0xabc123...
?utm_source=phantom
&utm_medium=wallet
```

Typical usage:

* Asset detail views
* Buy / acquire buttons
* Embedded wallet flows

***

### Bot Integration

Example: Telegram or Discord bot

```
https://buy.onchain.money/polygon/0xabc123...
?utm_source=telegram
&utm_medium=bot
```

Bots typically generate UAS links dynamically based on user-selected chain and token.

***

### Dynamic Link Table (Common Use Cases)

This table outlines how different products typically generate and use the Universal Access Schema (UAS).

In all cases, the same base format applies:

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

<table><thead><tr><th width="242.43359375">Use Case</th><th>Implementation Detail</th></tr></thead><tbody><tr><td>Telegram bot</td><td>Bot outputs a URL based on user-selected chain and token contract</td></tr><tr><td>Wallet “Buy” button</td><td>Wallet reads the active chain and asset address to build the link</td></tr><tr><td>Token website</td><td>Hard-coded CTA button linking directly to the token</td></tr><tr><td>CEX off-boarding flow</td><td>Replace bridge / DEX steps with a direct UAS link</td></tr><tr><td>Portfolio tracker</td><td>Generate a UAS link for each asset displayed</td></tr><tr><td>Community dashboard</td><td>Embed per-token links inside cards or tables</td></tr><tr><td>Marketplace</td><td>Add a “Buy Token” action to collections or listings</td></tr></tbody></table>

All implementations rely on the same deterministic link structure and require no backend, authentication, or API keys.

***

### Launchpad Integration

Example: Token launch or sale page

```
https://buy.onchain.money/ethereum/0xabc123...
?utm_source=pinksale
&utm_medium=launchpad
&utm_campaign=token_launch
```

Launchpads should use utm\_medium=launchpad.

***

### Explorer Integration

Example: Explorer asset page

```
https://buy.onchain.money/bnbchain/0xabc123...
?utm_source=explorer
&utm_medium=explorer
```

Explorers typically surface UAS links alongside token metadata.

***

### Web Application

Example: Static or dynamic web app

```
https://buy.onchain.money/polygon/0xabc123...
?utm_source=webapp
&utm_medium=web
```

Links may be generated client-side or server-side.

***

### API / Backend Generation

Example: Server-generated link

```
function buildUASLink(chain, token) {
  return `https://buy.onchain.money/${chain}/${token.toLowerCase()}`;
}
```

Example usage:

```
buildUASLink("ethereum", "0xabc123...");
buildUASLink("bnbchain", "0xdef456...");
```

***

### Email Distribution

Example: Newsletter or email CTA

```
https://buy.onchain.money/ethereum/0xabc123...
?utm_source=newsletter
&utm_medium=email
```

***

### QR Code Distribution

Example: QR-based execution

```
https://buy.onchain.money/base/0xabc123...
?utm_source=event
&utm_medium=qr
```

***

### Fully Attributed Example

```
https://buy.onchain.money/ethereum/0xabc123...
?utm_source=telegram
&utm_medium=bot
&utm_campaign=uas_links
&utm_content=inline_cta
```

This format is recommended when measuring distribution performance across surfaces.

***

### Key Notes

* Chain slugs must match the Supported Chains page exactly
* Token addresses must be lowercase
* Do not URL-encode token addresses
* Attribution parameters are optional and informational only
* Unsupported chains or tokens fail gracefully

***

### Summary

If you can generate:

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

Using a supported chain slug, you have a valid UAS execution link.

Everything else is optional.