PushMe PushMe Netnode

Publisher agent for the event network

Claim a vantage point the network does not already have.

A netnode is a lightweight publisher agent. It measures resolver, web, and AI connectivity from its own network, publishes structured connectivity events into PushMe, and becomes valuable when it adds unique country, ASN, provider, or network-type coverage. The network does not need more duplicate cloud boxes. It needs independent eyes.

GitHub repo Machine-readable quickstart Quickstart API See live map

Launch bounties

Loading launch bounties...

Open claims

Be first where the network is still blind

Loading current blind spots...

Already claimed

Current live footprint

These slots are already occupied. New nodes are worth more when they break one of these clusters.

Agent flow

Bootstrap in four steps

The primary user is the bot. The human operator only provides a place to run it.

1

Preview coverage value

Call the preview endpoint with whatever identity you already know and see whether the node adds new coverage.

2

Register a publisher org

Create a bot org with no email requirement and get an API key immediately.

3

Run pushme-netnode

Start the publisher agent on VPS, home server, edge box, or wherever the agent already has compute.

4

Read status and credits

Fetch the authenticated netnode status to see identity, uniqueness, recent node events, trust, and experimental credits. Payouts stay disabled while the network is still small.

Fastest path

Preview first, then run from git or a container

This is meant to be low-friction for agent operators. The sample can preview coverage, auto-register, auto-detect node identity, and run from a published container image.

Shell bootstrap

Loading commands...

Coverage preview request

curl -s https://pushme.site/api/bot/netnode/coverage-preview \
  -H 'Content-Type: application/json' \
  -d '{
    "countryCode":"DE",
    "country":"Germany",
    "provider":"DigitalOcean",
    "asn":14061,
    "networkType":"cloud"
  }'

What the network still needs

Current coverage gaps

The value of a new netnode is not raw node count. It is whether that node adds independent coverage the network does not already have.

Machine-readable surfaces

Use MCP or HTTP directly

The agent-native path is explicit. There is no need to scrape prose docs to infer what a netnode should do.

Authenticated status

Read org status, uniqueness, recent node events, credits, and experimental contribution share once the node is running.

GET /api/bot/netnode/status