The Qredo API and Partner API are being deprecated and will be replaced by a breaking change in Q4. To receive updates about the release, register here.
Qredo Logo

Signing Agent


Web App v1/v2

The new Qredo Web App v2 is now available! If you're using the Signing Agent API, you'll be migrated to the new Web App later. Right now you'll be temporarily redirected to the legacy Web App Web App — Qredo Web App v1. All UI steps and concepts mentioned in this section match the legacy Web App.


  • Signing Agent is a programmatic service allowing you to automate the approval or rejection of transactions
  • It integrates with the Partner API and Web3 Wallets
  • This service is useful for managing high-volume and high-velocity transactions
  • It intuitively integrates with your third-party dApp

Service overview

Signing Agent enables you to automate the approval or rejection of transactions according to your customized rulesets for dedicated connected Wallets.

Signing Agent becomes a programmatic member of your custody group: speeding up the approval process and relieving the demand on trusted parties who make approvals through the Qredo Signing App on their mobile. From the perspective of your custody policies, an automated approval by a Signing Agent equates to one approval by a (human) trusted party. It can be used to create a programmable approver service that listens to incoming approval requests over WebSockets to perform automated custody.

Signing Agent uses a dedicated subset of the Partner API for fetching, approving, and rejecting transactions pending custody. It can operate as a standalone service (exposing a RESTful API to 3rd party applications), or as a library integrated into an application. We recommend deploying the service on premise, on your own infrastructure. We also recommend that every Signing Agent instance be used to manage a unique agent ID, and that multiple instances be deployed (preferably on different cloud infrastructures) in order to meet a multiple signer threshold such as 2 or 3 out of 5.


Partner API
Web3 Wallets

Who uses Signing Agent?

Signing Agent is used by companies and developers requiring:

Together, the transaction creation API, Web3 API, and Signing Agent enable dApp developers, fund managers, and other high-volume, high-velocity transaction entities to programmatically create and approve transactions. All while maintaining custody over your digital assets.


Welcome to the Qredo Signing Agent v2.

Signing Agent v1 is deprecated

As of Q4 2022, Signing Agent v2 replaces v1: Core Client providing a much-simplified implementation.

Partner API entities