Sign a Bitcoin PSBT with a scoped agent wallet
Changed onRequires agent access plus owner/admin recent MFA or delegated signer credentials with sign_transaction. The route decodes standard Bitcoin PSBT destination outputs, computes input/output/fee totals before signing, rejects excessive fees, evaluates both destination outputs and aggregate destination+fee spend against the agent policy set, and records the signed spend for future policy counters. It also requires an enabled raw-signing-chain policy that explicitly allows bitcoin and secp256k1.
Request
- Base URLhttp://localhost:3200
- Auth
- HTTP bearer
- or API key in header X-Steward-API-Key
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Headers
Unix seconds, Unix milliseconds, or HTTP/ISO timestamp. Sensitive mutating routes require this or X-Steward-Request-Expires-At when request-expiry or request signatures are enforced.
Unix seconds, Unix milliseconds, or HTTP/ISO expiry time. Sensitive mutating routes require this or X-Steward-Request-Timestamp when request-expiry or request signatures are enforced.
Authorization signature for sensitive mutating routes when STEWARD_REQUIRE_AUTH_SIGNATURE=true or production enforcement is enabled. Use v1=<hmac-sha256> or p256=<signature>.
Tenant request-signing key id used to select a managed HMAC signing key. Required when signing with a managed tenant key; omit only for static or app-client signing secrets.
Required for signed sensitive requests and recommended for all sensitive mutating requests. Replays are scoped to authenticated or explicitly signed contexts.
Request body
Response
JSON response
Changes
- info
endpoint added
- info