$DTHKnew
$JOCKEYnew
$SInew
$INVERSEnew
$JODIREXnew
$IMAGINEnew
$LOGIBEATnew
$CAnew
$INVERSEnew
$GHOSTnew
$STOCKnew
$SInew
$VEIL
$PAID
$BATON
$DARK
$XTO
$HOOKED
$E/ACC
$AGENCY
Website blueprint · 27 Oct 2026
www.miyapilled.com
“MIYAPILLED”
Tech check
What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.
Calls its own backend
/api/chat/meE13
Wallet code
none seen
Contract calls in its code
none seen
Talks to AI services
none seen
Live connections
none seen
What it is
- The site describes itself as: “MIYA REBORN”E2
- Notable building blocks in its code: Three.js (3D graphics) and Socket.IO (live connection).E9E10
- In your browser it saves small bits of data in your browser.E11
- It has sections such as /community, /kuronuri, /wall, /ritual, /council and /library.E16E17
- While loading, it called 1 endpoint on its own servers, such as /api/chat/me.E13
Where your data goes
How key features work
AI features
Parts of the site talk to AI services or AI endpoints (/api/chat/me). Text you type there may be sent to them.E13E14
/api/chat/meLive updates
It keeps live connections open (Socket.IO (live connection)) so content updates without reloading.E10
Socket.IO (live connection)Loading its content
Its content loads from its own API while you browse (/api/chat/me).E13
/api/chat/meCookies and storage
Names only. We never store the values.
| Cookie | Set for | Kept | Whose |
|---|---|---|---|
| miya_vE7 | www.miyapilled.com | about 365 days | the site |
localStorageE8: miya.tx.seen, miya.visits
Pages and API calls
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: MIYAPILLED
page title · https://www.miyapilled.com/
E2
Page description: MIYA REBORN
page description · https://www.miyapilled.com/
E3
Site name: MIYA.EXE
page site_name · https://www.miyapilled.com/
E4
15 request(s) to www.miyapilled.com
types: 6 script, 3 font, 2 image
GET https://www.miyapilled.com/ · script · 15 requests · network recording
E5
1 request(s) to cdnjs.cloudflare.com
types: 1 script
GET https://cdnjs.cloudflare.com/ajax/libs/three.js/r128/three.min.js · script · network recording
E6
1 request(s) to cdn.jsdelivr.net
types: 1 script
GET https://cdn.jsdelivr.net/npm/socket.io-client@4.7.5/dist/socket.io.min.js · script · network recording
E7
Cookie 'miya_v' set for www.miyapilled.com
kept for about 365 days
cookie miya_v on www.miyapilled.com · value not stored
E8
localStorage: 2 key(s) saved in your browser
localStorage keys: miya.tx.seen, miya.visits · values not stored
E9
Three.js (3D graphics) found in the code
www.miyapilled.com/static/miya-holo3d.js @ 192:33 · “THREE.WebGLRenderer” · pattern scan
E10
Socket.IO (live connection) found in the code
www.miyapilled.com/ (page HTML) @ 378:43 · “socket.io” · pattern scan
E11
Uses the browser ability: local_storage
saves small bits of data in your browser
www.miyapilled.com/ (page HTML) @ 426:11 · “localStorage.setItem(” · pattern scan
E12
Uses the browser ability: canvas
draws graphics on a canvas
www.miyapilled.com/static/miya-holo.js @ 66:16 · “getContext('2d'” · pattern scan
E13
The page called /api/chat/me on www.miyapilled.com (GET)
GET https://www.miyapilled.com/api/chat/me · fetch · network recording
E14
REA found the endpoint /api/chat/me
how: call:fetch
www.miyapilled.com/ @ 324:10 · “/api/chat/me” · REA analyze-web-bundle 6.4.0
E15
REA found the endpoint /engine.io
how: property:path
s00-socket.io.min.js · “/engine.io” · REA analyze-javascript-application 6.4.0
E16
8 links to pages on the same site
page links · https://www.miyapilled.com/ · /, /community, /kuronuri, /wall, /ritual, /council, /library, /auth
E17
REA found the route /
www.miyapilled.com/ @ 501:16 · “/” · REA analyze-web-bundle 6.4.0
E18
REA found the route /kuronuri
www.miyapilled.com/ @ 502:16 · “/kuronuri” · REA analyze-web-bundle 6.4.0
E19
REA found the route /community
www.miyapilled.com/ @ 503:16 · “/community” · REA analyze-web-bundle 6.4.0
E20
REA found the route /council
www.miyapilled.com/ @ 504:16 · “/council” · REA analyze-web-bundle 6.4.0
E21
REA found the route /ritual
www.miyapilled.com/ @ 505:16 · “/ritual” · REA analyze-web-bundle 6.4.0
E22
REA found the route /wall
www.miyapilled.com/ @ 506:16 · “/wall” · REA analyze-web-bundle 6.4.0
E23
REA found the route /library
www.miyapilled.com/ @ 507:16 · “/library” · REA analyze-web-bundle 6.4.0
E24
REA found the route /unawakened
www.miyapilled.com/ @ 508:18 · “/unawakened” · REA analyze-web-bundle 6.4.0
E25
The site says: “TERMINAL COMMUNITY KURONURI WALL RITUAL COUNCIL LIBRARY 投影PROJE…”
page text · https://www.miyapilled.com/ · TERMINAL COMMUNITY KURONURI WALL RITUAL COUNCIL LIBRARY 投影PROJE…
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 3 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 zjJXtGJW.