Now supporting EIP-7702

Write intent once. Run across EOA → 7702 → UserOps.

AbstractApex compiles actions into the optimal execution format per user, wallet, and chain—then upgrades users automatically when policies require it.

intent.json
7702 Batch Tx
ERC-4337 UserOp
7579 + Hooks
1 API: execute()

Wallet UX depends on
chain + wallet quirks.

Fragmented Logic

Teams rewrite execution logic for EOAs vs UserOps repeatedly, creating tech debt.

Migration friction

Migrating users is hard, so products delay AA adoption and lose UX benefits.

Bespoke Glue Code

Compliance, AI agents, and gas abstraction require custom brittle integration per chain.

legacy_handler.ts

if (wallet.type === 'EOA') {

if (chain.id === 1) { // mainnet gas logic ... }

else if (chain.supports7702) { ... }

else { fallback() }

}

else if (wallet.isSmartAccount) {

if (entrypoint === 'v0.6') { ... }

if (module.isInstalled) { ... }

}

Graph Resolved

1. Define Action Intent

Describe what needs to happen, not how. AbstractApex parses the intent into a declarative schema.

2. Negotiate Capabilities

The engine checks the wallet's current state. Is it an EOA? Does it support batching? Are modules installed?

3. Execute & Upgrade

Transactions are constructed in the most advanced format available. If policies require it, the account is upgraded JIT.

The Unified Action Graph

One snippet to rule them all.

Input: Intent

const intent = await apex.create({
  actions: [
    { to: usdc, data: approve },
    { to: vault, data: deposit }
  ],
  policy: {
    gasSponsorship: true,
    spendingLimit: "100 USDC"
  }
});

Compiled Output

// Fallback: Standard EOA execution return { type: "eip-1559", // Must execute individually :( batch: false, steps: [ { to: usdc, data: approve }, { to: vault, data: deposit } ] };

The Upgrade Lifecycle

Most users start as EOAs. AbstractApex upgrades them silently as their needs grow, preserving the address while unlocking capabilities.

Explore the architecture
0

Tier 0: EIP-7702 Superpowers

Temporarily upgrade an EOA to a smart contract for a single transaction. Batch actions and sponsor gas without permanent migration.

CAPABILITY_BATCH_CALL
1

Tier 1: UserOps Foundation

Permanent deployment of an ERC-4337 account. Enables session keys, social recovery, and non-blocking interactions.

CAPABILITY_PAYMASTER
2

Tier 2: Modules + Registry

Install specific plugins from the registry. Spend limits, recurring payments, and DeFi automations.

CAPABILITY_MODULE_INSTALL
3

Tier 3: Attested Services

Enterprise-grade compliance. Attested execution, policy-based AI spending, and unified gas vaults.

CAPABILITY_POLICY_ROOT

Why AbstractApex Wins

Capabilities AbstractApex Traditional AA SDKs WalletConnect/Wagmi
Start from EOA without migration
Vendor-agnostic (Safe / Kernel / Biconomy)
Bundler Failover Routing
Compliance via Signed Attestations

Consumer Onboarding

Sponsor and batch transactions for EOAs immediately using EIP-7702 without forcing a contract deployment.

DeFi Power Users

Enable passkeys, social recovery, and session keys for high-frequency traders.

Agentic UX

Policy-based spending for AI agents using Lit Protocol and Programmable Key Pairs.

Built for builders.

  • Works natively with viem
  • ERC-4337 v0.6/v0.7 routing
  • Bring your own bundler/paymaster
  • Preview simulation before execute
Open Documentation View Reference Integrations
➜ ~ npm install @abstractapex/sdk
added 1 package in 0.4s
➜ ~

Graceful Degradation

Capability probing ensures the transaction always executes, even if advanced features are unavailable.

Health Checks

Real-time bundler monitoring with automated failover routing across 3+ providers.

Replay Protection

Attestation verification with expiry and nonce tracking to prevent signature reuse.

Sovereign Escape

Timelock escape hatches ensure users can always force-exit their assets directly on-chain.

Onboard with EIP-7702 today.
Upgrade when it matters.

AbstractApex compiles intents into the best execution format for the user’s current capabilities.