Integration Patterns

Choose where to put records on the record.

Capture data record locally, register the event via API, store the retrieval ID with the record then verify anytime. Integrate where your system requests and responds to work.

Need credentials before you wire this in? Issue an API key and credential pair.

Get API key

EVENTArtifactsrequest | responseREGISTERRecordretrievalId + statePROOFVerifyas needed

OpenClaw

Add Cryptowerk as a skill. Uses cURL calls to get an API key, hash files locally, register them at scale and creates verifiable seals as sidecars.

  1. Hash the request, response, or files locally.
  2. POST /register with lookupInfo and optional callback.
  3. Store retrievalId and seal with the record.

OpenClaw clawhub install verifiable-data

Open clawhub

Gateway / API layer

Wrap the existing gateway call. Register hashes before or after the upstream model or tool completes.

  1. Build a deterministic payload for the business event.
  2. Hash it locally and register the hash.
  3. Fetch record state and proof later with getseal or callback delivery.

Portkey plugin coming soon

Worker / backend

Use Cryptowerk where jobs already finish. Persist retrievalId with the job so record lookup and proof retrieval are easy later.

  1. Hash artifacts at completion time.
  2. POST /register from the worker.
  3. Persist hash, retrievalId, and status.

See stored fields

AI tools

Expose Cryptowerk through your own backend tool instead of letting the model call it directly.

  1. Define a backend tool for register.
  2. Define a backend tool for getseal.
  3. Keep credentials and raw logic server-side.

Open playground