For the complete documentation index, see llms.txt. This page is also available as Markdown.

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.

Last updated