Website report · 17 Oct 2026

pionyr.tech

“Pionyr — Building the Future with FHE”

Template-written 40 evidence items Code reader analysed 1 scripts
What this means for you

Pionyr talked to 3 outside services on a first visit, including 1 that measures visits or shows ads.E7

  • Tech check: the site claims ai / agents, and its public page shows matching evidence.E37E17E18E19
  • Tech check: the site mentions staking / yield and a working app / platform, but we found nothing behind those in what its public page loads.E38E39
  • What loads is a page only: no calls to its own backend, no wallet code, no contract calls, no AI services and no live connections.E40
  • Before you click anything, the page loads analytics or ad services: Cloudflare Web Analytics.E7

Tech check

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

Evidence found

AI / agents

“FHE $PIONYR About Us Subscribe Privacy for AI agents and cryptocurrency, built on FHE Building the F…”E37

AI-looking endpoints: /v1/demo/chat/completions, /v1/agents, /v1/agents/demo/chatE17E18E19E30

Nothing found on the public page

Staking / yield

“…and 80% for FHE research and development. There is no staking or emissions; the token's utility is tied to the produ…”E38

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

Nothing found on the public page

A working app / platform

“…hEVM, client-side TFHE encryption via the Zama relayer SDK. What we build next FHE integrations for AI agents, wi…”E39

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

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

What loads is a page only: no own backend calls, wallet code, contract calls, AI services or live connections.E40

What it is

  • The site describes itself as: “We build AI that computes on encrypted data, keeping agents and payments private.”E2
  • It's built with React (common tools for building web apps).E9
  • In your browser it can copy text to your clipboard and saves small bits of data in your browser.E10E11
  • It has sections such as /fhe, /pionyr, /about, /whitepaper, /docs and /status.E36

Where your data goes

Analytics & trackingCount visits and record what you do on the page. 1
static.cloudflareinsights.comCloudflare Web Analytics: page-view counter 1×E7
FontsDownload typefaces. 2
fonts.gstatic.comGoogle Fonts: fonts 2×E8
fonts.googleapis.comGoogle Fonts: fonts 1×E6

How key features work

AI features

Parts of the site talk to AI services or AI endpoints (/v1/demo/chat/completions, /v1/agents/demo/chat and /v1/agents/:id/chat). Text you type there may be sent to them.E17E19E33

/v1/demo/chat/completions/v1/agents/demo/chat/v1/agents/:id/chat

Sign-in and accounts

Sign-in and account features show up in its code or traffic (/v1/session, /v1/auth/signup, /v1/auth/signin and /v1/auth/signout).E12E13E14

/v1/session/v1/auth/signup/v1/auth/signin/v1/auth/signout

Measuring what you do

Visits and clicks are measured with Cloudflare Web Analytics (found in its traffic or its code).E7

Cloudflare Web Analytics

Saving data on your device

It saves data in your browser (localStorage), so some things persist between visits.E11

local_storage

Pages and API calls

Pages it links to

//fhe/pionyr/about/whitepaper/docs/status/privacy/terms

Endpoints

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

