Biconomy
- Features
- Ease of use
- Ease of management
- Quality of support
- Affordability
- Market presence
What is Biconomy
Account abstraction tooling
Developer APIs and SDKs
Cross-chain execution support
Infrastructure dependency risk
Chain and feature coverage varies
Complex security and compliance
Plan & Pricing
Pricing model: Pay-as-you-go How fees are calculated (official): Biconomy returns dynamic per-transaction quotes via its API (Supertransaction / MEE quote endpoints). Each quote includes a fee breakdown (gas, relayer, relayerService, app) and amounts are denominated in tokens (e.g., USDC/USDT/other ERC‑20) or can be sponsored by the integrator. The official docs show example quote endpoints and response fields but do not publish fixed subscription tiers or public per-unit prices.
Official doc-derived details & notes:
- Quote endpoints: POST /v1/mee/quote (Supertransaction API) — returns fee object with fee.amount and nested quote.fee fields (example response in docs).
- Fee components shown in docs: fees.gas, fees.relayer, fees.relayerService, fees.app (fee breakdown returned by quote responses).
- App-configurable fees: docs show an appFees parameter that allows apps to set an app fee (example value '30' as 0.3% in integration examples).
- Gas payment: docs state users can pay fees in many ERC-20 tokens (USDC/USDT etc.) or the app can sponsor gas via Biconomy’s sponsorship features (one gas tank across chains).
- Bridge/transfer products (e.g., Hyphen) are described as charging dynamic transfer fees (doc text explicitly describes a “dynamic transfer fee” and that transfer fees + transaction fees are deducted in token units).
Summary: No public, fixed pricing table or subscription tiers were found on Biconomy’s official documentation or website; pricing is usage-based and quoted per-request via the API.
Notes on availability of vendor-published numbers: Official docs provide fee structure and API mechanics but do not list a public rate card, fixed per-transaction rates, or a public free plan/trial on the documentation pages examined.