Skip to content
NOMA
docs

How NOMA works

Everything below is the launch behaviour. Numbers on the site are read from the chain and the API; nothing here is a promise of a value we do not serve.

on this page
§01 — what

What NOMA is

NOMA is a private commerce layer for digital services. You buy with crypto, you never create an account, and identity is either a wallet signature or an order key.

  • · eSIM · AI credits · VPN · proxy · VPS · gift cards
  • · payments are wallet-to-wallet; the platform never holds your funds
  • · staked $NOMA earns the weekly rewards (once the token is live)
§02 — orders

How an order works

  1. 01
    Choose

    The product page lists exactly what you provide and what you receive, before you pay anything.

  2. 02
    Pay

    An invoice locks the price for 15 minutes. It names the exact amount and the fixed NOMA address.

  3. 03
    Receive

    Payment is confirmed on-chain, the supplier is called, and the deliverable is stored encrypted — shown only to whoever holds the order key.

  4. 04
    Prove (optional)

    Attach the order to a wallet and it appears in your order index. Otherwise the order key is the only credential.

§03 — payments

Payments

Pay in USDG (the canonical stablecoin on Robinhood Chain) or ETH. The buyer pays wallet-to-wallet into one fixed NOMA address; the platform never holds a balance for the buyer.

methodwallet → NOMA address
identifierthe exact invoice amount
custodynone · no escrow
price lock15 minutes

Each invoice has a unique amount — send exactly it. The watcher confirms after a few blocks and only then fulfills. A payment that arrives after the invoice expired is refunded in full to the payer.

§04 — order key

The order key

The order key is returned once when the invoice is created; only its hash is stored. It is the only way back to an anonymous order — and it cannot be recovered or reset. That is the cost of having no accounts.

The key lives in the URL fragment, so it never reaches the server logs. If you paid from a connected wallet, the order also appears in your order index.

§05 — delivery

Delivery

The deliverable is encrypted at rest and shown only to the order-key holder. What you get depends on the category:

eSIMan LPA activation string + QR
VPShost, root password, ssh one-liner
VPNaccount + WireGuard and OpenVPN configs
Proxygateway, ports, credentials, examples
AI creditsan API key with its credit limit
Gift cardthe code and any PIN
§06 — rewards

Rewards & staking

$NOMA trades on Pons with a 1% creator tax. At cycle end the Reward Engine Safe claims the fees, swaps them 50/50 into ZEC and the Stock of the Week, and streams both into NomaStaking over 7 days.

  • · only staked $NOMA earns
  • · unstaking stops earning immediately; withdraw after a 7-day cooldown
  • · rewards stream over 7 days and never expire; claim anytime with claimAll
  • · staking and the reward engine activate when the token launches
§07 — agent

The agent

The agent searches the NOMA catalog only. It compares products and returns selectable options. It never pays on its own — checkout is the normal flow.

§08 — privacy

Privacy

An order shares only the fields the supplier needs to deliver it. The checkout shows them before you pay; the order page keeps the receipt. Deliverables are encrypted at rest and are never assembled for anyone but the order-key holder.

§09 — faq

FAQ

Do I need an account?
No. Identity is a wallet signature or an order key.
What if I lose the order key?
The order cannot be recovered. If you paid from a connected wallet, it stays in your order index.
What if the supplier fails?
The order is refunded automatically to the payer address.
Which assets can I pay with?
USDG or ETH on Robinhood Chain. USDG is pegged at $1.
Is the reward engine live?
Not yet. It activates when $NOMA launches and staking is deployed.
Where are the contract addresses?
In the footer, once they exist. Nothing is deployed until launch.
§10 — ai gateway

AI gateway

AI credits are sold as a NOMA API key, not an OpenRouter key. The OpenRouter key stays on our server; your key calls NOMA, and NOMA calls the model. The endpoint is OpenAI-compatible, so any SDK or client that accepts a base URL works.

base urlhttps://usenoma.org/api/ai/v1
authBearer noma_sk_…
compatibleOpenAI chat completions
usageOpenRouter cost + platform fee
balancethe amount you paid
expiryshown on delivery · 365 days by default

Request

curl https://usenoma.org/api/ai/v1/chat/completions \
  -H "Authorization: Bearer noma_sk_..." \
  -H "Content-Type: application/json" \
  -d '{"model":"<model>","messages":[{"role":"user","content":"hello"}]}'

OpenAI SDK

from openai import OpenAI

client = OpenAI(base_url="https://usenoma.org/api/ai/v1", api_key="noma_sk_...")
print(client.chat.completions.create(
    model="<model>",
    messages=[{"role": "user", "content": "hello"}],
))

Usage and balance

Your balance is the amount you paid. Each request is billed at the model's OpenRouter cost plus the platform fee, and the balance is debited per request. When it reaches zero, requests are refused until you buy another key.

curl https://usenoma.org/api/ai/v1/usage \
  -H "Authorization: Bearer noma_sk_..."

Rules

  • · the key is a bearer secret; anyone holding it can spend the balance
  • · the key expires; unused credit expires with it
  • · prompts go to OpenRouter and the model provider; NOMA stores tokens and cost, not message bodies
  • · only the models listed on the product page are accepted
  • · no refunds after the key is issued; a leaked key can be revoked from the admin side
  • · use the HTTPS endpoint for real keys; a bearer key over plain HTTP is exposed