CLI
Use the preview command-line client for public registry lookups.
clawdbase CLI package. Its verify command currently reads the public registry lookup route; it is not the authenticated, metered REST operation contract.npx clawdbase verify owner/repositoryUse the CLI for interactive inspection of public registry evidence. Use REST API with a scoped Access Key when your application needs authenticated execution, idempotent metering, ledger attribution, or one of the six canonical operations.
Run the preview
npx runs the published package without requiring a global installation. Pin a package version in automated environments so a later Preview release cannot change behavior unexpectedly. Check the returned command status before consuming JSON output in a script.
Commands
clawdbase verify <entity> [--json]
clawdbase search [query] [--type agent|skill] [--json]
clawdbase card <owner/repository> [--json]
clawdbase origin <owner/repository> [--json]
clawdbase widget <owner/repository>Endpoint override
Local development can point the client at another Clawdbase deployment:
CLAWDBASE_API_URL=http://localhost:3000 clawdbase verify owner/repositoryDo not treat an arbitrary endpoint override as trusted. The CLI sends public lookup requests and does not accept a Clawdbase Access Key today.
Output boundary
verify --json returns the public lookup shape used by the CLI. It is different from POST /api/clawdbase/operations/run. Do not build a production policy against CLI presentation fields and assume they are the metered API contract.
The CLI is not “the same enforcement” as the REST operation runner. That wording remains reserved until a released CLI authenticates to the six-operation endpoint and its production behavior is verified end to end.
Failures and automation
A missing registry entity, malformed identifier or unavailable lookup should be treated as an unsuccessful inspection—not as evidence that an artifact is trusted or untrusted. Do not substitute sample values when the command cannot return a confirmed record.
For CI/CD or runtime policy, call the authenticated REST operation that matches the subject you intend to evaluate. Preserve its idempotency key across uncertain retries, validate the operation status and freshness, and apply your own application policy to the confirmed Trust and Confidence values.