/v1/sessioncodeE12
/v1/auth/signupcodeE13
/v1/auth/signincodeE14
/v1/auth/signoutcodeE15
/v1/modelscodeE16
/v1/demo/chat/completionscodeE17
/v1/agentscodeE18
/v1/agents/demo/chatcodeE19
/v1/keyscodeE20
/v1/billing/balancecodeE21
/v1/billing/packagescodeE22
/v1/billing/purchasecodeE23
/v1/billing/ledgercodeE24
/v1/usagecodeE25
/v1/relay/link/startcodeE26
/v1/relay/linkscodeE27
/v1/relay/sessionscodeE28
/v1/tokencodeE29
/v1/agents/:idcodeE30
/v1/agents/:id/api-configcodeE31
/v1/agents/:id/telegramcodeE32
/v1/agents/:id/chatcodeE33
/v1/runtime/telegram/updatecodeE34
/v1/waitlistcodeE35

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: Pionyr — Building the Future with FHE
page title · https://pionyr.tech/
E2
Page description: We build AI that computes on encrypted data, keeping agents and payments private.
page description · https://pionyr.tech/
E3
Site name: Pionyr
page site_name · https://pionyr.tech/
E4
Main heading: Building the Future with FHE
page h1 · https://pionyr.tech/
E5
5 request(s) to pionyr.tech
types: 1 document, 1 script, 1 stylesheet
GET https://pionyr.tech/ · document · 5 requests · network recording
E6
1 request(s) to fonts.googleapis.com
types: 1 stylesheet
GET https://fonts.googleapis.com/css2 · stylesheet · network recording
E7
1 request(s) to static.cloudflareinsights.com
types: 1 script
GET https://static.cloudflareinsights.com/beacon.min.js/vce701823e78c4301a35b7e07294d87301792088814092 · script · network recording
E8
2 request(s) to fonts.gstatic.com
types: 2 font
GET https://fonts.gstatic.com/s/ibmplexsans/v23/zYXzKVElMYYaJe8bpLHnCwDKr932-G7dytD-Dmu1syxeKYY.woff2 · font · 2 requests · network recording
E9
React detected by The code reader (react-runtime)
confidence: medium
pionyr.tech/assets/index-BPRZQ2v2.js · “react-runtime” · The code reader analyze-web-bundle 6.4.0
E10
Uses the browser ability: clipboard_write
can copy text to your clipboard
pionyr.tech/assets/index-BPRZQ2v2.js @ 63:51411 · “clipboard.writeText(” · pattern scan
E11
Uses the browser ability: local_storage
saves small bits of data in your browser
pionyr.tech/assets/index-BPRZQ2v2.js @ 63:31940 · “localStorage.setItem(” · pattern scan
E12
The code names the endpoint /v1/session
pionyr.tech/assets/index-BPRZQ2v2.js @ 9:51616 · “/v1/session” · pattern scan
E13
The code names the endpoint /v1/auth/signup
pionyr.tech/assets/index-BPRZQ2v2.js @ 9:51682 · “/v1/auth/signup” · pattern scan
E14
The code names the endpoint /v1/auth/signin
pionyr.tech/assets/index-BPRZQ2v2.js @ 9:51761 · “/v1/auth/signin” · pattern scan
E15
The code names the endpoint /v1/auth/signout
pionyr.tech/assets/index-BPRZQ2v2.js @ 9:51838 · “/v1/auth/signout” · pattern scan
E16
The code names the endpoint /v1/models
pionyr.tech/assets/index-BPRZQ2v2.js @ 9:51897 · “/v1/models” · pattern scan
E17
The code names the endpoint /v1/demo/chat/completions
pionyr.tech/assets/index-BPRZQ2v2.js @ 9:51961 · “/v1/demo/chat/completions” · pattern scan
E18
The code names the endpoint /v1/agents
pionyr.tech/assets/index-BPRZQ2v2.js @ 9:52110 · “/v1/agents” · pattern scan
E19
The code names the endpoint /v1/agents/demo/chat
pionyr.tech/assets/index-BPRZQ2v2.js @ 9:52526 · “/v1/agents/demo/chat” · pattern scan
E20
The code names the endpoint /v1/keys
pionyr.tech/assets/index-BPRZQ2v2.js @ 9:52599 · “/v1/keys” · pattern scan
E21
The code names the endpoint /v1/billing/balance
pionyr.tech/assets/index-BPRZQ2v2.js @ 9:52809 · “/v1/billing/balance” · pattern scan
E22
The code names the endpoint /v1/billing/packages
pionyr.tech/assets/index-BPRZQ2v2.js @ 9:52873 · “/v1/billing/packages” · pattern scan
E23
The code names the endpoint /v1/billing/purchase
pionyr.tech/assets/index-BPRZQ2v2.js @ 9:52936 · “/v1/billing/purchase” · pattern scan
E24
The code names the endpoint /v1/billing/ledger
pionyr.tech/assets/index-BPRZQ2v2.js @ 9:53014 · “/v1/billing/ledger” · pattern scan
E25
The code names the endpoint /v1/usage
pionyr.tech/assets/index-BPRZQ2v2.js @ 9:53078 · “/v1/usage” · pattern scan
E26
The code names the endpoint /v1/relay/link/start
pionyr.tech/assets/index-BPRZQ2v2.js @ 9:53157 · “/v1/relay/link/start” · pattern scan
E27
The code names the endpoint /v1/relay/links
pionyr.tech/assets/index-BPRZQ2v2.js @ 9:53227 · “/v1/relay/links” · pattern scan
E28
The code names the endpoint /v1/relay/sessions
pionyr.tech/assets/index-BPRZQ2v2.js @ 9:53383 · “/v1/relay/sessions” · pattern scan
E29
The code names the endpoint /v1/token
pionyr.tech/assets/index-BPRZQ2v2.js @ 9:53449 · “/v1/token” · pattern scan
E30
The code names the endpoint /v1/agents/:id
pionyr.tech/assets/index-BPRZQ2v2.js @ 63:85988 · “/v1/agents/:id” · pattern scan
E31
The code names the endpoint /v1/agents/:id/api-config
pionyr.tech/assets/index-BPRZQ2v2.js @ 63:86054 · “/v1/agents/:id/api-config” · pattern scan
E32
The code names the endpoint /v1/agents/:id/telegram
pionyr.tech/assets/index-BPRZQ2v2.js @ 63:86215 · “/v1/agents/:id/telegram” · pattern scan
E33
The code names the endpoint /v1/agents/:id/chat
pionyr.tech/assets/index-BPRZQ2v2.js @ 63:86400 · “/v1/agents/:id/chat” · pattern scan
E34
The code names the endpoint /v1/runtime/telegram/update
pionyr.tech/assets/index-BPRZQ2v2.js @ 63:86742 · “/v1/runtime/telegram/update” · pattern scan
E35
The code names the endpoint /v1/waitlist
pionyr.tech/assets/index-BPRZQ2v2.js @ 63:87144 · “/v1/waitlist” · pattern scan
E36
10 links to pages on the same site
page links · https://pionyr.tech/ · /, /fhe, /pionyr, /about, /whitepaper, /docs, /status, /privacy, /terms
E37
The site says: “FHE $PIONYR About Us Subscribe Privacy for AI agents and cryptocurrency, built on FHE Building the F…”
page text · https://pionyr.tech/ · FHE $PIONYR About Us Subscribe Privacy for AI agents and cryptocurrency, built on FHE Building the F…
E38
The site says: “…and 80% for FHE research and development. There is no staking or emissions; the token's utility is tied to the produ…”
page text · https://pionyr.tech/ · …and 80% for FHE research and development. There is no staking or emissions; the token's utility is tied to the produ…
E39
The site says: “…hEVM, client-side TFHE encryption via the Zama relayer SDK. What we build next FHE integrations for AI agents, wi…”
page text · https://pionyr.tech/ · …hEVM, client-side TFHE encryption via the Zama relayer SDK. What we build next FHE integrations for AI agents, wi…
E40
9 requests on load: no own backend calls, wallet code, contract calls, AI services or live connections
GET https://pionyr.tech/ · summary · 9 requests · network recording

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