OAccess

INTEGRATION DOCS

Production Gateway

Build an OAccess Gateway link.

Use a current OAccess chain slug and the exact token contract or mint. OAccess checks current availability when the user opens the link.

Quickstart

https://buy.oaccess.link/{chain}/{contract-or-mint}
JavaScript · Base USDC
const gatewayHost = "https://buy.oaccess.link";
const chain = "base";
const contract = "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913";
const url = new URL(`/${chain}/${contract}`, gatewayHost).href;

This example uses a fixed Gateway host and an exact validated identity. For dynamic inputs, use existing Gateway-compatible chain and contract/mint validation before constructing the URL. Never use a symbol alone or accept an arbitrary host, full URL or query string as an identifier.

Examples

Examples only. Current availability is checked when the link is opened.

USDC

Base
0x833589fcd6edb6e08f4c7c32d4f71b54bda02913
Open

WETH

Base
0x4200000000000000000000000000000000000006
Open

AERO

Base
0x940181a94a35a4569e4529a3cdfb74e38fd98631
Open

USDC

Solana
EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v
Open
Example identity sources

How it works

  1. Build the URL

    Use an exact chain slug and exact contract or mint.

  2. Open the Gateway

    OAccess identifies the requested asset and checks current availability.

  3. Continue in OAccess

    If current route and eligibility checks pass, the user can continue through checkout.

Current network reference

A valid Gateway link does not guarantee that the asset exists, is currently available to buy, or is eligible for a particular user. OAccess checks the current state when the link is opened.

Exact identity rules
  • Use an exact current Gateway chain slug, not a guessed network name or token symbol.
  • EVM tokens require a full 0x-prefixed, 40-hex-character contract address. Gateway links canonicalize its casing.
  • Solana uses an exact Base58 mint representing 32 bytes. Preserve its casing; a wallet address is not automatically a token mint.
  • Native-asset markers are separate Gateway exceptions, not a replacement for a token contract or mint.
  • A link does not establish asset existence, endorsement, investment merit, route or payment availability, or user eligibility.
Common errors and recovery
Malformed identity
Correct the chain and full contract or mint. Use the Gateway link composer; never guess from a symbol.
Unsupported or unavailable network
Check the current network reference. A temporarily unavailable catalog is not proof that a network is permanently unsupported.
Unresolved asset
Check the exact address against the issuer’s source. Missing metadata or a temporary read failure does not establish that a token does not exist.
Route unavailable
An identified asset may have no current purchase route. Follow the Gateway’s current explanation; do not substitute another token silently.
Temporarily unavailable
Retry later when offered. Do not interpret an upstream outage as a token rejection.
Customer eligibility
Geography, compliance, wallet, provider and payment-method eligibility are checked for the user in the Gateway.

For developers and agents

Websites, wallets, screeners, bots and AI applications can compose the same URL from an exact identity. OAccess is developing a read-only MCP interface; no MCP connection is required to build a link. See the plain-text reference.