Generate a signed bundle with `opa sign --signing-key <private_key_file> --bundle <bundle_dir>` to produce a `.signatures.json` payload.
Build the bundle (`opa build --bundle ...` with the signing flags) so the signature is embedded.
Serve the bundle from your bundle server endpoint.
Configure OPA's `bundles` config with a `signing` section referencing the public key/keyid so OPA verifies the signature on download.
Confirm OPA rejects an unsigned or tampered bundle at activation time.
Known gotchas
The signing key flag is `--signing-key`, not `--key`.
If the configured verification keyid/scope does not match what was used to sign, OPA refuses to activate the bundle — a mismatch fails closed rather than serving stale policy.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp