URSY.ORG
The public ledger for verified AI commerce

An open record of what AI actually sold.

One verifiable ledger for every specialist entity on the network — not one shop. The first entity handshake is now verified: teas.co.uk is live as URSY-001, discoverable in UK and Europe scope layers, with token minting still locked until release.

URSY network · live registry 01 VERIFIED
{{ e.domain }}
node {{ e.node }} · {{ e.spec }}
{{ e.status }}
Check-in · live Claims locked
Verified entities
01
Tokens minted
0
Discovery places
83,102
Ledger bricks
07
The network ledger

Every entity URSY monitors

This is not one shop's ledger. It is the public record of every specialist entity registered on the network — the domain truth spines URSY tracks and will mint verified tokens for on completed, checked evidence. It now has one handshake-verified entity and a live discovery graph.

EntitySpecialismTuckersScopesState
{{ e.domain }} node {{ e.node }} · {{ e.region }}
{{ e.spec }} {{ e.tuckers }} {{ e.scopes }} {{ e.status }}
Network total  ·  1 verified entity  ·  4 discovery placements  ·  0 active alliances  ·  0 minted tokens ledger head 000000 · 6 receipts · sealed 2026‑06‑21

The handshake is live; the mint is not. Minting remains locked until 22 July 2026 and token claims stay disabled until the daily claim feed is released. The public ledger can therefore show real entity and discovery-placement proof while keeping the token counts honestly at zero.

Node 001 · handshake verified

Inside the first entity's record

Every node opens a record like this one. teas.co.uk is URSY-001, the first registered URSY network entity. Its public key handshake is verified, its six-hour check-in channel is live, and its token claim channel is deliberately left closed until the daily feed is released.

Handshake
verified
teas.co.uk Specialist tea · UK · URSY-001
TokenHeldState
{{ t.name }}
{{ t.sub }}
0
awaiting mint
Discovery placements  4 · active alliances 0 check-ins 3 · receipts 6 · mint locked
Live proof layer

The first entity is live

URSY now has a verified entity, a public contract, a signed receiver, public-safe receipts and a cron audit that checks the truth spine every six hours. The important restraint is visible too: the mint is still closed and active alliances are still zero.

Verified entity
teas.co.uk

URSY-001 · first registered network entity · UK/Europe discoverable · active alliances 0.

Contract seen
p6 synced

25d1b209aed1a1bca9977380091d99d416ba8e6514b96e6992f17d7ff62d6555

Receiver state
check-in live

6 check-ins · 3 calibration claim batches · 9 signed receipts.

Safety boundary
mint locked

Public ledger proof live · zero minted tokens until the daily feed is released.

Entity discovery

Not a flat directory. A world graph.

URSY can discover entities by world, continent, country, region, county, town, sector, speciality and service radius. TEAS is discoverable in Europe, the UK, UK online retail and UK tea. Those are discovery placements, not active alliances.

Place graph
83,102
Countries
252
Scope layers
12
Local orphans
0
01 · World layer

Every country has a place

The seed holds world, continent, country, nation, region, subregion, county, metro, city and town scopes. A machine can ask for a business by place without URSY pretending every business is national.

02 · UK/Europe scope

The UK layer is active

Teas.co.uk is placed in Europe, United Kingdom, UK online retail and UK tea discovery layers. Online sellers can sit above one town only when their declared/evidenced scope supports it.

03 · Local services

Radius stops nonsense

A plumber, builder, hairdresser or local service can belong to a town, county or service-radius discovery layer. URSY will not flatten a local provider into national discovery unless it declares national coverage.

04 · Business fit

Built for different shapes

Online retail, tea, food and drink, home services, trades, local hospitality, professional services and specialist publishers can all be modelled by combining sector, place and evidence.

Ask it naturally

The discovery API already answers natural questions such as “who is relevant for tea in the UK?” or “who is relevant for plumbing near Crowborough?” The first returns Teas; the second returns the local discovery layer without inventing a national plumber.

tea in the UK home services near Tunbridge Wells directory audit
How the ledger works

Report. Verify. Issue.

Three steps, once a day, for every node. The entity reports; the ledger checks; only what survives the check is recorded.

STEP 01

Report

Once a day, a registered entity sends the ledger its proven events from the last 24 hours — sales, refunds, chargebacks and citations — each carrying its evidence.

STEP 02

Verify

The ledger checks each event independently against the real payment record. No verification, no token. A machine cannot talk its way into a token.

STEP 03

Issue

