Verae Node-RED tools
Nodes and flows that connect your automation to Verae over NATS, with billing that meters work and calls the Verae API for digests-only timestamping. Metadata and object storage stay under your control. This site explains how the tools work.
Documentation only — not a hosted Node-RED
nodered.verae.ai does not publish a public Node-RED host or editor. You run Node-RED in your own environment. Runtime, flows, and credentials stay with you.
How it works
- Hash locally. Flows work with SHA-256 digests (and optional metadata handles). Document bytes do not need to leave your network.
- Publish on NATS. Verae nodes talk to nats.verae.ai with your account credentials — job requests, receipts, and status on queue subjects.
- Billing meters the work. The billing path authorizes and accounts for each stamp/prove before work hits the API.
- API stamps the digest. Billing calls the Verae stamp API (api.verae.ai) directly. Digests-only registration; chain holds the multi-hash.
- Metadata & storage stay yours. ERP / ITAD / API metadata stay off-chain as versioned JSONL and link to the digest; optional Peergos holds objects. Payloads are not written on chain.
Sample workflow
Example Node-RED path: hash locally, publish on NATS, billing meters the request, API stamps the digest, then append versioned metadata as JSONL (optional Peergos archive).
- Inject / file — business event or document arrives in the flow.
- SHA-256 — digest computed on your side; bytes need not leave your network.
- NATS out — publish the stamp/prove request to nats.verae.ai.
- Billing — meters and authorizes the request.
- API stamp — billing calls api.verae.ai; digests-only registration.
- Receipt — confirmation returns on NATS / the response path.
- Metadata JSONL — append a versioned ERP / ITAD / API metadata line linked to the digest.
- Optional Peergos — archive related objects to your Peergos home.
Tooling map
NATS nodes
Connect, publish, and subscribe on Verae subjects for stamp, prove, and receipt events.
Billing-aware requests
Each request carries your Verae credentials so metering happens before the API stamps.
API stamp / prove
Digests-only timestamping and existence checks via the Verae API behind the NATS path.
Metadata & Peergos helpers
Attach off-chain ERP / ITAD / API metadata to a digest, and archive objects to your Peergos home.
Version-controlled metadata behind hashes
Digests on the chain are fixed fingerprints. In Node-RED, ERP / ITAD / API metadata ride beside those digests so you can track versioned metadata over time — see what changed behind a hashed item as it moves through enterprise workflows (status, ownership, location, approvals, schema revisions) without rewriting the hash itself. Each meaningful state can mint or reference a new digest while metadata history shows how the business record evolved. Metadata is stored as JSONL (JSON Lines) — one versioned record per line — so history appends cleanly and stays easy to stream, ship, and audit.
- Hash = immutable content fingerprint (Verae API via NATS + billing)
- Metadata = versioned ERP / ITAD / API fields in JSONL over time
- Together = audit how enterprise changes relate to each stamped digest
What you run yourself
- Node-RED 3.x / 4.x on your laptop, server, or private network
- Verae account credentials for NATS + billing
- Optional Peergos home if you archive objects alongside digests