Programmable signaling fabric

Stop building APIs for simple communication. Use a vertex.

Node Vertex turns a URL into a stateful, secure, optionally intelligent endpoint. Store values, signal events, attach logic, share files, coordinate devices, and let AI agents exchange state through simple HTTP instead of custom glue infrastructure.

If all you need is POST /acme/build-status and GET /acme/build-status, you should not have to design, deploy, secure, monitor, and version another API.

See how it works Read developer docs
One vertex. Two calls.
POST /acme/build-status 
{ "status": "passed" }
GET /acme/build-status 
{ "status": "passed" }
No controller. No queue setup. No webhook receiver. Just a secure stateful URL.

The simplest way to connect anything to anything

A vertex replaces the small APIs, webhook glue, and coordination scripts that slow teams down.

Store state

Persist primitives, JSON, files, task output, flags, and configuration at a stable URL. Read it back from any service, script, browser, device, or agent.

Signal events

Use a POST as an event, command, heartbeat, workflow trigger, deployment notification, or machine-to-machine signal.

Secure endpoints

Protect vertices with public access, bearer tokens, basic auth, tenant auth, signed expiring links, and future-ready OIDC and SAML policies.

Use TTL

Create short-lived vertices for ephemeral communication: one-time payloads, temporary command channels, expiring downloads, and transient agent rendezvous.

Smart Vertices

Endpoints can be more than storage. They can become programmable coordination points.

A Smart Vertex is a URL with behavior: validation, lifecycle, access control, optional history, signed access, append-only semantics, read-once or write-once constraints, and future hooks for webhooks, server-sent events, MQTT bridges, agent workflows, and policy engines.

Developers get the speed of a key-value store, the reach of HTTP, and the operational posture of a secured, auditable integration layer.

Primitive values Structured JSON Signals Mailboxes Files Operation results API keys OIDC and SAML ready Signed links TTL expiration Write-once output Audit hashes

Real-world use cases

Built for developers, IoT devices, AI agents, and automation systems.

Build and deployment status

CI posts status to a vertex. Dashboards, release scripts, and agents read the latest state.

POST /acme/build-status
AI agent output

An agent publishes a task result to a stable URL without hosting its own callback server.

GET /agents/research-result-42
IoT heartbeats

Devices post telemetry and health signals using lightweight HTTP from constrained environments.

POST /factory/device-17-heartbeat
Temporary handoffs

Use TTL for expiring values, one-time reads, temporary tokens, and short-lived coordination channels.

GET /ops/incident-bridge?token=...
Webhook replacement

Instead of exposing another receiver, let systems post to a vertex and have workers consume when ready.

POST /billing/payment-events
Secure file endpoints

Attach a report or artifact to a vertex and share it through a signed expiring URL.

GET /acme/report-q2

Developer examples

Simple HTTP. Immediate value.

Create communication surfaces with URLs that already understand state, security, and lifecycle.

Store build status

curl -X POST https://n-v.io/acme/build-status \
  -H "Content-Type: application/json" \
  -d '{"status":"passed"}'

curl https://n-v.io/acme/build-status

Signal a device

curl -X POST https://n-v.io/factory/reboot-device-17 \
  -H "Authorization: Bearer {token}" \
  -d '{"command":"reboot"}'

Publish an agent result with TTL

POST /agents/research-result-42
{
  "ttlMinutes": 60,
  "result": "analysis complete"
}

Product differentiation

Node Vertex is not a URL shortener. It is communication infrastructure.

Not a URL shortener

A shortener redirects. A vertex stores state, accepts writes, enforces auth, expires, logs events, and returns data or files. The URL is the endpoint, not a pointer to one.

Better than webhooks

Webhooks require a receiver that is online, secured, and reachable. A vertex is a durable rendezvous point. Producers can write now. Consumers can read, poll, or drain when ready.

Lighter than APIs

Traditional APIs are right for complex domains. For simple state, signaling, file handoff, or agent output, a vertex removes boilerplate routes, deployments, auth plumbing, and persistence code.

Pricing summary

Start free. Scale when vertices become infrastructure.

Free

Free

1,000 vertices, 100K requests/month, Public + API key auth, Basic TTL.

Pro

$49/mo

10,000 vertices, 5M requests/month, Private vertices, TTL + versioning.

Business

$199/mo

Smart vertices, webhooks, subscriptions, audit logs, and 50M requests/month.

Enterprise

Custom

Unlimited scale, OIDC/SAML, Zero Trust policies, data residency, and SLA.

View full pricing

More information

Tell us what you want to connect with vertices.

Share your use case and we will follow up with guidance for developers, IoT fleets, AI agents, workflow automation, or enterprise security requirements.

Why build an API for this when you can just use a vertex?

Store, signal, trigger, and communicate through programmable URLs designed for the next generation of automation.

Start with the developer docs