Omnibus only talked to its own servers while we watched.E1
An AI agent used the site and saw 1 of 2 claimed features working.E33E35E36E38E34
Fee schedule for Send / Take delivery / Swap / Statement (relayer fee only, 0.20% and 0.10% protocol fees): The fee table is published on the homepage and on the /docs/fees page, which adds that the relayer fee applies to take delivery and swap as well. The Swap and Send pages under /account show 'Locked' and ask for a wallet connection and a signed message, so I couldn't run a transaction to check the fees actually charged.E33E35E36E38
Extra observation: The Book live dashboard: The /book page loaded data from api.omnibus.work/v1/config and /v1/book. It shows a tree root at depth 26, and every counter and vault balance (USDC, USDT, SOL, JUP, Bonk, WIF) is 0, which means no recorded activity yet.E34
Tech check: the site claims trading / swaps / bots, and its public page shows matching evidence.E31E29
We saw no known analytics or advertising services load on the first visit.E1
Its code can ask your wallet to sign transactions. Read every wallet pop-up before approving.E29
Tech check
What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.
Evidence found
Trading / swaps / bots
“…Send Relayer fee only Take delivery 0.20% protocol fee Swap 0.10% protocol fee Statement Relayer fee only From you…”E31
Transaction requests to your wallet: signTransactionE29
An AI agent (claude-opus-5-5) used the site in our sandbox for 6 steps and saw 0 of 1 claimed feature working. It can't connect a wallet, pay, sign or log in, so those features count as "couldn't test". What it reports is what it observed, not a verdict.
Couldn't test
Fee schedule for Send / Take delivery / Swap / Statement (relayer fee only, 0.20% and 0.10% protocol fees)
The fee table is published on the homepage and on the /docs/fees page, which adds that the relayer fee applies to take delivery and swap as well. The Swap and Send pages under /account show 'Locked' and ask for a wallet connection and a signed message, so I couldn't run a transaction to check the fees actually charged.E33E35E36E38
Also noticed
Things the agent saw along the way that aren't among the site's claims. Not counted above.
Noticed
The Book live dashboard
The /book page loaded data from api.omnibus.work/v1/config and /v1/book. It shows a tree root at depth 26, and every counter and vault balance (USDC, USDT, SOL, JUP, Bonk, WIF) is 0, which means no recorded activity yet.E34
What it is
The Internet Archive has never saved this site, so it is probably new.E32
The site describes itself as: “Street name for Solana: hold, pay and trade any token from one account the chain can't read.”E2
It's built with Next.js and React (common tools for building web apps).E8E9
In your browser it saves small bits of data in your browser.E10
It has sections such as /account, /book, /docs, /token and /view.E28
While loading, it called 2 endpoints on its own servers, such as /v1/config and /v1/book.E13E14
Where your data goes
On a first visit the page only talked to its own servers (omnibus.work, api.omnibus.work).
Crypto and wallets
signTransaction: asks a wallet to sign transactions (often Solana wallets).E29
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: Omnibus — street name for Solana
page title · https://omnibus.work/
E2
Page description: Street name for Solana: hold, pay and trade any token from one account the chain can't read.
page description · https://omnibus.work/
E3
Site name: Omnibus
page site_name · https://omnibus.work/
E4
Main heading: Street name for Solana
page h1 · https://omnibus.work/
E5
18 request(s) to omnibus.work
types: 11 script, 3 font, 3 stylesheet
GET https://omnibus.work/ · script · 18 requests · network recording
E6
5 request(s) to api.omnibus.work
types: 5 fetch
GET https://api.omnibus.work/v1/config · fetch · 5 requests · network recording
E7
sessionStorage: 1 key(s) saved in your browser
sessionStorage keys: omnibus.seen · values not stored
E8
Next.js detected by the code reader (next-runtime)
confidence: high
omnibus.work/_next/static/chunks/turbopack-3-ry682tkyiqk.js · “next-runtime” · the code reader
E9
React detected by the code reader (react-runtime)
confidence: medium
omnibus.work/_next/static/chunks/38j7e35_4hoix.js · “react-runtime” · the code reader
The site says: “…Send Relayer fee only Take delivery 0.20% protocol fee Swap 0.10% protocol fee Statement Relayer fee only From you…”
page text · https://omnibus.work/ · …Send Relayer fee only Take delivery 0.20% protocol fee Swap 0.10% protocol fee Statement Relayer fee only From you…
E32
The Internet Archive has no saved copy of omnibus.work
page web archive · https://web.archive.org/web/*/omnibus.work
E33
Agent step 1: view
AI agent step 1 · view on /
E34
Agent step 2: go /book
AI agent step 2 · go on /book · page called GET api.omnibus.work/v1/config, GET api.omnibus.work/v1/book
E35
Agent step 3: go /account
AI agent step 3 · go on /account · page called GET api.omnibus.work/v1/config, GET api.omnibus.work/v1/book
E36
Agent step 4: go /account/swap
AI agent step 4 · go on /account/swap · page called GET api.omnibus.work/v1/config, GET api.omnibus.work/v1/book
E37
Agent step 5: go /docs
AI agent step 5 · go on /docs · page called GET api.omnibus.work/v1/config, GET api.omnibus.work/v1/book
E38
Agent step 6: go /docs/fees
AI agent step 6 · go on /docs/fees · page called GET api.omnibus.work/v1/config, GET api.omnibus.work/v1/book
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 5 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 dQyfEyCw.
WELCOME TO TRENCHCOAT
1 of 3 · What it does
Know the coin before you buy it
Paste any coin address, wallet or X post. We scan it in seconds, free, no sign-up.
Every coin gets a green, yellow or red light and a score out of 100, and every point links to its source.
2 of 3 · How to read a check
Three questions, then the money
Is the tech real? Is the dev legit? Fair launch? Each has its own score and its top reasons.
Who's behind it: the dev's linked wallets, crews that buy launches together, and the launch block by who paid for it.
Money taken out: what the dev and launch-block wallets sold or pulled in the first 24 hours.
3 of 3 · Stay on it
Track coins and wallets
Press Track on any coin or wallet. You'll get a browser notification when the dev sells, liquidity is pulled, the price moves hard, or a tracked wallet trades.
No account: it's tied to this browser. See everything you track under Tracking.