Website report · 11 h ago

trycall.app

“call: get paid properly for your callouts”

Template-written 16 evidence items Code reader analysed 25 scripts
What this means for you

call only talked to its own servers while we watched.E1

  • Tech check: the site claims wallet connection and a working app / platform, and its public page shows matching evidence.E14E15E13E9
  • 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.E13

Tech check

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

Evidence found

Wallet connection

“…close no solana wallet found in this browser. install phantom or solflare , or open this page in your wallet's brows…”E14

Wallet requests in its code: signTransactionE13

Evidence found

A working app / platform

“…r 40% callers, wallets that bring buyers 10% call, the platform examplea 1 sol buy on the curve carries 0.003 sol of c…”E15

Calls to its own backend: /api/liveE9

Calls its own backend /api/liveE9
Wallet code signTransactionE13
Contract calls in its code none seen
Talks to AI services none seen
Live connections none seen

What it is

  • The Internet Archive first saved this site on 2026-11-15 (2 days ago).E16
  • The site describes itself as: “get paid properly for your callouts. built on pump.fun creator fees: put your call link in your callout, and when a wallet makes its first b”E2
  • It's built with React and Next.js (common tools for building web apps).E6E7
  • In your browser it can copy text to your clipboard.E8
  • It has sections such as /launch, /rules and /_next/image.E11E12
  • While loading, it called 1 endpoint on its own servers, such as /api/live.E9

Where your data goes

On a first visit the page only talked to its own servers (trycall.app).

Crypto and wallets

  • signTransaction: asks a wallet to sign transactions (often Solana wallets).E13

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.E13

signTransaction

Loading its content

Its content loads from its own API while you browse (/api/live).E9

/api/live

Pages and API calls

Pages it links to

//launch/rules/_next/image

Endpoints

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

trycall.app/api/liveseenE9
/api/livecodeE10

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: call: get paid properly for your callouts
page title · https://trycall.app/
E2
Page description: get paid properly for your callouts. built on pump.fun creator fees: put your call link in your callout, and when a wallet makes its first buy of the
page description · https://trycall.app/
E3
Site name: call
page site_name · https://trycall.app/
E4
Main heading: call a coin. get paid when your buyers trade.
page h1 · https://trycall.app/
E5
35 request(s) to trycall.app
types: 13 script, 8 fetch, 7 font
GET https://trycall.app/ · script · 35 requests · network recording
E6
React detected by the code reader (react-runtime)
confidence: medium
trycall.app/_next/static/immutable/chunks/1vgjr_h9cvn3m.js · “react-runtime” · the code reader
E7
Next.js detected by the code reader (next-runtime)
confidence: high
trycall.app/_next/static/immutable/chunks/2eb3ozggr0boz.js · “next-runtime” · the code reader
E8
Uses the browser ability: clipboard_write
can copy text to your clipboard
trycall.app/_next/static/immutable/chunks/3uvrv4y8vn5ey.js @ 1:10962 · “clipboard.writeText(” · pattern scan
E9
The page called /api/live on trycall.app (GET)
GET https://trycall.app/api/live · fetch · network recording
E10
Code reader found the endpoint /api/live
how: call:fetch
trycall.app/_next/static/immutable/chunks/13ascdyfjnefo.js @ 1:11421 · “/api/live” · the code reader
E11
3 links to pages on the same site
page links · https://trycall.app/ · /, /launch, /rules
E12
Code reader found the route /_next/image
trycall.app/_next/static/immutable/chunks/2eb3ozggr0boz.js @ 1:3445 · “/_next/image” · the code reader
E13
Wallet request in code: signTransaction
asks a wallet to sign transactions (often Solana wallets)
trycall.app/_next/static/immutable/chunks/05wch5736_236.js @ 1:1774 · “signTransaction” · pattern scan
E14
The site says: “…close no solana wallet found in this browser. install phantom or solflare , or open this page in your wallet's brows…”
page text · https://trycall.app/ · …close no solana wallet found in this browser. install phantom or solflare , or open this page in your wallet's brows…
E15
The site says: “…r 40% callers, wallets that bring buyers 10% call, the platform examplea 1 sol buy on the curve carries 0.003 sol of c…”
page text · https://trycall.app/ · …r 40% callers, wallets that bring buyers 10% call, the platform examplea 1 sol buy on the curve carries 0.003 sol of c…
E16
The Internet Archive first saved trycall.app on 2026-11-15 and has snapshots from 1 different days
page web archive · https://web.archive.org/web/20261115162914/trycall.app

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 6 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 TU3SKcMx.