Biconomy primary-source snapshot
Fetched: 2026-04-25 UTC
1) Official docs introduction
Source: https://docs.biconomy.io/
Selected excerpts from the docs:
Biconomy provides the infrastructure to build Web3 applications with Web2-level user experience. Execute complex multi-chain workflows with a single signature, abstract away gas entirely, and enable automation through delegated permissions.
Biconomy offers two ways to integrate, depending on your needs: Supertransaction API … [and] AbstractJS SDK.
Smart Sessions enable delegated execution—perfect for AI agents, bots, and automated strategies.
Additional signals from the docs:
- The docs present Biconomy as a broader execution/orchestration layer, not merely a “gasless transaction” helper
- The official introduction tightly bundles account abstraction, cross-chain orchestration, and automation into one product story
2) llms.txt documentation index
Source: https://docs.biconomy.io/llms.txt
Selected excerpts from the docs index:
Biconomy is the onchain orchestration layer for multi-chain applications. Compose multi-step, cross-chain blockchain workflows — swaps, bridges, DeFi deposits, custom contract calls — into a single user signature.
Powered by the Modular Execution Environment (MEE), which handles sequencing, runtime parameter injection, bridge timing, gas abstraction, and failure recovery across 20+ EVM chains.
Additional signals from the docs index:
- The docs index is unusually rich and agent-friendly, exposing canonical pages, API patterns, explorer URLs, decision rules, and error-handling guidance
- This makes the docs index itself a meaningful primary artifact for understanding the platform’s operating model
3) Smart Sessions docs
Source: https://docs.biconomy.io/new/smart-sessions/introduction
Selected excerpts from the docs:
Smart Sessions are a powerful feature of the Biconomy stack which allows accounts (EOAs and Smart Accounts) to delegate certain permissions to other signers.
Smart Sessions are extremely useful for automation and agentic execution.
Unlike ERC-4337 account providers, the Biconomy Smart Session stack has been built from the ground up to be multichain first!
Additional signals from the docs:
- The permissions model is described concretely in terms of spend limits, contract allowlists, token restrictions, and multi-chain scope
- Biconomy is explicit that it wants to support EOAs as well as smart accounts via EIP-7702 / Fusion-related flows
4) Nexus overview docs
Source: https://docs.biconomy.io/new/learn-about-biconomy/nexus
Selected excerpts from the docs:
Nexus is Biconomy’s ERC-7579 compliant smart account—the most gas-efficient on the market with 25% lower costs than alternatives.
Nexus is the only smart account solution on the market enabling composable batch execution.
EIP-7702 compatibility ensures forward compatibility with Ethereum’s account abstraction roadmap.
Additional signals from the docs:
- Nexus is positioned as the account layer inside a broader orchestration stack, not as the entire company story
- The docs emphasize modularity, batching, gas efficiency, third-party modules, and compatibility with future Ethereum AA direction
5) Public GitHub organization
Source: https://github.com/bcnmy
Selected excerpts/signals from the public org page:
Biconomy is the smart wallet and execution engine for high-performance DeFi and autonomous onchain agents.
70M+ transactions processed
4.7M+ smart accounts
Additional signals from the org page:
- The org summary reinforces Biconomy’s newer positioning around execution, multichain workflows, and autonomous-agent use cases
- Public GitHub presence suggests the company is shipping SDKs and contracts in the open rather than presenting only closed enterprise surfaces
6) Nexus repository
Source: https://github.com/bcnmy/nexus
Selected excerpts/signals from the repository page:
Nexus - ERC-7579 Modular Smart Account Base
Nexus contracts are pre-deployed on most EVM chains.
Additional signals from the repository page:
- The repo exposes multiple audit reports (CodeHawks/Cyfrin, Spearbit, Zenith, Pashov), which is useful primary-source evidence for maturity and security posture
- Public deployment scripts, testing commands, and audit artifacts suggest Nexus is intended as serious production infrastructure rather than only a managed SaaS abstraction
Notes
- This pass did not locate a classic whitepaper or litepaper from official Biconomy sources.
- The strongest primary materials were the docs introduction,
llms.txtdocs index, Smart Sessions docs, Nexus overview, GitHub organization, and Nexus repository. - Biconomy appears best categorized as smart account infrastructure / onchain orchestration / cross-chain execution with a strong automation and delegated-permissions angle.