Biconomy

• Name: Biconomy
• URL: https://www.biconomy.io/
• Category: smart account infrastructure / onchain orchestration / cross-chain execution
• Tags: ethereum-ecosystem
• Summary: Biconomy is an account-abstraction and execution stack whose real story is routed multichain orchestration, not just old gasless-UX marketing. Nexus, MEE, the Supertransaction API, and Smart Sessions make it worth tracking as a serious execution layer. Still, this is not base account substrate; it is a control plane wrapped around it.
• What it does:
  • Provides Nexus, an ERC-7579 smart account product with gas sponsorship, ERC-20 gas payments, batching, recovery/session-key-style modules, and unified deployment across EVM networks
  • Exposes orchestration infrastructure through the Modular Execution Environment (MEE), letting developers compose multi-step and cross-chain workflows with a single user signature
  • Ships both a REST-based Supertransaction API and a TypeScript AbstractJS SDK for swaps, bridges, DeFi deposits, conditional execution, and other orchestrated flows
  • Offers Smart Sessions for delegated permissions and automation, including agent-style execution with contract/function/token constraints across multiple chains
  • Maintains public contract repositories and audit artifacts around Nexus, plus docs indexes (llms.txt) and developer-facing operational references
• Key claims:
  • Official docs describe Biconomy as “the full-stack infrastructure for building seamless Web3 experiences across chains” and say the platform supports single-signature multichain workflows, gas abstraction, and delegated automation
  • Biconomy’s docs say MEE handles sequencing, runtime parameter injection, bridge timing, gas management, and failure recovery across 20+ EVM chains, positioning it as more than a basic ERC-4337 stack
  • Smart Sessions docs explicitly frame the product for automation and agentic execution, including multichain permissions and support for both smart accounts and EOAs via EIP-7702 / Fusion-style flows
  • Nexus materials claim ERC-7579 modularity, EIP-7702 compatibility, lower gas costs than alternatives, and public security/audit coverage through the Nexus repository
  • Public GitHub materials and docs show Biconomy exposing production-oriented APIs, explorers, supported-chain references, and DeFi integration surfaces rather than only wallet SDK abstractions
• Whitepaper: No classic whitepaper or litepaper was found during this pass. The strongest primary materials were the official docs, llms.txt docs index, Smart Sessions docs, Nexus overview/repository, and public GitHub organization; see ../whitepapers/biconomy-primary-sources-2026-04-25.md.
• Sources:
  • https://www.biconomy.io/
  • https://docs.biconomy.io/
  • https://docs.biconomy.io/llms.txt
  • https://docs.biconomy.io/new/smart-sessions/introduction
  • https://docs.biconomy.io/new/learn-about-biconomy/nexus
  • https://github.com/bcnmy
  • https://github.com/bcnmy/nexus

Internal linkages

• Company / operator boundary for API keys, dashboard access, hosted MEE execution, explorer truth, and account-mode packaging: biconomy.
• Best peers and anchors: pimlico, alchemy, and safe.

Protocol / company boundary

• Keep this note on the product and mechanism surface: Nexus accounts, modules, Smart Sessions, MEE orchestration behavior, and the concrete developer-facing execution patterns.
• Use biconomy when the sharper question is who runs the quote and execution endpoints, chooses supported-chain and account-mode exposure, and sits inside the hosted retry / routing / status-publishing path around that product stack.
• That split matters because what can Biconomy orchestrate? and who controls the hosted traffic and policy shell around it? are related but not identical questions.

Control surface

• The onchain piece is legible enough: Nexus accounts, modules, delegated permissions, and executed user operations land onchain.

• The leverage sits in the surrounding service layer: routing defaults, bridge choice, relayer selection, retry logic, sponsorship policy, and which chains or modules get first-class support.

• Read it as a routed execution layer around the account substrate, not as the substrate itself.

• For the named operator boundary around API keys, dashboard authority, hosted execution, and status truth, read biconomy.

• Last reviewed: 2026-08-10 UTC