brokers.sh
“brokers”
Tech check
What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.
AI / agents
“…on StonkFun paired with a tokenized stock and hire an AI broker in a suit with its own browser. It reads the fo…”E41
No matching code, calls or services in what loaded for us.
What it is
- The site describes itself as: “A StonkFun launchpad where every coin gets an AI broker with its own browser. It works the coin around the clock: finds the threads, lists a”E2
- It's built with Next.js and React (common tools for building web apps).E6E7
- Notable building blocks in its code: Socket.IO (live connection).E8
- In your browser it can copy text to your clipboard, saves small bits of data in your browser, receives a live stream of updates from a server and runs compiled WebAssembly code in your browser.E10E11E12E13
- It has sections such as /floor, /explore, /launch, /docs, /t and /leaderboard.E35E36
- While loading, it called 4 endpoints on its own servers, such as /api/platform, /api/desk/floor, /api/t/HXL4XEc3TscftE1DkNBNBAxyZRxgAW2Vg2Ux88BGvDLi/broker/frame and 1 more.E15E16E17E18
Where your data goes
On a first visit the page only talked to its own servers (brokers.sh).
Crypto and wallets
How key features work
What it can ask your wallet to sign
Its code can ask your wallet for signTransaction. Each of these opens a wallet pop-up you must approve; read it before you click.E39
signTransactionConnecting your wallet
It connects to crypto wallets using Phantom, signTransaction and signMessage. Connecting shows the site your wallet address; it doesn't move funds by itself.E9
PhantomsignTransactionsignMessageSign-in and accounts
Sign-in and account features show up in its code or traffic (/api/auth/nonce).E33
/api/auth/nonceLive updates
It keeps live connections open (server-sent events and Socket.IO (live connection)) so content updates without reloading.E12E8
event_sourceSocket.IO (live connection)Loading its content
Its content loads from its own API while you browse (/api/platform, /api/desk/floor, /api/t/HXL4XEc3TscftE1DkNBNBAxyZRxgAW2Vg2Ux88BGvDLi/broker/frame and /api/t/HXL4XEc3TscftE1DkNBNBAxyZRxgAW2Vg2Ux88BGvDLi/broker).E15E16E17E18
/api/platform/api/desk/floor/api/t/HXL4XEc3TscftE1DkNBNBAxyZRxgAW2Vg2Ux88BGvDLi/broker/frame/api/t/HXL4XEc3TscftE1DkNBNBAxyZRxgAW2Vg2Ux88BGvDLi/brokerDrawing and editing in the browser
The page draws and edits graphics in your browser using WebAssembly and the canvas.E13E14
webassemblycanvasSaving data on your device
It saves data in your browser (localStorage), so some things persist between visits.E11
local_storagePages and API calls
Pages it links to
//floor/explore/launch/docs/t/leaderboard/engine.io/socket.io/_next/imageEndpoints
Called while loading (seen) or named in the code (code).
| brokers.sh/api/platform | seenE15 |
| brokers.sh/api/desk/floor | seenE16 |
| brokers.sh/api/t/HXL4XEc3TscftE1DkNBNBAxyZRxgAW2Vg2Ux88BGvDLi/broker/frame | seenE17 |
| brokers.sh/api/t/HXL4XEc3TscftE1DkNBNBAxyZRxgAW2Vg2Ux88BGvDLi/broker | seenE18 |
| /api/platform | codeE19 |
| /api/quotes | codeE20 |
| /api/launch | codeE21 |
| /socket.io | codeE22 |
| /engine.io | codeE23 |
| /api/t/68R6PSWipAwGVmHpfvsCSfQG6chrqe7q4tA3uDoevJ2S/broker/frame | codeE24 |
| /api/t/B2GESkSErPjuCq6n4LcaJP5v2z1kJnw3xHVZnop2sZx/broker/frame | codeE25 |
| /api/t/F1DNjQUPECYid8Kaws3KeAXMMzCvm55ZLpwr79hzCeqg/broker/frame | codeE26 |
| /api/t/6GmAFSYs4gk3FDao5FzzySQpPZaWsa4rUJHacpMpUNgx/broker/frame | codeE27 |
| /api/t/HcRLc9VDgjLeK154xDawfb1dmVJ98DoSqcwTHGqiDeJR/broker/frame | codeE28 |
| /api/t/ALDVtr9JeLjKH91fHFvLxFoyd7C6eLUxi9dUoN2FsWdD/broker/frame | codeE29 |
| /api/t/HuAXPyDWDaMYFKuwQHpqL1oPnj93zdzWmtvFGzCeCUa7/broker/frame | codeE30 |
| /api/desk/graph | codeE31 |
| /api/t | codeE32 |
| /api/auth/nonce | codeE33 |
| /api/live/stream | codeE34 |
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.
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.
- REA hit its size budget on parts of 9 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 YxFLVyQn.