CryptowerkFor the record.

Integration Patterns

Choose where to generate records.

Hash locally, register the event, store the retrievalId, then retrieve proof later. The right integration point depends on where your system already completes work.

EVENTArtifactsrequest | responseREGISTERRecordretrievalId + statePROOFVerifyas needed

OpenClaw

Add Cryptowerk as a run-complete step. Hash artifacts locally, register them, then store the retrievalId on the run.

  1. Hash the request, response, or artifact inside the route.
  2. POST /register with lookupInfo and optional callback.
  3. Store retrievalId with the run record.
Coming soon

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