The $SX token, layer by layer

01 / WHAT RUNS TODAY

Call these before you read anything else here.

curl -s https://api.proxies.sx/v1/gateway/pool/stock     # listed and connected counts per country
curl -s https://api.proxies.sx/v1/x402/pool/pricing      # USDC price per GB, both networks
curl -s https://api.proxies.sx/v1/x402/status            # component status, no uptime promise implied
curl -s https://agents.proxies.sx/compute/facts.json     # compute status and term

Status words on this page: live (reachable now at the URL given), built (code at a named path, not yet serving a customer), in test (deployed to a test path, with the measured thing named), planned (on the plan, no code yet), decided (an owner decision recorded on the date shown).

Counts are from the 2026-11-03 23:21 UTC read of GET /v1/gateway/pool/stock and are per country only. Call the endpoint for the current figure.

Peer traffic enters through relays in two regions, EU and US, each with an assigned spare; the peer API runs on a two-node tier, and the database sits on its own host.

When copies disagree, the live API wins, then the product skill.md, then this page.

02 / THE PLAN, WITH STATUS WORDS

The direction we recorded on 3 November 2026 is that $SX becomes the settlement unit for each access layer we operate or build: peer SDK supply, customer access, Apple Silicon compute, resellers and the layers we have not built yet. Status: planned. The table has seven rows: the five access layers, then lock periods and contributions. Each row names what the token would do, the condition that moves it, the contract an agent reads and what an agent must not invent; the owner decides each move and we date it here. We have paid no $SX to anyone under any row.

How a row moves

We change a status only by adding a dated line to the record in 04. A row whose date changes shows the old date beside the new one. A planned row is not a commitment to launch; it may change or never launch. We have not set a month for any row; when we set one, it appears in the row with the date we set it. No staking, reward or checkout API exists, and an agent that constructs one from these rows is wrong.

The $SX token page ↗ $SX is not required to use the services. Holding it creates no service credit and no claim on company revenue. No activation date, no promised return.

03 / ORDER OF OPERATIONS

Useful service → Measured earnings → Settlement → Optional $SX step (planned)

We published this order here on 29 September 2026, after the token page had said on 25 September 2026 that a completed payout record comes before any reward is called live; neither has changed. Status: decided. A supplier's earnings settle in USDC, SOL or BTC first; an optional $SX quote may follow settlement, and we publish a budget and a completed payout record before we describe the reward as live. Existing earnings, payout terms and verified transfers remain authoritative; do not infer a payout from a token balance.

Where this sits in the thesis →

04 / PUBLISHED AND SHIPPED

What we published and what shipped since, with a place to check each. When a date changes, the old date stays in the row beside the new one.

We add the next row when the next thing ships.

05 / BOUNDARIES

06 / FOR AGENTS

The machine contract for this page is /sx-token/ecosystem.md, with the same rows and boundaries. A planned row has no endpoint. A live row names one, and until this page shows a row as in test or live with a date, treat it as planned.

READ THE UNDERLYING CONTRACTS

• The $SX token page
• /sx-token/ecosystem.md
• /thesis/
• /pool/skill.md, /peer/skill.md, /build/skill.md
• /compute/facts.json, /compute/skill.md
• /compute/vs-nosana-io-net-akash/
• /system-map/, /status/