privy integrations blockaid get
Read safe metadata for blockaid. Production-app-only cross-app scanning configuration; also requires an enabled verified cookie domain or non-private ecosystem. No production conversion, billing change, domain, account approval or publishing is performed implicitly.
privy integrations blockaid get [options]Options
Section titled “Options”| Option | Description |
|---|---|
--dry-run |
Validate and print the API request without network access or credentials. |
Global options such as --app, --account and --profile also apply. See the command reference overview.
Examples
Section titled “Examples”privy integrations blockaid getBehavior
Section titled “Behavior”- Changes data: no, read-only.
- Scope: app
- Verification: Allowlisted read-back; masked credentials are not exact-value proof; no external integration verification.
- Retries: No automatic write retries.
Related guides
Section titled “Related guides”Inspect the full contract locally with privy schema integrations blockaid get.
Privy CLI is an unofficial, community project by Samarth Saxena. Not affiliated with or endorsed by Privy. The Privy name and wordmark belong to Privy. It uses undocumented dashboard APIs that can change.