trysent.app
“Sent”
Tech check
What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.
The page doesn't make tech claims we check for (AI, on-chain, wallets, trading, own chain, staking, live data, an app).
What it is
- The Internet Archive has never saved this site, so it is probably new.E36
- The site describes itself as: “Direct token fees to real world payment apps.”E2
- It's built with React (common tools for building web apps).E8
- In your browser it saves small bits of data in your browser.E9
- It has sections such as /explore, /launch, /payments, /account, /docs and /t.E33
- While loading, it called 4 endpoints on its own servers, such as /api/stats, /api/tokens, /api/payments and 1 more.E10E11E12E13
Where your data goes
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.E34
signTransactionSign-in and accounts
Sign-in and account features show up in its code or traffic (/api/auth/logout, /api/auth/wallet/challenge, /api/auth/wallet and /api/auth/x/start).E18E19E20
/api/auth/logout/api/auth/wallet/challenge/api/auth/wallet/api/auth/x/startLoading its content
Its content loads from its own API while you browse (/api/stats, /api/tokens, /api/payments and /api/me).E10E11E12E13
/api/stats/api/tokens/api/payments/api/meSaving data on your device
It saves data in your browser (localStorage), so some things persist between visits.E9
local_storagePages and API calls
Pages it links to
//explore/launch/payments/account/docs/t/terms/privacyEndpoints
Called while loading (seen) or named in the code (code).
| trysent.app/api/stats | seenE10 |
| trysent.app/api/tokens | seenE11 |
| trysent.app/api/payments | seenE12 |
| trysent.app/api/me | seenE13 |
| /api/token | codeE14 |
| /api/rewards/me | codeE15 |
| /api/rewards/settings | codeE16 |
| /api/rewards/withdraw | codeE17 |
| /api/auth/logout | codeE18 |
| /api/auth/wallet/challenge | codeE19 |
| /api/auth/wallet | codeE20 |
| /api/setup/check | codeE21 |
| /api | codeE22 |
| /api/lookup | codeE23 |
| /api/setup | codeE24 |
| /api/setup/send | codeE25 |
| /api/setup/confirm | codeE26 |
| /api/launch/options | codeE27 |
| /api/launch/pair | codeE28 |
| /api/launch/pairs | codeE29 |
| /api/launch | codeE30 |
| /api/launch/sign | codeE31 |
| /api/auth/x/start | codeE32 |
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).
- 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 FabcUnD2.