Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Use the web app

Paste a hash at oculr.xyz/app, watch the analysis stream live, and read the result in five views - no code, no per-request wallet signature.

The web app is the fastest way to triage a single transaction: one-off incident checks, eyeballing something suspicious, or walking a teammate through what a transaction did. For automation, use the API or agent integration instead - same JSON contract, same pricing.

What you need

  • A browser wallet (MetaMask, Rabby, or anything EIP-1193 compatible) - only to sign a one-time sign-in message. It never needs to hold funds itself.
  • USDC on Tempo, sent from any wallet or exchange to your personal deposit address (shown after you sign in). Your connected wallet doesn't have to be the source of funds.

Connect, sign in, and top up

  1. Open oculr.xyz/app and click Connect wallet.
  2. Click Sign in. Your wallet prompts for a signature (SIWE, EIP-4361) - no transaction, no gas, no network switch required. This sets a session cookie; oculr now recognises you.
  3. Open the balance menu (click your address in the top right) and choose Top up. A dialog shows your personal deposit address as text and a QR code.
  4. Send USDC on Tempo to that address from any wallet or exchange - it doesn't have to be the wallet you signed in with. Deposits from an exchange withdrawal work fine.
  5. Click I've sent it to trigger an immediate balance check. Your balance updates as soon as the transfer has one confirmation; if the immediate check misses it, a background scan credits it within a few minutes regardless - you don't need to keep the dialog open.

How much to send - these are web-app prepaid ledger figures, a different rail from the API's MPP payment channel, which has its own $2 admission floor and $16 suggested deposit (see The channel deposit). There's no fixed minimum, but the gate needs at least $2 free balance to start an analysis - and $2 is a floor to begin a run, not a working balance. Routine analyses run roughly $1 to $2, while incident and exploit investigations usually run around $3-4. The recommended deposit is $6 - it comfortably covers a full analysis, and topping up again later is a single transfer. Nothing is spent until you run an analysis, and unspent balance stays yours. See Pricing for the measured distribution.

Run an analysis

Paste a transaction hash from any of the 50+ supported EVM mainnets - the chain is auto-detected, no dropdown to pick. The analysis streams in real time, and the app switches to the Summary tab when it completes. Typical runs take 1-2 minutes; complex transactions take longer.

Pricing is metered, same as the API: you pay for the actual cost of analysing your transaction, deducted from your balance as the analysis runs. Once a run starts it always completes - your balance can dip slightly negative to cover it; top up before your next run if that happens.

The five views

TabWhat it showsWhen to use it
WorkflowThe live stream: pre-flight progress, the agent's reasoning as it thinks, and every tool call with its durationWatching the analysis run; understanding how oculr reached its conclusion
SummaryThe human-readable result - what happened, who did it, risks, protocol, USD value, confidenceThe answer, for humans
TraceThe decoded call tree with resolved function signatures and address labelsDigging into a specific call frame yourself
FlowA rendered diagram of the transaction - who called what, where assets movedExplaining the transaction to someone else; screenshots for write-ups
JSONThe raw ExplanationResult, exactly as the API returns itCopying structured data into a report or tool

The Workflow tab is worth watching at least once: each tool call you see is the agent buying a resource under the hood - a trace, a label lookup, a price - and it makes the metered cost of the run concrete.

Reading the result

The same rules apply as in the API:

  • Check confidence first (shown in the Summary). high means protocol and actors identified; low means sparse data - treat the summary as a lead, not a verdict. See Confidence levels.
  • A partial result is not an error. If an upstream source had a transient issue you still get a result, flagged as partial with the reason. Re-running after a moment usually completes it.

Withdrawing your balance

Open the balance menu and choose Withdraw. Enter an amount up to your free balance.

  • Withdrawals go only to the wallet you're signed in with - there's no separate destination field.
  • Every withdrawal sits in a 24-hour security window before it pays out. You can cancel a pending withdrawal at any time before it executes; the balance menu shows a live countdown.
  • Daily withdrawal caps apply as an anti-abuse safeguard. If you hit one, wait for the next day's window or contact support.

Troubleshooting

Connect succeeds but "Sign in" fails - your wallet rejected or cancelled the signature request. Click Sign in again; no transaction is sent so there's no cost to retrying.

Analysis won't start / input is locked - the app locks the transaction input until you've connected, signed in, and your balance is at least $2. The lock message tells you which of the three is missing.

Balance shows $0 or negative mid-analysis - the analysis keeps running to completion; open Top up and send more USDC before starting your next one.

"I've sent it" doesn't show a credit right away - the deposit needs one on-chain confirmation. If the immediate check comes back empty, a background scan still picks it up within a few minutes - no action needed.

Related