Appearance
What is Blazpay
Blazpay is a DeFi super-app. A user states an intent — in plain English, in a chat box, or through a conventional trading form — and the platform quotes it across every liquidity source it can reach, settles it on-chain through its own relayer contract, and never takes custody of the funds along the way.
That sentence hides three quite different systems, and most of this documentation exists to explain how they fit together:
- BlazAI turns natural language into a structured, parameterised intent.
- The trading core turns an intent into the best available route and a signed transaction.
- The ecosystem layer wraps retention mechanics — staking, quests, games, governance, creator payouts — around the trading core.
The shortest possible tour
A user's wallet signs exactly one transaction. Everything upstream of that signature — classification, quoting, route comparison, gas simulation, calldata assembly — happens off-chain in the backend, and everything downstream happens inside a single executeMetaTransactionSwap call on the BlazpayRelayer contract.
What makes it different from a DEX aggregator
Plenty of products aggregate quotes. The combination below is what Blazpay actually sells:
| Capability | Why it is unusual |
|---|---|
| AI that executes, not advises | BlazAI does not hand back instructions. It hands back a signable transaction card. See the agent. |
| Aggregating the aggregators | 26 providers are integrated in swap-sdk, 21 live. Blazpay quotes 1inch and LiFi and Odos and Relay in the same fan-out. See providers. |
| Non-custodial automation | Recurring buys (CSIP) and rule-based agents (Autopilot) run from vault contracts the user owns, executed by a platform bot that cannot redirect funds. |
| Safety tooling inside the trading surface | Contract audits, rug checks, wallet reputation and approval revocation are chat intents, not a separate product. See safety suite. |
| Emerging-market fiat rails | INR via UPI, plus 20+ currencies most global DEXs ignore. See buy/sell. |
| Early coverage of new chains | Berachain, Sei, Sonic, Hemi, Soneium, Unichain, HyperEVM, Abstract and others are live rather than "planned". See chains. |
| A retention economy, not just a tool | NFT staking, prediction markets, quests, a marketplace, a DAO and a creator payout program share the same backend. See rewards. |
The four repositories
Everything in this documentation maps onto four codebases, all siblings inside the defi-set working directory.
| Repo | Language / stack | Role |
|---|---|---|
bz-agent | TypeScript, LangChain + LangGraph | Intent classification and parameter extraction. No chain access, no execution. |
bz-backend | Node, Express, MongoDB, Redis | The platform monolith: quote fan-out, EIP-712 signing, provider proxies, automation crons, and the entire ecosystem layer. |
defi-dex | React 18, Vite, Tailwind | Two app shells from one repo — the trading app and the chat-only AI app. |
swap-sdk | TypeScript, ethers v6 | The aggregation engine. One class per provider, plus the relayer meta-transaction builder. Consumed by both the backend and the frontend. |
A fifth surface, contract-deployment inside bz-backend, holds the Solidity for the relayer, the DCA vault, the Autopilot vault and the ecosystem NFT contracts. See contracts.
Reading order
If you are new, read in this order:
- The three pillars — the product-level shape of the platform.
- Ecosystem map — every module, and which repo owns it.
- Domains & surfaces — which product lives at which hostname, and why the AI split happened.
- Custody & trust model — what the platform can and cannot do with user funds. Read this before touching automation code.
- System overview — then dive into whichever core you are working on.
Verify usage figures before publishing them
Numbers like "136,000+ AI messages" or "1,417 unique wallets" in these pages are point-in-time analytics snapshots, and the source of each is noted where it appears. Re-query before putting one in a press release or a landing page.
Provider and chain counts drift
swap-sdk registers providers in its TradeManager constructor and comments out any whose upstream API is down. The live count therefore changes without a code review. swap-sdk/src/index.ts is the only authority; the provider table records the state at the time of writing.