Skip to main content

​
POST /execute

Executes a queued SafeTx. The agent EOA relays execTransaction and pays BNB gas. Its signing behavior depends on whose signatures are already on the row:
  • User signatures below threshold, screening on: the agent adds its confirmation (2 of 2) via the Safe Transaction Service, then executes. Called after an APPROVE verdict or a Telegram approval.
  • User signatures meet the threshold (starter wallets, or screening-off with a backup co-signature): relay-only — the agent submits and pays gas but contributes no signature.
  • Screening off, below threshold: refused with “Awaiting backup co-signature” — no caller (client, Telegram, MCP, or the agent itself) can make the agent sign an unscreened transaction. Complete the row via /cosign or the Safe app. Legacy v1 accounts without a backup key are exempt.
Idempotency and nonce races are handled server-side: if the Safe’s on-chain nonce already passed the row’s nonce, the server checks whether this transaction was executed from the Safe app (the override path) before marking it superseded.

​
Request

​
Response