Live demo
Format
UNYKORNOperating layer

Web3 & x402

Your wallet signs. The platform never holds a key.

Sign in with any EIP-1193 wallet, read positions straight from the chains, and pay for machine services with x402 — USDC on Base by signed authorisation, or SOL on the legacy rail. Every call is recorded in the evidence chain with a receipt number. Nothing here is an offer of securities; these are technology services priced in cents.

No wallet connectedAPI: checking…

Keys stay with the holder · policy runs here
Keys stay with the holder · policy runs here

Session

Sign-in is an EIP-191 message with a one-time nonce. The API recovers the signer, compares it to the address, burns the nonce and issues a 24-hour session. No transaction is created.

Address
Chain
Session
none
Receipt

Live chain reads

Read-only JSON-RPC through web3.unykorn.org, a UnyKorn-operated front door with provider failover and state-changing methods refused by policy. Balances for the connected address on Ethereum, Base and Polygon; an ERC-3643 check against any permissioned token you paste; and an XRPL account lookup.

Native balances

Ethereum
Base
Polygon
USDC · Base

ERC-3643 compliance check

Identity registry
Holder verified
Token
Balance

XRPL account

XRP balance
Trust lines
Sequence
Ledger

x402 · pay per call

Three machine-payable services. The browser asks the API, receives a 402 with the price and rails, signs a USDC TransferWithAuthorization with your wallet (no gas, no approval), and retries. The facilitator verifies and settles on-chain; the response carries the settlement and a receipt number. Agents do the same thing with an x402 client library.

$0.05

OFAC address screen

Exact match against today’s SDN digital-currency identifiers — entity, program, list version and hash.

$0.02

Engagement quote

The same bands as the Modules page, returned as JSON for procurement tooling.

$0.01

Evidence verify

Check a receipt hash against the append-only chain.

Call log

rail: —
Nothing paid yet.

Agents: GET /api/x402 lists the resources and accepted rails. Legacy clients can still pay the SOL rail by sending the transfer with memo x402:<path> and retrying with X-Payment-Signature.