Approve Hyperliquid builder-code fee cap for an agent
Changed onOperator recovery endpoint. Auth deliberately accepts platform operators or tenant admins and must not require an agent JWT, so humans can recover funds when the agent token is expired. Raw signing keys never leave the vault; all recovery actions are audited and idempotency-protected. Platform-key only route that submits Hyperliquid's user-signed approveBuilderFee action. The approval must be signed by the agent's master Hyperliquid wallet, not an API/agent wallet.
Request
- Base URLhttp://localhost:3200
- AuthAPI key in header X-Steward-Platform-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
Example request
{
"maxFeeRate": "0.1%"
}Response
JSON response
Changes
- info
endpoint added
- info