Mode Data: Index DeFi, Agents, and Onchain Activity

Index Mode's contract events, token transfers, and decoded transactions in one pipeline, delivered to your own database. Real-time and complete historical data, no node to run.

Mode bills itself as the modular DeFi L2 built to dominate DeFi with AI-powered apps and agents, an Ethereum Layer 2 on the OP Stack. Its push is DeFAI: verifiable AI trading agents, a native perpetuals DEX built with Orderly, and restaking and yield apps. You can read how the team frames it at mode.network.

That mix is the data problem. Mode is an EVM chain where DeFi protocols, AI agents, and a long tail of yield apps emit contract events, token transfers, and decoded calls block after block. Indexing Co covers Mode in a single pipeline, decodes the raw chain into the shape you want, and delivers it to your own PostgreSQL, warehouse, or webhook. Real-time and full history, with no node to operate.

Source Mode L2 blocks

Ingest blocks, logs, traces

Decode ABIs to events

Transform your JavaScript

Deliver your database

Why Mode data is hard

DeFi and Agent Activity Mode leans into DeFAI: perpetuals trading, AI quant tooling, restaking and yield vaults, and onchain agents that fire transactions on their own schedule. Tracking who traded, what an agent executed, and how a vault position moved means stitching together many event types in real time, not just reading balances.

OP Stack Specifics Mode is an OP Stack rollup that batches transactions and posts data back to Ethereum L1. Sequencer ordering, L1-to-L2 deposits, and the deposit and withdrawal lifecycle all add structure a naive EVM scraper misses. You want history that reflects how the rollup actually settles.

Decoding Across Many Protocols A real Mode dataset spans dozens of contracts at once: the native perps DEX, lending and restaking markets, and AI agent vaults. Each needs its own ABI and event handling, and proxy upgrades make the right ABI a moving target as protocols ship new versions.

Your Own DB, Not a Hosted API Generic RPC endpoints and hosted query APIs leave you rate-limited and renting someone else's schema. Powering an app or analytics workload on Mode means owning the data in your own store, shaped the way your product queries it, from agent dashboards to yield analytics.

What Indexing Co delivers for Mode

The DIY Path

Stand up and maintain the whole stack yourself.

Run a Mode archive node or wire up a third-party RPC.
Fetch and decode logs, traces, and receipts against the right ABIs.
Track proxy upgrades and per-protocol event schemas by hand.
Build backfill, reorg handling, and real-time delivery from scratch.

Indexing Co

One pipeline sources, decodes, and delivers Mode to your store.

Mode contract events, token transfers, and decoded txs in a single pipeline.
Decoded data, shaped by your JavaScript transform.
Lands in your PostgreSQL, BigQuery, warehouse, or webhook.
Real-time delivery plus complete backfilled history. No node, no RPC babysitting.

What you can index

EVM data type	On Mode, for example
Contract events and logs	Perps DEX trades, lending borrows, vault deposits
Token transfers (ERC-20, ERC-721)	MODE and stablecoin transfers, ETH gas movements
Decoded transactions and traces	AI agent executions and smart-account user operations
Protocol and account state	Restaking vault balances, MODE staking positions

A transform, not a subgraph

You write the transform in JavaScript, not AssemblyScript, and change it without re-indexing from block zero. Indexing Co runs your function over each block server-side: decode the logs you care about and return rows for your destination.

// Indexing Co transform: reshape each block into rows for your database
function transform(block) {
  const results = [];
  const signatures = [
    'event Transfer(address indexed from, address indexed to, uint256 value)'
  ];

  for (const tx of block.transactions || []) {
    for (const log of tx.receipt?.logs || []) {
      const event = utils.evmDecodeLogWithMetadata(log, signatures);
      if (!event) continue;
      results.push({
        chain: block._network,
        block: Number(block.number),
        tx_hash: tx.hash,
        contract_address: log.address?.toLowerCase(),
        from: event.decoded.from,
        to: event.decoded.to,
        value: event.decoded.value,
      });
    }
  }
  return results;
}

Mode with Indexing Co

Run it yourself if

You want full control of node infrastructure and have the team to operate a Mode archive node, decode every protocol's ABIs, and build backfill and reorg handling in-house.

Use Indexing Co if

You want Mode contract events, token transfers, and decoded transactions delivered to your own database, with real-time plus complete history and no infrastructure to run.

Get a Demo Open the Console

FAQ

Do I need to run a Mode node?

No. Indexing Co sources Mode blocks, logs, and traces for you, including full historical data, so you never operate an archive node or babysit an RPC endpoint.

Can I index any protocol on Mode?

Yes. Point a pipeline at any Mode contract or set of contracts, from the perps DEX and restaking vaults to AI agent contracts or your own deployments, and we decode the events against the right ABI.

Can I track Mode's AI agents and DeFi activity together?

Yes. Because the pipeline decodes any contract you target, you can capture agent executions, trades, and vault movements side by side and join them in your own schema.

Does Indexing Co handle Mode reorgs and proxy upgrades?

Yes. The pipeline accounts for chain reorganizations and tracks proxy implementation changes so your decoded data stays correct as contracts upgrade.

Can I get complete historical Mode data?

Yes. We backfill from your chosen start block and merge it with real-time data, so your Mode dataset is gap-free from genesis forward if you want it.

Get Started

Index Mode in minutes. Set up your first Mode contract or token pipeline without running a node.