trenchcoat
Free · no sign-up
Website report · 30 Oct 2026

usoe.tech

“USOE — United States Oil Exchange | American oil, on-chain”

Template-written 15 evidence items Code reader analysed 7 scripts
What this means for you

usoe.tech talked to 2 outside services on a first visit.E6E5

  • Tech check: the site claims live data / analytics, and its public page shows matching evidence.E14E10
  • Tech check: the site mentions on-chain / smart contracts and trading / swaps / bots, but we found nothing behind those in what its public page loads.E12E13
  • We saw no known analytics or advertising services load on the first visit.E1
  • 2 cookies were set in your browser, all by the site itself.E7E8

Tech check

What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.

Nothing found on the public page

On-chain / smart contracts

“…N · USOE NAMED THE SETTLEMENT LAYER FOR AMERICAN CRUDE ON-CHAIN · GOES LIVE NOVEMBER 7 BULLETIN · USOE NAMED THE SETTL…”E12

No matching code, calls or services in what loaded for us.

Nothing found on the public page

Trading / swaps / bots

“…III Pipeline — Holder dashboard — Barrel proof feed — Market maker program PHASE IV Reserve — Institutional access — Vaul…”E13

No matching code, calls or services in what loaded for us.

Evidence found

Live data / analytics

“…seeded — Coinbase listing PHASE III Pipeline — Holder dashboard — Barrel proof feed — Market maker program PHASE IV Re…”E14

Calls to its own backend: /__l5e/trackeventsE10

Calls its own backend /__l5e/trackeventsE10
Wallet code none seen
Contract calls in its code none seen
Talks to AI services none seen
Live connections none seen

What it is

  • The Internet Archive has never saved this site, so it is probably new.E15
  • The site describes itself as: “$USOE turns American crude into a portable, on-chain claim. Barrel-backed, built for markets that never sleep. Goes live November 7, 2026.”E2
  • It's built with React (common tools for building web apps).E9
  • While loading, it called 1 endpoint on its own servers, such as /__l5e/trackevents.E10

Where your data goes

FontsDownload typefaces. 2
fonts.gstatic.comGoogle Fonts: fonts 4×E6
fonts.googleapis.comGoogle Fonts: fonts 1×E5

How key features work

Loading its content

Its content loads from its own API while you browse (/__l5e/trackevents).E10

/__l5e/trackevents

Cookies and storage

Names only. We never store the values.

CookieSet forKeptWhose
__dplE7usoe.tech about 1 daysthe site
__cf_bmE8usoe.tech about 0 daysthe site

Pages and API calls

Pages it links to

/

Endpoints

Called while loading (seen) or named in the code (code).

usoe.tech/__l5e/trackeventsseenE10

Evidence

Every sentence above points to one of these. Code references show the file, line:column and the short identifier that matched, never the site's code itself.

E1
Page title: USOE — United States Oil Exchange | American oil, on-chain
page title · https://usoe.tech/
E2
Page description: $USOE turns American crude into a portable, on-chain claim. Barrel-backed, built for markets that never sleep. Goes live November 7, 2026.
page description · https://usoe.tech/
E3
Main heading: American Oil, now on-chain.
page h1 · https://usoe.tech/
E4
9 request(s) to usoe.tech
types: 4 script, 2 image, 1 document
GET https://usoe.tech/ · script · 9 requests · network recording
E5
1 request(s) to fonts.googleapis.com
types: 1 stylesheet
GET https://fonts.googleapis.com/css2 · stylesheet · network recording
E6
4 request(s) to fonts.gstatic.com
types: 4 font
GET https://fonts.gstatic.com/s/jetbrainsmono/v24/tDbv2o-flEEny0FZhsfKu5WU4zr3E_BX0PnT8RD8yKwBNntkaToggR7BYRbKPxDcwg.w… · font · 4 requests · network recording
E7
Cookie '__dpl' set for usoe.tech
kept for about 1 days
cookie __dpl on usoe.tech · value not stored
E8
Cookie '__cf_bm' set for usoe.tech
kept for about 0 days
cookie __cf_bm on usoe.tech · value not stored
E9
React detected by The code reader (react-runtime)
confidence: medium
usoe.tech/assets/index-Dg6oKQof.js · “react-runtime” · The code reader analyze-web-bundle 6.4.0
E10
The page called /__l5e/trackevents on usoe.tech (POST)
POST https://usoe.tech/__l5e/trackevents · fetch · network recording
E11
1 links to pages on the same site
page links · https://usoe.tech/ · /
E12
The site says: “…N · USOE NAMED THE SETTLEMENT LAYER FOR AMERICAN CRUDE ON-CHAIN · GOES LIVE NOVEMBER 7 BULLETIN · USOE NAMED THE SETTL…”
page text · https://usoe.tech/ · …N · USOE NAMED THE SETTLEMENT LAYER FOR AMERICAN CRUDE ON-CHAIN · GOES LIVE NOVEMBER 7 BULLETIN · USOE NAMED THE SETTL…
E13
The site says: “…III Pipeline — Holder dashboard — Barrel proof feed — Market maker program PHASE IV Reserve — Institutional access — Vaul…”
page text · https://usoe.tech/ · …III Pipeline — Holder dashboard — Barrel proof feed — Market maker program PHASE IV Reserve — Institutional access — Vaul…
E14
The site says: “…seeded — Coinbase listing PHASE III Pipeline — Holder dashboard — Barrel proof feed — Market maker program PHASE IV Re…”
page text · https://usoe.tech/ · …seeded — Coinbase listing PHASE III Pipeline — Holder dashboard — Barrel proof feed — Market maker program PHASE IV Re…
E15
The Internet Archive has no saved copy of usoe.tech
page web archive · https://web.archive.org/web/*/usoe.tech

Limits

  • We only see what your browser sees: code and requests on a first visit, without logging in or accepting cookie banners. What the servers do with data is invisible from outside.
  • Site code is usually minified (compressed), so names are partly lost and some code may be only partly analysed.
  • Some trackers only load after you accept cookies or log in, so the real list can be longer.
  • We visited from a server in the United States. Sites load different trackers and cookie banners in different countries (visitors in the EU usually get a consent banner first).
  • The tech check compares the site's own words with what its public page loads. Work done on servers, in private code or in separate apps isn't visible here, so 'nothing found' means not visible on the public page, not that it doesn't exist.
  • This text was written from fixed templates because no AI writer was available. It uses exactly the same evidence.
  • The code reader hit its size budget on parts of 1 large bundle file(s); those parts weren't fully analysed.

Facts, not judgements: this page describes what the code and traffic show, not anyone's intent. Not financial advice. Case id XAxs8Szp.