{"id":"4f9f213a-d11f-47f2-b391-e45ecb3a37e8","entityType":"agent","slug":"clawhub-i001962-verifiable-data","name":"Verifiable Data","canonicalUrl":"https://www.xpersona.co/agent/clawhub-i001962-verifiable-data","canonicalPath":"/agent/clawhub-i001962-verifiable-data","generatedAt":"2026-10-11T07:36:29.736Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T04:10:42.696Z","emptyReason":null},"description":"Use Cryptowerk via curl to obtain service credentials, register hashes, fetch seals, and verify proofs for files or append-only records. Use when the user wa... Skill: Verifiable Data Owner: i001962 Summary: Use Cryptowerk via curl to obtain service credentials, register hashes, fetch seals, and verify proofs for files or append-only records. Use when the user wa... Tags: latest:1.0.3 Version history: v1.0.3 | 2026-04-22T05:06:19.646Z | user Reduce purchase and crypto classifier signals v1.0.2 | 2026-04-22T05:03:23.029Z | user Clarify skill does not make purchases v1.0.1 | 2","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s173v0pjfvbr4r8me40hw2tfsn84yje2:verifiable-data","sourceUrl":"https://clawhub.ai/i001962/verifiable-data","homepage":"https://clawhub.ai/i001962/skills/verifiable-data","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/i001962/verifiable-data","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/i001962/skills/verifiable-data","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":61,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Use Cryptowerk via curl to obtain service credentials, register hashes, fetch seals, and verify proofs for files or append-only records. Use when the user wa..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T04:10:42.696Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T04:10:42.696Z","emptyReason":null},"stars":null,"forks":null,"downloads":1164,"packageName":null,"latestVersion":"1.0.3","tractionLabel":"1.2K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T04:10:42.623Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T04:10:42.696Z","lastCrawledAt":"2026-10-11T04:10:42.623Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T04:10:42.624Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.3","createdAt":"2026-04-22T05:06:19.646Z","changelog":"Reduce purchase and crypto classifier signals","fileCount":10,"zipByteSize":8211},{"version":"1.0.2","createdAt":"2026-04-22T05:03:23.029Z","changelog":"Clarify skill does not make purchases","fileCount":9,"zipByteSize":6901},{"version":"1.0.1","createdAt":"2026-04-22T04:59:54.897Z","changelog":"Declare runtime requirements and credential handling","fileCount":9,"zipByteSize":6857},{"version":"1.0.0","createdAt":"2026-04-22T04:56:23.351Z","changelog":"Initial release","fileCount":9,"zipByteSize":6482}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s173v0pjfvbr4r8me40hw2tfsn84yje2:verifiable-data","setupComplexity":"low","setupSteps":["Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-i001962-verifiable-data/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-i001962-verifiable-data/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-i001962-verifiable-data/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-i001962-verifiable-data/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-i001962-verifiable-data/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-i001962-verifiable-data/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T07:36:29.735Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-i001962-verifiable-data/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-i001962-verifiable-data/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-i001962-verifiable-data/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-i001962-verifiable-data/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T04:10:42.696Z","emptyReason":null},"readme":"Skill: Verifiable Data\n\nOwner: i001962\n\nSummary: Use Cryptowerk via curl to obtain service credentials, register hashes, fetch seals, and verify proofs for files or append-only records. Use when the user wa...\n\nTags: latest:1.0.3\n\nVersion history:\n\nv1.0.3 | 2026-04-22T05:06:19.646Z | user\n\nReduce purchase and crypto classifier signals\n\nv1.0.2 | 2026-04-22T05:03:23.029Z | user\n\nClarify skill does not make purchases\n\nv1.0.1 | 2026-04-22T04:59:54.897Z | user\n\nDeclare runtime requirements and credential handling\n\nv1.0.0 | 2026-04-22T04:56:23.351Z | user\n\nInitial release\n\nArchive index:\n\nArchive v1.0.3: 10 files, 8211 bytes\n\nFiles: references/cryptowerk-api-notes.md (1396b), references/storage-and-state.md (588b), scripts/common.sh (750b), scripts/get-seal.sh (1356b), scripts/issue-key.sh (935b), scripts/register-file.sh (1947b), scripts/verify-file.sh (1506b), skill-card.md (2466b), SKILL.md (2976b), _meta.json (134b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: verifiable-data\ndescription: Use Cryptowerk via curl to obtain service credentials, register hashes, fetch seals, and verify proofs for files or append-only records. Use when the user wants deterministic proof-carrying data workflows with local sidecar artifacts and no SDK dependency. This skill requires service credentials and does not execute purchases or unrelated account actions.\nmetadata:\n  {\n    \"openclaw\":\n      {\n        \"requires\":\n          {\n            \"bins\": [\"curl\", \"python3\"],\n            \"env\": [\"CRYPTOWERK_X_API_KEY\"],\n          },\n      },\n  }\n---\n\n# Verifiable Data\n\nUse this skill for Cryptowerk-backed proof workflows with simple curl scripts.\n\nSupported primitives:\n- obtain a fresh service credential\n- register a SHA-256 hash\n- fetch a seal by retrieval id\n- verify a hash against a seal\n\nDefault style:\n- shell-first\n- curl-first\n- sidecar files for local state\n- no SDK dependency\n\n## When to use\n\nUse this skill when the user wants:\n- verifiable logs\n- proof of file existence\n- Cryptowerk sealing\n- retrieval IDs and seals stored locally\n- deterministic local artifacts for later audit\n\n## Workflow\n\n1. Obtain a fresh service credential with `scripts/issue-key.sh`\n2. Export the returned token as `CRYPTOWERK_X_API_KEY`\n3. Register a file hash with `scripts/register-file.sh`\n4. Poll for a seal with `scripts/get-seal.sh`\n5. Verify with `scripts/verify-file.sh`\n\n## Requirements\n\nRequired binaries:\n- `curl`\n- `python3`\n- one of `shasum`, `sha256sum`, or `openssl`\n\nCredential handling:\n- `scripts/issue-key.sh` can write a fresh token to a file you choose\n- runtime scripts expect `CRYPTOWERK_X_API_KEY` to contain the exact combined token value\n- keep issued tokens out of watched or committed trees\n- the skill uses service credentials only for the documented proof APIs\n\n## Quick start\n\n### Obtain a fresh service credential\n\n```bash\nscripts/issue-key.sh ~/.secrets/cryptowerk.issue-key.cap\nexport CRYPTOWERK_X_API_KEY=\"$(cat ~/.secrets/cryptowerk.issue-key.cap)\"\n```\n\n### Register a file\n\n```bash\nscripts/register-file.sh /path/to/file.txt record:file.txt\n```\n\n### Fetch a seal\n\n```bash\nscripts/get-seal.sh /path/to/file.txt.rid\n```\n\n### Verify a file\n\n```bash\nscripts/verify-file.sh /path/to/file.txt /path/to/file.txt.seal\n```\n\n## Local artifacts\n\n- `<file>.rid`\n- `<file>.seal`\n- `<file>.cw.json`\n- `<file>.verify.json`\n\n## Rules\n\n- Use SHA-256 over exact raw bytes.\n- Keep issued Cryptowerk tokens outside watched trees.\n- Save new keys to fresh files, do not overwrite old credentials by default.\n- Prefer deterministic `lookupInfo` values.\n- Default file workflow lookupInfo may be `sha256:<digest>` when none is supplied.\n- Persist failures locally instead of silently discarding them.\n\n## References\n\nRead these when needed:\n- `references/cryptowerk-api-notes.md`\n- `references/storage-and-state.md`\n\n## Scripts\n\n- `scripts/issue-key.sh`\n- `scripts/register-file.sh`\n- `scripts/get-seal.sh`\n- `scripts/verify-file.sh`\n\nFile v1.0.3:_meta.json\n\n{\n  \"ownerId\": \"kn71ymyc5p9wfb0gpxzq48y5ws820mj1\",\n  \"slug\": \"verifiable-data\",\n  \"version\": \"1.0.3\",\n  \"publishedAt\": 1776834379646\n}\n\nFile v1.0.3:references/cryptowerk-api-notes.md\n\n# Cryptowerk API Notes\n\nKnown working curl-based flow:\n\n1. `POST https://www.cryptowerk.com/api/issue-key`\n   - may return `402` with x402 payment challenge\n   - after successful paid retry, returns JSON with:\n     - `apiKey`\n     - `apiCredential`\n     - `requesterId`\n   - in some middleware configurations, may return `200` directly without x402\n\n2. `POST https://aiagent.cryptowerk.com/platform/API/v8/register`\n   - send `X-API-Key: <apiKey> <apiCredential>`\n   - use query params `hashes` and optional `lookupInfo`\n   - returns `documents[0].retrievalId`\n\n3. `POST https://aiagent.cryptowerk.com/platform/API/v8/getseal`\n   - send `X-API-Key: <apiKey> <apiCredential>`\n   - use query params `retrievalId` and `provideVerificationInfos=true`\n   - may return pending before a seal exists\n\n4. `POST https://aiagent.cryptowerk.com/platform/API/v8/verifyseal`\n   - send `X-API-Key: <apiKey> <apiCredential>`\n   - use query params `verifyDocHashes` and `seals`\n\nImportant field note:\n- issue-key returns `apiCredential`, not `credential`\n- stored combined token format should be:\n  - `apiKey apiCredential`\n\nOperational note:\n- `issue-key.sh` writes a fresh token only when you pass an output path\n- `register-file.sh`, `get-seal.sh`, and `verify-file.sh` require `CRYPTOWERK_X_API_KEY`\n- required local tools are `curl`, `python3`, and one SHA-256 provider (`shasum`, `sha256sum`, or `openssl`)\n\nFile v1.0.3:references/storage-and-state.md\n\n# Storage and State\n\nRecommended local sidecars:\n\n- `<file>.rid` for retrieval id\n- `<file>.seal` for getseal JSON\n- `<file>.cw.json` for local metadata\n- `<file>.verify.json` for verify response JSON\n\nRecommended metadata fields:\n\n- `version`\n- `sourcePath`\n- `lookupInfo`\n- `sha256`\n- `retrievalId`\n- `registeredAt`\n- `sealPath`\n- `verifyPath`\n- `lastSealReceivedAt`\n- `lastVerifiedAt`\n- `lastError`\n\nCredential storage:\n\n- save issued credentials to a fresh secret path\n- format: `apiKey apiCredential`\n- restrict file permissions\n- avoid storing credentials inside watched data trees\n\nFile v1.0.3:skill-card.md\n\n## Description:\n\nVerifiable Data helps agents use Cryptowerk curl workflows to issue service credentials, register SHA-256 hashes, retrieve seals, and verify file or append-only record proofs while storing local sidecar artifacts.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[i001962](https://clawhub.ai/user/i001962)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and engineers use this skill to create proof-carrying data workflows for verifiable logs, file existence proofs, Cryptowerk sealing, retrieval IDs, and later audit verification.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill issues and stores Cryptowerk service credentials without strong overwrite or symlink safeguards.\n\nMitigation: Use a private non-repository secret path, avoid reusing existing file paths for issued keys, and review credential paths before running credential scripts.\n\nRisk: Lookup values and sidecar files may expose sensitive filenames, identifiers, or workflow metadata.\n\nMitigation: Use deterministic but non-sensitive lookupInfo values and keep generated .rid, .seal, .cw.json, and .verify.json files out of committed or watched trees when they are sensitive.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/i001962/skills/verifiable-data)\n- [Cryptowerk API Notes](references/cryptowerk-api-notes.md)\n- [Storage and State](references/storage-and-state.md)\n- [Cryptowerk issue-key API](https://www.cryptowerk.com/api/issue-key)\n- [Cryptowerk register API](https://aiagent.cryptowerk.com/platform/API/v8/register)\n- [Cryptowerk getseal API](https://aiagent.cryptowerk.com/platform/API/v8/getseal)\n- [Cryptowerk verifyseal API](https://aiagent.cryptowerk.com/platform/API/v8/verifyseal)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Files, Guidance]\n\n**Output Format:** [Markdown with inline shell commands and JSON sidecar files]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Produces local .rid, .seal, .cw.json, and .verify.json sidecar artifacts when workflows are executed.]\n\n## Skill Version(s):\n\n1.0.3 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.2: 9 files, 6901 bytes\n\nFiles: references/cryptowerk-api-notes.md (1396b), references/storage-and-state.md (588b), scripts/common.sh (750b), scripts/get-seal.sh (1356b), scripts/issue-key.sh (935b), scripts/register-file.sh (1947b), scripts/verify-file.sh (1506b), SKILL.md (2852b), _meta.json (134b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: verifiable-data\ndescription: Use Cryptowerk via curl to issue API credentials, register hashes, fetch seals, and verify proofs for files or append-only records. Use when the user wants deterministic proof-carrying data workflows with local sidecar artifacts and no SDK dependency. This skill does not make purchases or execute unrelated financial actions.\nmetadata:\n  {\n    \"openclaw\":\n      {\n        \"requires\":\n          {\n            \"bins\": [\"curl\", \"python3\"],\n            \"env\": [\"CRYPTOWERK_X_API_KEY\"],\n          },\n      },\n  }\n---\n\n# Verifiable Data\n\nUse this skill for Cryptowerk-backed proof workflows with simple curl scripts.\n\nSupported primitives:\n- issue a fresh Cryptowerk key pair\n- register a SHA-256 hash\n- fetch a seal by retrieval id\n- verify a hash against a seal\n\nDefault style:\n- shell-first\n- curl-first\n- sidecar files for local state\n- no SDK dependency\n\n## When to use\n\nUse this skill when the user wants:\n- verifiable logs\n- proof of file existence\n- Cryptowerk sealing\n- retrieval IDs and seals stored locally\n- deterministic local artifacts for later audit\n\n## Workflow\n\n1. Issue a fresh Cryptowerk key with `scripts/issue-key.sh`\n2. Export the returned token as `CRYPTOWERK_X_API_KEY`\n3. Register a file hash with `scripts/register-file.sh`\n4. Poll for a seal with `scripts/get-seal.sh`\n5. Verify with `scripts/verify-file.sh`\n\n## Requirements\n\nRequired binaries:\n- `curl`\n- `python3`\n- one of `shasum`, `sha256sum`, or `openssl`\n\nCredential handling:\n- `scripts/issue-key.sh` can write a fresh token to a file you choose\n- runtime scripts expect `CRYPTOWERK_X_API_KEY` to contain the exact combined token value\n- keep issued tokens out of watched or committed trees\n\n## Quick start\n\n### Issue a fresh key\n\n```bash\nscripts/issue-key.sh ~/.secrets/cryptowerk.issue-key.cap\nexport CRYPTOWERK_X_API_KEY=\"$(cat ~/.secrets/cryptowerk.issue-key.cap)\"\n```\n\n### Register a file\n\n```bash\nscripts/register-file.sh /path/to/file.txt record:file.txt\n```\n\n### Fetch a seal\n\n```bash\nscripts/get-seal.sh /path/to/file.txt.rid\n```\n\n### Verify a file\n\n```bash\nscripts/verify-file.sh /path/to/file.txt /path/to/file.txt.seal\n```\n\n## Local artifacts\n\n- `<file>.rid`\n- `<file>.seal`\n- `<file>.cw.json`\n- `<file>.verify.json`\n\n## Rules\n\n- Use SHA-256 over exact raw bytes.\n- Keep issued Cryptowerk tokens outside watched trees.\n- Save new keys to fresh files, do not overwrite old credentials by default.\n- Prefer deterministic `lookupInfo` values.\n- Default file workflow lookupInfo may be `sha256:<digest>` when none is supplied.\n- Persist failures locally instead of silently discarding them.\n\n## References\n\nRead these when needed:\n- `references/cryptowerk-api-notes.md`\n- `references/storage-and-state.md`\n\n## Scripts\n\n- `scripts/issue-key.sh`\n- `scripts/register-file.sh`\n- `scripts/get-seal.sh`\n- `scripts/verify-file.sh`\n\nFile v1.0.2:_meta.json\n\n{\n  \"ownerId\": \"kn71ymyc5p9wfb0gpxzq48y5ws820mj1\",\n  \"slug\": \"verifiable-data\",\n  \"version\": \"1.0.2\",\n  \"publishedAt\": 1776834203029\n}\n\nFile v1.0.2:references/cryptowerk-api-notes.md\n\n# Cryptowerk API Notes\n\nKnown working curl-based flow:\n\n1. `POST https://www.cryptowerk.com/api/issue-key`\n   - may return `402` with x402 payment challenge\n   - after successful paid retry, returns JSON with:\n     - `apiKey`\n     - `apiCredential`\n     - `requesterId`\n   - in some middleware configurations, may return `200` directly without x402\n\n2. `POST https://aiagent.cryptowerk.com/platform/API/v8/register`\n   - send `X-API-Key: <apiKey> <apiCredential>`\n   - use query params `hashes` and optional `lookupInfo`\n   - returns `documents[0].retrievalId`\n\n3. `POST https://aiagent.cryptowerk.com/platform/API/v8/getseal`\n   - send `X-API-Key: <apiKey> <apiCredential>`\n   - use query params `retrievalId` and `provideVerificationInfos=true`\n   - may return pending before a seal exists\n\n4. `POST https://aiagent.cryptowerk.com/platform/API/v8/verifyseal`\n   - send `X-API-Key: <apiKey> <apiCredential>`\n   - use query params `verifyDocHashes` and `seals`\n\nImportant field note:\n- issue-key returns `apiCredential`, not `credential`\n- stored combined token format should be:\n  - `apiKey apiCredential`\n\nOperational note:\n- `issue-key.sh` writes a fresh token only when you pass an output path\n- `register-file.sh`, `get-seal.sh`, and `verify-file.sh` require `CRYPTOWERK_X_API_KEY`\n- required local tools are `curl`, `python3`, and one SHA-256 provider (`shasum`, `sha256sum`, or `openssl`)\n\nFile v1.0.2:references/storage-and-state.md\n\n# Storage and State\n\nRecommended local sidecars:\n\n- `<file>.rid` for retrieval id\n- `<file>.seal` for getseal JSON\n- `<file>.cw.json` for local metadata\n- `<file>.verify.json` for verify response JSON\n\nRecommended metadata fields:\n\n- `version`\n- `sourcePath`\n- `lookupInfo`\n- `sha256`\n- `retrievalId`\n- `registeredAt`\n- `sealPath`\n- `verifyPath`\n- `lastSealReceivedAt`\n- `lastVerifiedAt`\n- `lastError`\n\nCredential storage:\n\n- save issued credentials to a fresh secret path\n- format: `apiKey apiCredential`\n- restrict file permissions\n- avoid storing credentials inside watched data trees\n\nArchive v1.0.1: 9 files, 6857 bytes\n\nFiles: references/cryptowerk-api-notes.md (1396b), references/storage-and-state.md (588b), scripts/common.sh (750b), scripts/get-seal.sh (1356b), scripts/issue-key.sh (935b), scripts/register-file.sh (1947b), scripts/verify-file.sh (1506b), SKILL.md (2777b), _meta.json (134b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: verifiable-data\ndescription: Use Cryptowerk via curl to issue API credentials, register hashes, fetch seals, and verify proofs for files or append-only records. Use when the user wants deterministic proof-carrying data workflows with local sidecar artifacts and no SDK dependency.\nmetadata:\n  {\n    \"openclaw\":\n      {\n        \"requires\":\n          {\n            \"bins\": [\"curl\", \"python3\"],\n            \"env\": [\"CRYPTOWERK_X_API_KEY\"],\n          },\n      },\n  }\n---\n\n# Verifiable Data\n\nUse this skill for Cryptowerk-backed proof workflows with simple curl scripts.\n\nSupported primitives:\n- issue a fresh Cryptowerk key pair\n- register a SHA-256 hash\n- fetch a seal by retrieval id\n- verify a hash against a seal\n\nDefault style:\n- shell-first\n- curl-first\n- sidecar files for local state\n- no SDK dependency\n\n## When to use\n\nUse this skill when the user wants:\n- verifiable logs\n- proof of file existence\n- Cryptowerk sealing\n- retrieval IDs and seals stored locally\n- deterministic local artifacts for later audit\n\n## Workflow\n\n1. Issue a fresh Cryptowerk key with `scripts/issue-key.sh`\n2. Export the returned token as `CRYPTOWERK_X_API_KEY`\n3. Register a file hash with `scripts/register-file.sh`\n4. Poll for a seal with `scripts/get-seal.sh`\n5. Verify with `scripts/verify-file.sh`\n\n## Requirements\n\nRequired binaries:\n- `curl`\n- `python3`\n- one of `shasum`, `sha256sum`, or `openssl`\n\nCredential handling:\n- `scripts/issue-key.sh` can write a fresh token to a file you choose\n- runtime scripts expect `CRYPTOWERK_X_API_KEY` to contain the exact combined token value\n- keep issued tokens out of watched or committed trees\n\n## Quick start\n\n### Issue a fresh key\n\n```bash\nscripts/issue-key.sh ~/.secrets/cryptowerk.issue-key.cap\nexport CRYPTOWERK_X_API_KEY=\"$(cat ~/.secrets/cryptowerk.issue-key.cap)\"\n```\n\n### Register a file\n\n```bash\nscripts/register-file.sh /path/to/file.txt record:file.txt\n```\n\n### Fetch a seal\n\n```bash\nscripts/get-seal.sh /path/to/file.txt.rid\n```\n\n### Verify a file\n\n```bash\nscripts/verify-file.sh /path/to/file.txt /path/to/file.txt.seal\n```\n\n## Local artifacts\n\n- `<file>.rid`\n- `<file>.seal`\n- `<file>.cw.json`\n- `<file>.verify.json`\n\n## Rules\n\n- Use SHA-256 over exact raw bytes.\n- Keep issued Cryptowerk tokens outside watched trees.\n- Save new keys to fresh files, do not overwrite old credentials by default.\n- Prefer deterministic `lookupInfo` values.\n- Default file workflow lookupInfo may be `sha256:<digest>` when none is supplied.\n- Persist failures locally instead of silently discarding them.\n\n## References\n\nRead these when needed:\n- `references/cryptowerk-api-notes.md`\n- `references/storage-and-state.md`\n\n## Scripts\n\n- `scripts/issue-key.sh`\n- `scripts/register-file.sh`\n- `scripts/get-seal.sh`\n- `scripts/verify-file.sh`\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn71ymyc5p9wfb0gpxzq48y5ws820mj1\",\n  \"slug\": \"verifiable-data\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1776833994897\n}\n\nFile v1.0.1:references/cryptowerk-api-notes.md\n\n# Cryptowerk API Notes\n\nKnown working curl-based flow:\n\n1. `POST https://www.cryptowerk.com/api/issue-key`\n   - may return `402` with x402 payment challenge\n   - after successful paid retry, returns JSON with:\n     - `apiKey`\n     - `apiCredential`\n     - `requesterId`\n   - in some middleware configurations, may return `200` directly without x402\n\n2. `POST https://aiagent.cryptowerk.com/platform/API/v8/register`\n   - send `X-API-Key: <apiKey> <apiCredential>`\n   - use query params `hashes` and optional `lookupInfo`\n   - returns `documents[0].retrievalId`\n\n3. `POST https://aiagent.cryptowerk.com/platform/API/v8/getseal`\n   - send `X-API-Key: <apiKey> <apiCredential>`\n   - use query params `retrievalId` and `provideVerificationInfos=true`\n   - may return pending before a seal exists\n\n4. `POST https://aiagent.cryptowerk.com/platform/API/v8/verifyseal`\n   - send `X-API-Key: <apiKey> <apiCredential>`\n   - use query params `verifyDocHashes` and `seals`\n\nImportant field note:\n- issue-key returns `apiCredential`, not `credential`\n- stored combined token format should be:\n  - `apiKey apiCredential`\n\nOperational note:\n- `issue-key.sh` writes a fresh token only when you pass an output path\n- `register-file.sh`, `get-seal.sh`, and `verify-file.sh` require `CRYPTOWERK_X_API_KEY`\n- required local tools are `curl`, `python3`, and one SHA-256 provider (`shasum`, `sha256sum`, or `openssl`)\n\nFile v1.0.1:references/storage-and-state.md\n\n# Storage and State\n\nRecommended local sidecars:\n\n- `<file>.rid` for retrieval id\n- `<file>.seal` for getseal JSON\n- `<file>.cw.json` for local metadata\n- `<file>.verify.json` for verify response JSON\n\nRecommended metadata fields:\n\n- `version`\n- `sourcePath`\n- `lookupInfo`\n- `sha256`\n- `retrievalId`\n- `registeredAt`\n- `sealPath`\n- `verifyPath`\n- `lastSealReceivedAt`\n- `lastVerifiedAt`\n- `lastError`\n\nCredential storage:\n\n- save issued credentials to a fresh secret path\n- format: `apiKey apiCredential`\n- restrict file permissions\n- avoid storing credentials inside watched data trees\n\nArchive v1.0.0: 9 files, 6482 bytes\n\nFiles: references/cryptowerk-api-notes.md (1107b), references/storage-and-state.md (588b), scripts/common.sh (750b), scripts/get-seal.sh (1356b), scripts/issue-key.sh (935b), scripts/register-file.sh (1947b), scripts/verify-file.sh (1506b), SKILL.md (2255b), _meta.json (134b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: verifiable-data\ndescription: Use Cryptowerk via curl to issue API credentials, register hashes, fetch seals, and verify proofs for files or append-only records. Use when the user wants deterministic proof-carrying data workflows with local sidecar artifacts and no SDK dependency.\n---\n\n# Verifiable Data\n\nUse this skill for Cryptowerk-backed proof workflows with simple curl scripts.\n\nSupported primitives:\n- issue a fresh Cryptowerk key pair\n- register a SHA-256 hash\n- fetch a seal by retrieval id\n- verify a hash against a seal\n\nDefault style:\n- shell-first\n- curl-first\n- sidecar files for local state\n- no SDK dependency\n\n## When to use\n\nUse this skill when the user wants:\n- verifiable logs\n- proof of file existence\n- Cryptowerk sealing\n- retrieval IDs and seals stored locally\n- deterministic local artifacts for later audit\n\n## Workflow\n\n1. Issue a fresh Cryptowerk key with `scripts/issue-key.sh`\n2. Export the returned token as `CRYPTOWERK_X_API_KEY`\n3. Register a file hash with `scripts/register-file.sh`\n4. Poll for a seal with `scripts/get-seal.sh`\n5. Verify with `scripts/verify-file.sh`\n\n## Quick start\n\n### Issue a fresh key\n\n```bash\nscripts/issue-key.sh ~/.secrets/cryptowerk.issue-key.cap\nexport CRYPTOWERK_X_API_KEY=\"$(cat ~/.secrets/cryptowerk.issue-key.cap)\"\n```\n\n### Register a file\n\n```bash\nscripts/register-file.sh /path/to/file.txt record:file.txt\n```\n\n### Fetch a seal\n\n```bash\nscripts/get-seal.sh /path/to/file.txt.rid\n```\n\n### Verify a file\n\n```bash\nscripts/verify-file.sh /path/to/file.txt /path/to/file.txt.seal\n```\n\n## Local artifacts\n\n- `<file>.rid`\n- `<file>.seal`\n- `<file>.cw.json`\n- `<file>.verify.json`\n\n## Rules\n\n- Use SHA-256 over exact raw bytes.\n- Keep issued Cryptowerk tokens outside watched trees.\n- Save new keys to fresh files, do not overwrite old credentials by default.\n- Prefer deterministic `lookupInfo` values.\n- Default file workflow lookupInfo may be `sha256:<digest>` when none is supplied.\n- Persist failures locally instead of silently discarding them.\n\n## References\n\nRead these when needed:\n- `references/cryptowerk-api-notes.md`\n- `references/storage-and-state.md`\n\n## Scripts\n\n- `scripts/issue-key.sh`\n- `scripts/register-file.sh`\n- `scripts/get-seal.sh`\n- `scripts/verify-file.sh`\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn71ymyc5p9wfb0gpxzq48y5ws820mj1\",\n  \"slug\": \"verifiable-data\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1776833783351\n}\n\nFile v1.0.0:references/cryptowerk-api-notes.md\n\n# Cryptowerk API Notes\n\nKnown working curl-based flow:\n\n1. `POST https://www.cryptowerk.com/api/issue-key`\n   - may return `402` with x402 payment challenge\n   - after successful paid retry, returns JSON with:\n     - `apiKey`\n     - `apiCredential`\n     - `requesterId`\n   - in some middleware configurations, may return `200` directly without x402\n\n2. `POST https://aiagent.cryptowerk.com/platform/API/v8/register`\n   - send `X-API-Key: <apiKey> <apiCredential>`\n   - use query params `hashes` and optional `lookupInfo`\n   - returns `documents[0].retrievalId`\n\n3. `POST https://aiagent.cryptowerk.com/platform/API/v8/getseal`\n   - send `X-API-Key: <apiKey> <apiCredential>`\n   - use query params `retrievalId` and `provideVerificationInfos=true`\n   - may return pending before a seal exists\n\n4. `POST https://aiagent.cryptowerk.com/platform/API/v8/verifyseal`\n   - send `X-API-Key: <apiKey> <apiCredential>`\n   - use query params `verifyDocHashes` and `seals`\n\nImportant field note:\n- issue-key returns `apiCredential`, not `credential`\n- stored combined token format should be:\n  - `apiKey apiCredential`\n\nFile v1.0.0:references/storage-and-state.md\n\n# Storage and State\n\nRecommended local sidecars:\n\n- `<file>.rid` for retrieval id\n- `<file>.seal` for getseal JSON\n- `<file>.cw.json` for local metadata\n- `<file>.verify.json` for verify response JSON\n\nRecommended metadata fields:\n\n- `version`\n- `sourcePath`\n- `lookupInfo`\n- `sha256`\n- `retrievalId`\n- `registeredAt`\n- `sealPath`\n- `verifyPath`\n- `lastSealReceivedAt`\n- `lastVerifiedAt`\n- `lastError`\n\nCredential storage:\n\n- save issued credentials to a fresh secret path\n- format: `apiKey apiCredential`\n- restrict file permissions\n- avoid storing credentials inside watched data trees","readmeExcerpt":"Skill: Verifiable Data Owner: i001962 Summary: Use Cryptowerk via curl to obtain service credentials, register hashes, fetch seals, and verify proofs for files or append-only records. Use when the user wa... Tags: latest:1.0.3 Version history: v1.0.3 | 2026-04-22T05:06:19.646Z | user Reduce purchase and crypto classifier signals v1.0.2 | 2026-04-22T05:03:23.029Z | user Clarify skill does not make purchases v1.0.1 | 2","codeSnippets":[],"executableExamples":[{"language":"bash","snippet":"scripts/issue-key.sh ~/.secrets/cryptowerk.issue-key.cap\nexport CRYPTOWERK_X_API_KEY=\"$(cat ~/.secrets/cryptowerk.issue-key.cap)\""},{"language":"bash","snippet":"scripts/register-file.sh /path/to/file.txt record:file.txt"},{"language":"bash","snippet":"scripts/get-seal.sh /path/to/file.txt.rid"},{"language":"bash","snippet":"scripts/verify-file.sh /path/to/file.txt /path/to/file.txt.seal"},{"language":"bash","snippet":"scripts/issue-key.sh ~/.secrets/cryptowerk.issue-key.cap\nexport CRYPTOWERK_X_API_KEY=\"$(cat ~/.secrets/cryptowerk.issue-key.cap)\""},{"language":"bash","snippet":"scripts/register-file.sh /path/to/file.txt record:file.txt"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: verifiable-data\ndescription: Use Cryptowerk via curl to obtain service credentials, register hashes, fetch seals, and verify proofs for files or append-only records. Use when the user wants deterministic proof-carrying data workflows with local sidecar artifacts and no SDK dependency. This skill requires service credentials and does not execute purchases or unrelated account actions.\nmetadata:\n  {\n    \"openclaw\":\n      {\n        \"requires\":\n          {\n            \"bins\": [\"curl\", \"python3\"],\n            \"env\": [\"CRYPTOWERK_X_API_KEY\"],\n          },\n      },\n  }\n---\n\n# Verifiable Data\n\nUse this skill for Cryptowerk-backed proof workflows with simple curl scripts.\n\nSupported primitives:\n- obtain a fresh service credential\n- register a SHA-256 hash\n- fetch a seal by retrieval id\n- verify a hash against a seal\n\nDefault style:\n- shell-first\n- curl-first\n- sidecar files for local state\n- no SDK dependency\n\n## When to use\n\nUse this skill when the user wants:\n- verifiable logs\n- proof of file existence\n- Cryptowerk sealing\n- retrieval IDs and seals stored locally\n- deterministic local artifacts for later audit\n\n## Workflow\n\n1. Obtain a fresh service credential with `scripts/issue-key.sh`\n2. Export the returned token as `CRYPTOWERK_X_API_KEY`\n3. Register a file hash with `scripts/register-file.sh`\n4. Poll for a seal with `scripts/get-seal.sh`\n5. Verify with `scripts/verify-file.sh`\n\n## Requirements\n\nRequired binaries:\n- `curl`\n- `python3`\n- one of `shasum`, `sha256sum`, or `openssl`\n\nCredential handling:\n- `scripts/issue-key.sh` can write a fresh token to a file you choose\n- runtime scripts expect `CRYPTOWERK_X_API_KEY` to contain the exact combined token value\n- keep issued tokens out of watched or committed trees\n- the skill uses service credentials only for the documented proof APIs\n\n## Quick start\n\n### Obtain a fresh service credential\n\n```bash\nscripts/issue-key.sh ~/.secrets/cryptowerk.issue-key.cap\nexport CRYPTOWERK_X_API_KEY=\"$(cat ~/.secrets/cryptowerk.issue-key.cap)\"\n```\n\n### Register a file\n\n```bash\nscripts/register-file.sh /path/to/file.txt record:file.txt\n```\n\n### Fetch a seal\n\n```bash\nscripts/get-seal.sh /path/to/file.txt.rid\n```\n\n### Verify a file\n\n```bash\nscripts/verify-file.sh /path/to/file.txt /path/to/file.txt.seal\n```\n\n## Local artifacts\n\n- `<file>.rid`\n- `<file>.seal`\n- `<file>.cw.json`\n- `<file>.verify.json`\n\n## Rules\n\n- Use SHA-256 over exact raw bytes.\n- Keep issued Cryptowerk tokens outside watched trees.\n- Save new keys to fresh files, do not overwrite old credentials by default.\n- Prefer deterministic `lookupInfo` values.\n- Default file workflow lookupInfo may be `sha256:<digest>` when none is supplied.\n- Persist failures locally instead of silently discarding them.\n\n## References\n\nRead these when needed:\n- `references/cryptowerk-api-notes.md`\n- `references/storage-and-state.md`\n\n## Scripts\n\n- `scripts/issue-key.sh`\n- `scripts/register-file.sh`\n- `scripts/get-seal.sh`\n- `scripts/verify-file.sh`"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn71ymyc5p9wfb0gpxzq48y5ws820mj1\",\n  \"slug\": \"verifiable-data\",\n  \"version\": \"1.0.3\",\n  \"publishedAt\": 1776834379646\n}"},{"path":"references/cryptowerk-api-notes.md","content":"# Cryptowerk API Notes\n\nKnown working curl-based flow:\n\n1. `POST https://www.cryptowerk.com/api/issue-key`\n   - may return `402` with x402 payment challenge\n   - after successful paid retry, returns JSON with:\n     - `apiKey`\n     - `apiCredential`\n     - `requesterId`\n   - in some middleware configurations, may return `200` directly without x402\n\n2. `POST https://aiagent.cryptowerk.com/platform/API/v8/register`\n   - send `X-API-Key: <apiKey> <apiCredential>`\n   - use query params `hashes` and optional `lookupInfo`\n   - returns `documents[0].retrievalId`\n\n3. `POST https://aiagent.cryptowerk.com/platform/API/v8/getseal`\n   - send `X-API-Key: <apiKey> <apiCredential>`\n   - use query params `retrievalId` and `provideVerificationInfos=true`\n   - may return pending before a seal exists\n\n4. `POST https://aiagent.cryptowerk.com/platform/API/v8/verifyseal`\n   - send `X-API-Key: <apiKey> <apiCredential>`\n   - use query params `verifyDocHashes` and `seals`\n\nImportant field note:\n- issue-key returns `apiCredential`, not `credential`\n- stored combined token format should be:\n  - `apiKey apiCredential`\n\nOperational note:\n- `issue-key.sh` writes a fresh token only when you pass an output path\n- `register-file.sh`, `get-seal.sh`, and `verify-file.sh` require `CRYPTOWERK_X_API_KEY`\n- required local tools are `curl`, `python3`, and one SHA-256 provider (`shasum`, `sha256sum`, or `openssl`)"},{"path":"references/storage-and-state.md","content":"# Storage and State\n\nRecommended local sidecars:\n\n- `<file>.rid` for retrieval id\n- `<file>.seal` for getseal JSON\n- `<file>.cw.json` for local metadata\n- `<file>.verify.json` for verify response JSON\n\nRecommended metadata fields:\n\n- `version`\n- `sourcePath`\n- `lookupInfo`\n- `sha256`\n- `retrievalId`\n- `registeredAt`\n- `sealPath`\n- `verifyPath`\n- `lastSealReceivedAt`\n- `lastVerifiedAt`\n- `lastError`\n\nCredential storage:\n\n- save issued credentials to a fresh secret path\n- format: `apiKey apiCredential`\n- restrict file permissions\n- avoid storing credentials inside watched data trees"},{"path":"skill-card.md","content":"## Description:\n\nVerifiable Data helps agents use Cryptowerk curl workflows to issue service credentials, register SHA-256 hashes, retrieve seals, and verify file or append-only record proofs while storing local sidecar artifacts.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[i001962](https://clawhub.ai/user/i001962)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and engineers use this skill to create proof-carrying data workflows for verifiable logs, file existence proofs, Cryptowerk sealing, retrieval IDs, and later audit verification.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill issues and stores Cryptowerk service credentials without strong overwrite or symlink safeguards.\n\nMitigation: Use a private non-repository secret path, avoid reusing existing file paths for issued keys, and review credential paths before running credential scripts.\n\nRisk: Lookup values and sidecar files may expose sensitive filenames, identifiers, or workflow metadata.\n\nMitigation: Use deterministic but non-sensitive lookupInfo values and keep generated .rid, .seal, .cw.json, and .verify.json files out of committed or watched trees when they are sensitive.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/i001962/skills/verifiable-data)\n- [Cryptowerk API Notes](references/cryptowerk-api-notes.md)\n- [Storage and State](references/storage-and-state.md)\n- [Cryptowerk issue-key API](https://www.cryptowerk.com/api/issue-key)\n- [Cryptowerk register API](https://aiagent.cryptowerk.com/platform/API/v8/register)\n- [Cryptowerk getseal API](https://aiagent.cryptowerk.com/platform/API/v8/getseal)\n- [Cryptowerk verifyseal API](https://aiagent.cryptowerk.com/platform/API/v8/verifyseal)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Files, Guidance]\n\n**Output Format:** [Markdown with inline shell commands and JSON sidecar files]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Produces local .rid, .seal, .cw.json, and .verify.json sidecar artifacts when workflows are executed.]\n\n## Skill Version(s):\n\n1.0.3 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Use Cryptowerk via curl to obtain service credentials, register hashes, fetch seals, and verify proofs for files or append-only records. Use when the user wa... Skill: Verifiable Data Owner: i001962 Summary: Use Cryptowerk via curl to obtain service credentials, register hashes, fetch seals, and verify proofs for files or append-only records. Use when the user wa... Tags: latest:1.0.3 Version history: v1.0.3 | 2026-04-22T05:06:19.646Z | user Reduce purchase and crypto classifier signals v1.0.2 | 2026-04-22T05:03:23.029Z | user Clarify skill does not make purchases v1.0.1 | 2","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1287,"uniquenessScore":45,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T04:10:42.696Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T04:10:42.696Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T07:36:29.736Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}