Quick start

From zero to a live alert in under five minutes. The free tier is enough to follow this guide end to end — no credit card required.

1. Create an account

Sign up at imaa.w3i.io/signup. The free tier includes 5 contracts, 100 alerts per month, email notifications, and a 15-minute polling interval. Upgrade later from the billing page when you need shorter polling, more channels, or API access.

2. Add a notification channel

Go to imaa.w3i.io/settings/notifications and add at least one channel. On the free tier, that means an email channel — drop in the address you want alerts sent to and confirm. Starter adds Slack; Pro and above add SMS, signed webhooks, Discord, and PagerDuty. See Notification channels for the full list.

3. Add a contract

Head to imaa.w3i.io/contracts/new, pick a chain (the picker lists every enabled chain — Ethereum, Base, Arbitrum, Polygon, Optimism and more, plus Solana) and paste the contract or program address. On EVM chains IMAA fetches the ABI automatically — first from Sourcify, then from Etherscan V2. The contract moves from pending to monitoring as soon as it has at least one monitor target — not when the ABI arrives. An ABI simply unlocks event- and function-level targets; generic targets like transaction rate work without one.

During onboarding you can pick which events you want to track. Each selected event becomes a candidate monitor target.

4. Add an alert rule

Open imaa.w3i.io/alerts/new, choose the monitor target created in the previous step, then define:

  • An operator (gt, gte, lt, lte, eq, neq)
  • A numeric threshold
  • A window in seconds (e.g. 60 for one minute)
  • A severity (info, warning, or critical)
  • The channel to notify

A reasonable starter rule: alert me when more than 5 Transfer events show up in a single poll, then stay quiet for 60 seconds. See Alert rules for the full semantics (including exactly what the window does).

5. Wait for an event

IMAA polls the chain on your tier's schedule (15 minutes on free, down to 30 seconds on Team). When a rule trips, an alert event is recorded and the channel fires. Review the history any time at imaa.w3i.io/alerts.

That's the loop. From here, scale up by adding more contracts, more targets, and more rules — or jump to the public API to manage everything as code.