MULTI-CHAIN ASSET INTELLIGENCE

See every asset, position, and risk across chains

Turn public addresses, token balances, DeFi positions, evidence, and continuous monitoring into one trustworthy multi-chain workflow.

Open asset scanner

One workbench for the complete asset workflow

  • Multi-chain asset scanning
  • Portfolio snapshots and XLSX export
  • Batch balance queries
  • DeFi lending and liquidity positions
  • Fund activity monitoring
  • Risk and data evidence

Support comes from the current runtime configuration

AInfos keeps catalog networks, runtime-enabled networks, protocol deployments, partial coverage, and unconfigured states distinct.

Built for individuals and evidence-driven teams

  • Personal wallet analysis
  • Team treasury monitoring
  • Batch operations and reports

Asset data should show where it came from

Every scan preserves Block or Slot, observed time, provider, explorer links, and pricing coverage. Failed reads never become zero assets.

Frequently asked questions

What onchain assets can AInfos query?

AInfos can query native assets, tokens, NFTs, and runtime-ready lending, LP, CLMM, and farm positions on enabled networks. Actual coverage remains explicit in each result.

What can an individual user do with AInfos?

Combine public wallets, DeFi positions, unpriced assets, and risk evidence in one view, then continue into monitoring or reporting when needed.

How can a team manage multiple public addresses?

Teams can create multi-address snapshots, compare chain subtotals and fund changes, review tasks and notifications, and export XLSX reports.

How are batch balances different from an asset scan?

An asset scan provides complete context for one address. Batch balances process many addresses and selected assets through filters, pages, and durable tasks.

How is network support counted?

Only networks currently returned as enabled by the public capability endpoint count as queryable. Unpublished catalog entries remain separate.

Why are some assets unpriced?

Onchain balance and pricing coverage are separate. AInfos preserves the raw balance and marks it unpriced instead of inventing fiat value.

Does a failed read become zero assets?

No. Failed, partial, unconfigured, and true zero-balance states remain distinct, with scope and recovery context where available.

How can I assess freshness and provenance?

Results preserve Block or Slot, observed time, provider/RPC provenance, and explorer links where available for independent checking.

Do public-address queries require a wallet connection?

No. They read public onchain data without requesting private keys, seed phrases, signatures, or token approvals.

Can AInfos submit transactions for me?

No. The asset query, reporting, and monitoring flows described here are read-only and do not construct, sign, or broadcast transactions.

What information does a public address expose?

A public address and its onchain activity are already publicly queryable. Never enter a private key, seed phrase, or other sensitive credential.

What happens when a provider is not configured?

The affected network is marked unconfigured or unavailable instead of returning fabricated results; support is never represented as a false zero.

How do teams maintain one data definition?

Snapshots, task history, status labels, and exports share the same provenance and coverage model, reducing spreadsheet and screenshot drift.

Can monitoring notifications replace reconciliation?

No. Notifications surface changes for review; decisions should still use a fresh scan, its evidence, and the relevant explorer.

Does a subscription change data truthfulness?

No. Plans only affect explicitly stated entitlements. Source, failure, partial, and unpriced states are never rewritten by tier.

When should I use snapshots or XLSX exports?

Use them for recurring multi-address reviews, team reconciliation, archival records, or downstream analysis.