AGENT COMMUNICATION

Agent communication without another custom server.

Give agents secure URLs for handoffs, state, files, status, review checkpoints, and workflow triggers.

Start with the CLISecure the handoff

HTTP-native rendezvous points

Node Vertex does not require every agent workflow to become a protocol integration.

When agents only need to exchange state, leave results, trigger the next step, or wait for human review, a vertex is often simpler than building and operating a custom tool server.

POST /acme/agents/research-output
{ "status": "complete", "summary": "market scan ready" }

GET /acme/agents/research-output

The vertex is addressable, auditable, protected by the Vertex Firewall, and usable by people, agents, scripts, and workflows.

Where Node Vertex fits with MCP and A2A

MCP and A2A are useful when agents need formal protocol-level tool access or structured agent interoperability. Node Vertex complements those systems by providing durable, policy-protected HTTP rendezvous points.

Use protocols when you need protocols. Use vertices when agents need simple, secure places to communicate.

Agent coordination patterns

Task handoffs

A research agent posts output. A review agent adds approval. A builder agent picks up approved work.

Status and memory

Agents publish status, short-lived memory, operation results, and next-step instructions at stable URLs.

Files and review

Attach files to a handoff vertex and give humans secure review links with expiration and audit.

Workflow triggers

A listener or polygon reacts when a vertex changes state.

Cross-system coordination

Use HTTP endpoints that existing tools, scripts, and platforms can already call.

Governed exposure

Apply authentication, TTL, rate limits, method policy, and audit to every handoff.

Example: human-reviewed agent handoff

# Research agent leaves work
POST /acme/agents/research-output

# Human reviewer opens a signed review link
GET /acme/reviews/research-output-42?token={signed}

# Review agent records approval
POST /acme/agents/review-status

# Builder agent reads approved work
GET /acme/agents/approved-work

Give every agent a secure place to leave work.

Every workflow starts with a vertex.

Build an agent handoff