What passes becomes a permanent, public token on the entity's record. What fails is rejected and logged. Nothing is self-reported.

The instruments

Five URSY confirmations, every one evidence-backed

Teas keeps its own local AI appreciation tokens. URSY keeps the entity-level confirmation mint for registered entities only. The first URSY family is shown here for teas.co.uk, and every count remains zero until the mint opens.

URSY.ORG - confirmed sale token - for: TEAS.CO.UK

Recorded only when a registered entity submits sale evidence that URSY can verify against the signed claim and payment reference.

URSY.ORG - confirmed AI citation token - for: TEAS.CO.UK

Recorded when AI citation evidence survives follow-back or review. URSY also runs its own site citation route: Ursy.org - Citation Appreciate Token.

URSY.ORG - confirmed refund token - for: TEAS.CO.UK

Recorded openly when a verified sale is later refunded. It sits beside the sale confirmations rather than being buried or netted away.

URSY.ORG - confirmed chargeback token - for: TEAS.CO.UK

Recorded openly when a sale is later charged back. The uncomfortable record stays visible because accountability has to include the bad data.

URSY.ORG - confirmed Tucker token - for: TEAS.CO.UK

The only URSY confirmation that can move once as an alliance commitment. It is one-hop only, retractable by the grantor, non-delegable and never market language.

The credibility token

What a Tucker is


A Tucker is earned, not bought. An entity earns one only when a qualifying settled value event survives its reversal window — a sale, booking, appointment, ticket, invoice, membership, donation or other approved contribution with credible evidence. Sales are the first live rail; the rule is transaction-backed proof, not market language.

A Tucker has no price and no market. It is not money; it is proof. It can be transferred once — a single hop, and it cannot be passed on again. And it can be withdrawn: if an alliance starts to degrade, you take your Tuckers back.

Face value
£0
Earned by
Settled value
Survival
Reversal window
Transfers
Once only
The protocol

How an alliance forms

Two entities form an alliance by committing Tuckers to one another. The commitment is visible, one-hop only, and retractable by the grantor.

Worked example · commitment model · one hop only
teas.co.uk
now wears
10 × biscuits.biz tucker
10 each way
handshake
biscuits.biz
now wears
10 × teas.co.uk tucker

Each side commits 10 of its own Tuckers to the other to open a handshake. Each then wears the other's tokens on its public record. The alliance is visible and provable because those Tuckers were transferred once as a deliberate commitment.

If an alliance degrades, either side withdraws its Tuckers and it ends. Joining a larger group requires commitment to the existing members, which keeps every alliance deliberate. Deeper alliances, where entities share data to defend one another, come later.

Domain mesh

Commerce proof and knowledge proof live together

URSY is not only for shops. A plumber can prove booked work. A charity can prove donations or memberships. A Devon geography guide can prove knowledge value through verified citations and become a Knowledge Partner to relevant alliances without entering the Tucker matrix.

Commerce member

Sales, bookings, tickets, invoices

Transaction-backed entities use settled value evidence to earn Tucker and take part in the alliance matrix.

Contribution member

Donations, memberships, subscriptions

A charity does not pretend a donation is a sale. It proves a settled contribution through a credible rail.

Knowledge partner

Citation reputation

Knowledge entities pair with alliances by subject and geography. Citation tokens stay soulbound and never convert into Tucker.

URSY-owned domains also connect through the URSY Domain Mesh. URSY.org is the canonical mesh authority; ursy.com is planned as the business education node. Mesh bulletins are signed read-only updates that other URSY domains can verify and store locally.

Why this exists

Premium intent


AI customers don't type three keywords any more. They describe exactly what they want, in detail — they arrive with high, specific intent.

A business alone can only answer for itself. A trusted alliance of complementary specialists can answer the whole intent: the right additions, the right recommendations, from sources that vouch for each other on the record. Higher intent, met properly, by businesses that have earned the right to recommend each other.

That is what this ledger is for.

Public accountability

The colony leaderboard

Every verified token also counts toward the AI provider that earned it. Over time this becomes a public ranking of which AI systems drive real, durable commerce — by verified outcome, not by claim. It is empty today.

{{ p.rk }}{{ p.name }} 0
Join the network

Build your own truth-spine entity

Bring your products. The setup wizard plumbs in your own ledger, branded to your own domain, with the same verification built in — a domain specialist that serves humans on desktop and machines over API, all relying on one trusted source of truth. The software is free — you pay only for hosting that scales with how busy you are.

Start at ursy.AI Visit ursy.com
Free software · domain-native tokens · same verified ledger