How Node Vertex works

A URL becomes an addressable vertex with behavior.

Each Node Vertex URL maps to a tenant-owned endpoint with a key, type, access policy, lifecycle, current value, optional history, optional file metadata, optional message queue, and optional write behavior. Clients interact with vertices using familiar HTTP verbs, while Node Vertex handles storage, authentication, auditing, and routing.

Create a vertex

Choose a tenant, key, type, access mode, allowed methods, expiration policy, and behavior such as append-only, read-once, or write-once.

https://n-v.io/acme/status-flag

Interact over HTTP

GET reads a value, POST writes or appends, PUT replaces, PATCH updates JSON, HEAD returns metadata, and DELETE disables according to policy.

curl -X PUT https://n-v.io/acme/status-flag -d true

Automate downstream

Agents, devices, workers, and applications can poll, consume, publish, or trigger workflows using the same stable address.

GET /acme/status-flag → true

Automation examples

Agent publishes an operation result

An autonomous worker finishes a scan and posts the result to a stable URL. Dashboards, users, and other agents can read the result without needing direct access to the worker.

curl -X POST https://n-v.io/acme/scan-output-88 \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer {token}" \
  -d '{"status":"complete","findings":12}'

Device receives a signal

A control plane posts a reboot command to a signal vertex. The device polls the vertex, validates the command, acts, and optionally posts an acknowledgement to another vertex.

POST /factory/reboot-device-17
{
  "command": "reboot",
  "issuedBy": "agent-01"
}

Telemetry mailbox

Many devices can POST telemetry messages into a mailbox vertex. A processing service reads or drains the queue on its own schedule.

curl -X POST https://n-v.io/acme/device-telemetry \
  -H "Content-Type: application/json" \
  -d '{"deviceId":"iot-17","temp":72.2,"status":"ok"}'

Secure temporary access

Generate an expiring signed URL for a file, report, result, or status payload. The link can be read-only, write-only, or read/write and can enforce a maximum number of uses.

https://n-v.io/acme/report-2026-q2?token={signedToken}

Designed for secure machine-to-machine communication

Node Vertex gives each endpoint an access policy. Public vertices are easy to share, while bearer tokens, basic auth, tenant user protection, and signed expiring tokens support controlled access. Secrets are hashed, writes create events, and payload hashes provide integrity evidence.

Vertex type	What it does	Typical use
Primitive	Stores a raw value	Status flags, counters, simple configuration
JSON	Stores structured payloads	Job results, metadata, integration state
Signal	Receives commands or events	Automation triggers, device commands
Mailbox	Appends readable messages	Telemetry, task queues, inboxes
File	Exposes downloadable file metadata/content	Reports, build artifacts, exports
Operation Result	Publishes stable task output	Agent results, worker completion records

Store, signal, trigger, and communicate through programmable URLs.

Start by creating a vertex, then connect it to an agent, device, workflow, or application using simple HTTP.

Create a vertex