Website blueprint · 19 Oct 2026

p0z.app

“p0z • Launch a coin, AI agents build it”

Template-written 27 evidence items REA analysed 1 scripts

What this means for you

p0z.app talked to 1 outside service on a first visit, including 1 that measures visits or shows ads.E5

Tech check: the site claims ai / agents, and its public page shows matching evidence.E27 E15 E21
Before you click anything, the page loads analytics or ad services: Cloudflare Web Analytics.E5

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

“Skip to the office floor Launch a coin. 2,222 AI agents build it. Name it, give it a picture, say what…”E27

AI-looking endpoints: /api/agents, /api/agentE15 E21

Calls its own backend /api/pad, /api/statsE8 E9

Wallet code none seen

Contract calls in its code none seen

Talks to AI services none seen

Live connections receives a live stream of updates from a serverE7

What it is

The site describes itself as: “Launch a coin on pump.fun and 2,222 AI agents build it: the memes, the website, the posts. Every agent is an NFT, paid from the fees of the ”E2
It's built with React (common tools for building web apps).E6
In your browser it receives a live stream of updates from a server.E7
It has sections such as /explore, /launch, /create, /agents, /mint and /market.E26
While loading, it called 2 endpoints on its own servers, such as /api/pad and /api/stats.E8 E9

Where your data goes

Analytics & trackingCount visits and record what you do on the page. 1

static.cloudflareinsights.com

Cloudflare Web Analytics: page-view counter

1×E5

How key features work

Live updates

It keeps live connections open (server-sent events) so content updates without reloading.E7

event_source

Loading its content

Its content loads from its own API while you browse (/api/pad and /api/stats).E8 E9

/api/pad/api/stats

Measuring what you do

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

Cloudflare Web Analytics

Pages and API calls

Pages it links to

//explore/launch/create/agents/mint/market/desk/docs/flow/coin/agent

Endpoints

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

p0z.app/api/pad	seenE8
p0z.app/api/stats	seenE9
/api/pad	codeE10
/api/coins/claim	codeE11
/api/stats	codeE12
/api/employees	codeE13
/api/coins	codeE14
/api/agents	codeE15
/api/wallets	codeE16
/api/creations	codeE17
/api/create	codeE18
/api/coin	codeE19
/api/employee	codeE20
/api/agent	codeE21
/api/coins/finish	codeE22
/api/coins/finish/landed	codeE23
/api/coins/landed	codeE24
/api/job	codeE25

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.

Page title: p0z • Launch a coin, AI agents build it

page title · https://p0z.app/

Page description: Launch a coin on pump.fun and 2,222 AI agents build it: the memes, the website, the posts. Every agent is an NFT, paid from the fees of the coins it b

page description · https://p0z.app/

Main heading: Launch a coin. 2,222 AI agents build it.

page h1 · https://p0z.app/

63 request(s) to p0z.app

types: 54 image, 2 font, 2 fetch

GET https://p0z.app/ · image · 63 requests · network recording

1 request(s) to static.cloudflareinsights.com

types: 1 script

GET https://static.cloudflareinsights.com/beacon.min.js/vce701823e78c4301a35b7e07294d87301792088814092 · script · network recording

React detected by REA (react-runtime)

confidence: medium

p0z.app/assets/index-BBocdS0O.js · “react-runtime” · REA analyze-web-bundle 6.4.0

Uses the browser ability: event_source

receives a live stream of updates from a server

p0z.app/assets/index-BBocdS0O.js @ 18:41488 · “new EventSource(” · pattern scan

The page called /api/pad on p0z.app (GET)

GET https://p0z.app/api/pad · fetch · network recording

The page called /api/stats on p0z.app (GET)

GET https://p0z.app/api/stats · fetch · network recording

E10

REA found the endpoint /api/pad

how: call:fetch

p0z.app/assets/index-BBocdS0O.js @ 18:42836 · “/api/pad” · REA analyze-web-bundle 6.4.0

E11

REA found the endpoint /api/coins/claim

how: call:fetch

p0z.app/assets/index-BBocdS0O.js @ 18:52091 · “/api/coins/claim” · REA analyze-web-bundle 6.4.0

E12

REA found the endpoint /api/stats

how: call:fetch

p0z.app/assets/index-BBocdS0O.js @ 18:66864 · “/api/stats” · REA analyze-web-bundle 6.4.0

E13

REA found the endpoint /api/employees

how: call:fetch

p0z.app/assets/index-BBocdS0O.js @ 18:85672 · “/api/employees” · REA analyze-web-bundle 6.4.0

E14

REA found the endpoint /api/coins

how: call:fetch

p0z.app/assets/index-BBocdS0O.js @ 18:135089 · “/api/coins” · REA analyze-web-bundle 6.4.0

E15

REA found the endpoint /api/agents

how: call:fetch

p0z.app/assets/index-BBocdS0O.js @ 18:135152 · “/api/agents” · REA analyze-web-bundle 6.4.0

E16

REA found the endpoint /api/wallets

how: call:fetch

p0z.app/assets/index-BBocdS0O.js @ 18:139400 · “/api/wallets” · REA analyze-web-bundle 6.4.0

E17

REA found the endpoint /api/creations

how: call:fetch

p0z.app/assets/index-BBocdS0O.js @ 18:164795 · “/api/creations” · REA analyze-web-bundle 6.4.0

E18

REA found the endpoint /api/create

how: call:fetch

p0z.app/assets/index-BBocdS0O.js @ 18:165276 · “/api/create” · REA analyze-web-bundle 6.4.0

E19

The code names the endpoint /api/coin

p0z.app/assets/index-BBocdS0O.js @ 18:51987 · “/api/coin” · pattern scan

E20

The code names the endpoint /api/employee

p0z.app/assets/index-BBocdS0O.js @ 18:87215 · “/api/employee” · pattern scan

E21

The code names the endpoint /api/agent

p0z.app/assets/index-BBocdS0O.js @ 18:112225 · “/api/agent” · pattern scan

E22

The code names the endpoint /api/coins/finish

p0z.app/assets/index-BBocdS0O.js @ 18:169156 · “/api/coins/finish” · pattern scan

E23

The code names the endpoint /api/coins/finish/landed

p0z.app/assets/index-BBocdS0O.js @ 18:169335 · “/api/coins/finish/landed” · pattern scan

E24

The code names the endpoint /api/coins/landed

p0z.app/assets/index-BBocdS0O.js @ 18:172507 · “/api/coins/landed” · pattern scan

E25

The code names the endpoint /api/job

p0z.app/assets/index-BBocdS0O.js @ 18:188955 · “/api/job” · pattern scan

E26

44 links to pages on the same site

page links · https://p0z.app/ · /, /explore, /launch, /create, /agents, /mint, /market, /desk, /docs, /flow, /coin, /agent

E27

The site says: “Skip to the office floor Launch a coin. 2,222 AI agents build it. Name it, give it a picture, say what…”

page text · https://p0z.app/ · Skip to the office floor Launch a coin. 2,222 AI agents build it. Name it, give it a picture, say what…

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