Getting Started

Retrieve `OPENAI_API_KEY` from project scope for `prod` and return just the raw value.

List project secrets tagged `payments` and show only stale entries matching `STRIPE_*`.

Set `STRIPE_SECRET_KEY` in project scope with tags `payments,prod` and a TTL of 86400 seconds.

Delete `LEGACY_TOKEN` from global scope and confirm whether it existed.

Check whether `GITHUB_TOKEN` exists in project scope and return true/false.

Export only `OPENAI_API_KEY` and `STRIPE_KEY` as `.env` for `prod`.

Import this `.env` content into project scope in dry-run mode and report what would change.

Validate `.q-ring.json` at this path and show missing, stale, and expired required keys.

Generate `.env` content from the project manifest for `staging` without writing files.

Inspect `DB_PASSWORD` and summarize scope, decay state, tags, and entanglement metadata.

Detect current environment for this project path and include the detection source.

Generate an `api-key` with prefix `sk-` and save it as `OPENAI_API_KEY` in project scope.

Entangle `API_KEY` in this project with `API_KEY_BACKUP` in another project path.

Remove entanglement between `API_KEY` and `API_KEY_BACKUP` and confirm success.

Create an ephemeral tunnel value with TTL 300 and maxReads 1, then return the tunnel ID.

Read tunnel `tu_abc123` once and return value or not-found/expired status.

List all active tunnels with read counts and time remaining.

Destroy tunnel `tu_abc123` immediately and confirm whether it existed.

Pack keys `OPENAI_API_KEY` and `STRIPE_KEY` into an encrypted bundle using this passphrase.

Unpack this teleport bundle in dry-run mode and list keys and scopes that would be imported.

Return last 100 `read` audit events for `OPENAI_API_KEY` in reverse chronological order.

Detect anomalies for `OPENAI_API_KEY` and include recommendations.

Run a project-scope health check and summarize healthy/stale/expired plus anomaly count.

Validate `OPENAI_API_KEY` with provider auto-detection and return provider + latency.

List available validation providers with descriptions and known key prefixes.

Register an HTTP hook for `DB_PASSWORD` rotate events to this URL with a clear description.

List all registered hooks and include type, match criteria, and enabled status.

Remove hook `hk_abc123` and return a not-found error if it does not exist.

Run `node scripts/smoke.js` with only `OPENAI_API_KEY` injected using restricted profile.

Scan `./src` for hardcoded secrets and return file, line, key name, and entropy.

Return redacted project context for this path including manifest and recent actions.

Remember the note `rotated Stripe keys after release` under key `release_notes`.

Recall key `release_notes`; if omitted, list all memory keys and update times.

Forget memory key `release_notes` and report whether it was present.

Lint these files for hardcoded secrets in fix mode and return structured fix results.

Analyze project secrets for unused keys, stale entries, and top read frequency.

Start the live status dashboard on port 9876 and return the local URL — page surfaces KPIs, manifest gaps, policy posture, approvals, hooks, anomalies, and a filterable 24h audit feed without ever rendering secret values.

Run one agent scan with auto-rotate enabled across these project paths and return report JSON.

Verify audit hash-chain integrity and show first break location if tampering is detected.

Export audit events as JSON from 2026-03-01 until now.

Attempt provider-native rotation for `OPENAI_API_KEY` and store the new value if rotated.

Run CI batch validation for project scope and return pass/fail summary JSON.

Check whether command `npm publish` is allowed by exec policy for this project path.

Return governance policy summary for this project, including tool and secret lifecycle rules.