--- title: "Quant Overledger Integration" description: "Quant Overledger puts many blockchains behind one REST gateway. Workflows read network and contract data, send JSON-RPC calls, record deposits, swaps, and withdrawals, and react to address activity and contract events." url: https://flowrunner.ai/integrations/overledger date_modified: 2026-09-04T14:51:36-07:00 --- # Quant Overledger [Finance](https://flowrunner.ai/integrations/category/finance-accounting) Quant Overledger puts many blockchains behind one REST gateway. Workflows read network and contract data, send JSON-RPC calls, record deposits, swaps, and withdrawals, and react to address activity and contract events. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 3 triggers · 69 actions · API key · available [Quant Overledger website](https://fusion-rollup.quant.dev/) · [Platform Documentation](https://docs.overledger.dev/) · Capability data verified 2026-08-25 1. A scheduled treasury job checks whether a rollup balance should be brought back to layer one 2. Get Deposit Balances and Get Total Staked read the current position 3. Get Supported Swap Tokens supplies the token's own decimals so the amount can be stated in real units 4. The agent confirms the network and token names come from the withdrawal enumeration, not the deposit one 5. The staged withdrawal posts with the amount restated in human units beside the digit string that will be sent 6. The treasury signer approves before Create Withdrawal opens an exit with no cancel route ## What This Integration Enables The most important thing to understand about Overledger is what it does not do. Create Deposit, Create Swap, and Record Stake register something that happened, or is about to happen, in your own wallet on chain. Overledger tracks it and credits it. It does not move tokens for you. Build on that assumption and the connector becomes what it actually is: a bookkeeping and coordination layer over multi chain activity, where the on chain action stays with your signer and the record keeping, the watching, and the follow through become an agent's job. FlowRunner agents read the networks Overledger knows about and the narrower set the rollup can actually bridge to, register and manage their own nodes and RPC providers, send JSON-RPC to the rollup node, and manage deployed contracts and who may reach them. They record deposits, swaps, stakes, and withdrawals, then poll the status operations that re-read the chain rather than the cached record. They also drive Flow Apps, which are server driven multi step forms, and subscribe to address activity and contract events. The base host is a connection setting rather than a constant, because Quant currently labels the documented host as a live testnet and publishes no separate production host, so you point the connection at whatever host your own Overledger contract gives you. ### Without FlowRunner **One integration per chain**: Every network brings its own client, its own node, and its own way of failing **Decimals assumed**: An amount is built assuming eighteen decimals, and a six decimal token is wrong by a factor the API cannot detect **Exits that stall**: A withdrawal is initiated and then forgotten, because nothing on the other side chases the remaining steps ### With FlowRunner **One gateway in front of many chains**: Networks, contracts, subscriptions, and transaction tracking sit behind a single connection **Decimals read from the source**: The token list returns its own decimals, and the amount is restated in human units before anyone approves it **Pending exits surfaced on a schedule**: A daily read reports exactly which withdrawals are waiting to be proved or finalized ## Use Case Scenarios ### A deposit that is confirmed rather than assumed Your signer moves tokens onto the rollup. The agent records the transfer with Create Deposit, carrying the transaction hash, then polls Check Deposit Status rather than Get Deposit, because only the status call re-reads the chain while the plain read returns the cached record. A flow that polls the wrong one can wait forever on a deposit that confirmed minutes ago. Once the status settles, the agent writes the confirmed amount, token, and network into [PostgreSQL](https://flowrunner.ai/integrations/postgresql) and posts a line into [Slack](https://flowrunner.ai/integrations/slack), so the treasury ledger reflects the chain rather than somebody's screenshot. ### Nothing chases a stalled exit, so a flow does A rollup exit runs initiate, prove on layer one, wait out the challenge period, then finalize on layer one, and it takes days. Create Withdrawal only performs the first step. A daily agent calls List Actionable Withdrawals, which reports precisely which withdrawals are now waiting for a prove or a finalize, and posts that list to the treasury channel in [Microsoft Teams](https://flowrunner.ai/integrations/microsoft-teams). As your signer sends each layer one transaction, Record Prove Tx and Record Finalize Tx tell Overledger about it. Funds stop getting stranded because somebody moved on to the next thing. ### Watching an address without running a node Instead of polling a node, the agent subscribes to an address with Subscribe To Address, pinned to the network that actually matters, since the same address exists on every EVM chain. When the address takes part in a transaction, the trigger fires and the agent enriches the event with token pricing from [CoinGecko](https://flowrunner.ai/integrations/coingecko) before writing it to a register in [Airtable](https://flowrunner.ai/integrations/airtable). If a delivery is missed, List Address Events replays what Overledger recorded from a point in time, so a restart does not create a hole in the record. ## Human-in-Loop Highlight Create Withdrawal has no cancel route in this connector. It opens an optimistic rollup exit that then needs two more layer one transactions from your side and a challenge period in between, and the parameters it accepts are easy to get wrong in ways nothing will catch. Withdrawal networks and tokens are a completely different enumeration from the deposit ones, lowercase where the deposit side is uppercase, and carrying tokens the deposit side does not have. Every amount is a plain digit string in the token's smallest units, so treating a six decimal token as an eighteen decimal one is a million fold error that is perfectly valid to the API. So the agent prepares and never sends. It reads the decimals from Get Supported Swap Tokens rather than assuming, restates the amount in human units, names the exact network and token strings it will submit, and posts to the treasury signer: "Ready to withdraw 2,500 uUSD on besu. Digit string is 2500000000 at 6 decimals read from the token list. This exit cannot be cancelled and will need a prove and a finalize on layer one. Approve?" The agent handles every step that can be redone. The one that cannot be undone waits for a person. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 69 actions ### Health and Identity 3 - **Get Health** Returns the gateway's liveness and the SDK versions it supports. Unauthenticated, so it separates a host problem from a credential problem. - **Get Readiness** Returns whether the gateway's own database is reachable. - **Get My User ID** Returns the canonical user id the credential resolves to. The cheapest authenticated connection test, and the value contract grants are keyed on. ### API Keys 3 - **Mint API Key** Issues a new Overledger API key and returns the raw key exactly once. It cannot be read back afterwards, so a workflow that does not capture it immediately has issued a credential nobody holds. - **List API Keys** Returns the caller's API key metadata. Secrets are never included. - **Revoke API Key** Revokes one of the caller's API keys. Key management accepts a bearer token only by design, so a connection configured with an API key cannot mint, list, or revoke keys. ### Networks 3 - **List Networks** Returns every blockchain network Overledger knows about. - **List Fusion Networks** Returns only the networks actually connected to the rollup. A different and narrower set, since a chain Overledger knows about is not necessarily one it can bridge to. - **Get Network Count** Returns how many networks are connected in total. ### Nodes and Providers 6 - **Register Node** Registers a blockchain node so your own infrastructure serves your requests. A public node requires an approved provider domain. - **Remove Node** Unregisters a node. - **List My Nodes** Returns the nodes you have registered. - **List My Providers** Returns your connected RPC providers with their quota state. Used to spot an exhausted provider before requests start failing. - **Update Provider Reset Policy** Sets when an exhausted provider quota counts as reset. The shape depends on the policy type, since a daily policy needs an hour and a monthly one needs a day of month. - **Reactivate Provider Nodes** Brings a provider's nodes back into service after its quota was exhausted. It answers asynchronously, so a flow polls the provider list rather than assuming it finished. ### RPC 1 - **Send JSON-RPC** Sends a JSON-RPC 2.0 request to the rollup node. Scoped to that node only, and a JSON-RPC error arrives inside a successful HTTP response, so the connector raises it rather than handing a flow a result that looks fine. ### Contracts 7 - **List My Deployed Contracts** Returns the contracts you have deployed on the rollup. - **Get My Access Details** Returns both the contracts you deployed and the permissioned contracts somebody else granted you access to. - **Get Contract** Returns a deployed contract's details and its visibility. - **Update Contract Visibility** Sets whether a contract is public, permissioned, or private. Visibility overrides the grant list, so switching a permissioned contract to public keeps the list and ignores it. - **List Contract Permissions** Returns who has been granted access to a permissioned contract. - **Grant Contract Permission** Grants a user access to a permissioned contract. Grants take an Overledger user id, not a wallet address. - **Revoke Contract Permission** Removes a user's access to a permissioned contract. ### Deposits 6 - **Create Deposit** Records a deposit of tokens onto the rollup. It registers what your wallet did on chain rather than performing the transfer itself. - **Get Deposit** Returns a deposit record as Overledger last saw it. The cached view, not a fresh chain read. - **Check Deposit Status** Re-reads the chain and returns the deposit's current on chain status. The operation a polling flow should be calling. - **List My Deposits** Returns your deposits onto the rollup. - **Get Deposit Balances** Returns a wallet's balances of the depositable tokens. - **Get Deposit Allowance** Returns how much of a token a wallet has already approved for deposit. ### Swaps 6 - **Get Supported Swap Tokens** Returns the swappable tokens with their addresses and, critically, their decimals. The authority a workflow should read rather than assuming eighteen. - **Get Swap Quote** Returns a quote with the route and the expected output. - **Create Swap** Records a swap that was executed on chain, so Overledger can track and credit it. - **Get Swap** Returns a swap record as last recorded. - **Check Swap Status** Re-reads the chain and returns the swap's current status. - **List My Swaps** Returns your swaps on the rollup. ### History 2 - **Get My History** Returns your deposits and swaps in one chronological list. The quickest way to assemble an activity statement. - **List My Transactions** Returns your transactions on the rollup. ### Withdrawals 7 - **Create Withdrawal** Initiates an exit from the rollup to layer one. Only the first of several steps, and the connector publishes no cancel route for it. - **Get Withdrawal** Returns a withdrawal record as last recorded. - **Check Withdrawal Status** Re-reads both chains and returns the withdrawal's current status. - **List Actionable Withdrawals** Returns the withdrawals now waiting for you to prove or finalize them. The operation worth running on a schedule, because nothing else will remind you. - **List My Withdrawals** Returns your withdrawals from the rollup. - **Record Prove Tx** Tells Overledger the layer one prove transaction has been sent. - **Record Finalize Tx** Tells Overledger the layer one finalize transaction has been sent, which completes the withdrawal. ### Staking 4 - **Get Staking Address** Returns the address QNT should be staked to for this user. It is per user, so a hard coded address copied from an old flow sends tokens this account will never be credited for. - **Record Stake** Registers a stake transaction with Overledger. - **List My Stakes** Returns your recorded stake transactions. - **Get Total Staked** Returns how much QNT this user has staked in total. ### Flow Apps 4 - **List Flow Apps** Returns the Flow Apps available to you. - **Get Flow App** Returns a Flow App's details and its published versions. Pinning a version matters, because an unpinned session follows whatever the app's author publishes next. - **Get Allowed Components** Returns the catalog of template, field, and action types a Flow App step can use. - **Query Flow App State** Runs one of a Flow App's own registered read only queries against your state, without starting a session. There is no generic state endpoint, so only the queries the app author registered exist. ### Flow Sessions 5 - **Create Flow Session** Starts a session with a Flow App and returns its first step. - **List Flow Sessions** Returns your Flow App sessions. - **Get Flow Session** Returns a session's metadata, including its current step id and its state version. - **Get Flow Step** Returns a step's specification: its fields, their types, and any data references already resolved. It answers only for the session's current step, so any other step id looks like a deleted session. - **Submit Flow Step** Submits a step's values and advances the session. It requires an idempotency key so a retry cannot submit twice, and a state version that must match the session's current one, which is what stops a stale write from overwriting a newer state. ### Flow App Webhooks 4 - **Create Flow Subscription** Registers a webhook for one Flow App event type. The target URL must not resolve to a private or loopback address, so an internal endpoint cannot be used directly. - **List Flow Subscriptions** Returns a Flow App's webhook subscriptions. - **Delete Flow Subscription** Removes a Flow App webhook subscription. - **Replay Flow App Events** Returns the webhook events Overledger persisted for a Flow App, paged from the last event id you processed. The recovery path for missed deliveries, which is unusual enough to be worth building in from the start. ### Address and Contract Event Subscriptions 6 - **Subscribe To Address** Watches a blockchain address and posts to a callback whenever it takes part in a transaction. The network matters, because the same address exists on every EVM chain and a wrong network is accepted and silent. - **Unsubscribe From Address** Cancels an address subscription. - **List Address Events** Returns the events Overledger recorded for a watched address, from a point in time. The catch up path after an outage. - **Subscribe To Contract Event** Watches a specific contract event signature and posts to a callback when it fires. The parameter list is the signature, so one wrong type or indexed flag produces a subscription that is accepted and never fires. - **Unsubscribe From Contract Event** Cancels a contract event subscription. - **List Contract Event Occurrences** Returns the events Overledger recorded for a contract event subscription. ### Transaction Tracking 2 - **Track Transaction** Watches one transaction hash and posts to a callback when it confirms. One shot, with no cancel route, which is why it is an action rather than a trigger. - **Get Transaction Status** Returns a tracked transaction's current status. ## Triggers 3 triggers ### Event Triggers 3 - **On Address Activity** Fires when a watched blockchain address takes part in a transaction. Overledger watches the chain and posts the moment the address is involved, which beats polling a node. Pin the network, because the same address exists on every EVM chain and a wrong network produces a subscription that is accepted and stays quiet. - **On Contract Event** Fires when a specific smart contract event is emitted. The event parameter list is the signature, in declaration order, with the indexed flags matching the contract, because Overledger computes the topic hash from it. Putting a value on an indexed parameter filters at the chain level, which is far cheaper than filtering inside the flow. - **On Flow App Event** Fires when a Flow App emits an event. Each subscription takes a single event type, so watching several means several triggers, and the available types are whatever the app's author registered. Missed deliveries are recoverable with Replay Flow App Events, which is worth wiring in for any flow that matters. ## Frequently Asked Questions ### What can FlowRunner do with Quant Overledger? FlowRunner agents can run Get Health, Get Readiness, and Get My User ID in Quant Overledger, plus 66 more actions. ### Does connecting Quant Overledger to FlowRunner require OAuth? No. Quant Overledger connects to FlowRunner with an API key, no OAuth flow required. ### Can Quant Overledger trigger a FlowRunner workflow automatically? Yes. Quant Overledger supports 3 triggers that can start a FlowRunner workflow automatically. **Work at Quant Overledger?** This integration exposes Quant Overledger to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/overledger. Site index: https://flowrunner.ai/llms.txt