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

Pick one way to sign in. Each has its own balance and its own way to pay.

  • A Google account and a card. No wallet needed. Your first 10 analyses are free. After that, buy credit by card: any amount from $10. $10 buys $10 of credit.
  • A browser wallet and USDC. A wallet (MetaMask, Rabby, or anything EIP-1193 compatible) - only to sign a one-time sign-in message. It never needs to hold funds itself. You fund your balance with 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.

The two are separate accounts: a Google account pays by card, a wallet account pays with USDC.

Sign in with Google and pay by card

  1. Open oculr.xyz/app, click Sign up (or Log in if you already have an account), and choose Continue with Google. Your first 10 analyses are free, whatever they cost: paste a hash and run, no balance needed. The balance chip counts them down, and they show as Free in My reports.
  2. Open the balance menu (top right) and choose Top up.
  3. Pick $10, $25, or $50, or type any other amount of $10 or more (for example $12.99). You pay on Stripe's secure checkout page - oculr never sees your card details - and come straight back to the app.
  4. Your balance updates as soon as you return. Stripe emails you a receipt.

$10 comfortably covers several analyses; routine analyses run about $1, while incident and exploit investigations usually run $1.50 to $2.50. See Pricing for the measured distribution. Nothing is spent until you run an analysis. There is a daily top-up limit per account as an anti-abuse safeguard.

Free analyses are limited to a daily total across all users. If today's are used up, the app says they are paused: your remaining ones keep until tomorrow, and a topped-up balance runs as normal in the meantime. A stopped analysis still counts as one of the ten.

Refunds. Unused credit can be refunded to your card on request: email rob@oculr.xyz. Card-funded credit can't be withdrawn as USDC.

Sign in with a wallet and deposit USDC

  1. Open oculr.xyz/app, click Sign up (or Log in if you already have an account), and pick your wallet in the dialog.
  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 about $1, while incident and exploit investigations usually run $1.50 to $2.50. 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.

My reports

Open the balance menu (click your address or email in the top right) and choose My reports to see the analyses you've run while signed in, and those paid with one of your API keys (labelled via key), newest first: the date, the transaction hash, the first line of the summary, and what the run cost. Open one to see the finished report exactly as it was, at no charge. Reports tied to your account are kept indefinitely.

A run that stopped because your balance ran out is listed as Unpaid: its report is finished but locked. Open it to see what is still owed and choose Unlock from balance to pay that remainder from your prepaid balance and see the report. You pay the run's price once; if the balance cannot cover the remainder, top up and try again.

An async run started with an API key is different: when the balance runs out mid-run, the key still receives the result, so the report is not locked. It is listed at what it collected, and the rest of its price is not owed.

API keys

With a Google sign-in, the balance menu also has API keys once they are enabled for your account. A key lets a script or pipeline spend this account's balance with no wallet and no browser, and keeps working after you sign out until you revoke it. See Use an API key.

Alert channels

The balance menu also has Alert channels, for either sign-in. A channel is an HTTPS endpoint (a Slack or Discord webhook, PagerDuty, or a service of your own) or a set of email addresses that receives every report your account produces as soon as it finishes. An HTTP channel takes your own headers and, if you want, your own JSON body layout; header values are stored encrypted and never shown again. An email recipient other than yourself confirms by link before anything is sent. Add one, press Send test to check it, and from then on every analysis you run, in the app or through an API key, is delivered to it. See Send reports to Slack, email, a webhook, or your own service.

Withdrawing your balance

Withdrawals apply to wallet accounts. Google accounts have no Withdraw option: unused card credit is refunded to your card on request instead.

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 signed in (with Google, or by connecting a wallet and signing the message) and your balance is at least $2. A Google account with a free analysis left needs no balance. The lock message tells you what is missing.

"Free analyses are paused for today" - today's free analyses are used up across all users. The ones you have left are still yours tomorrow; top up to run now.

Balance shows $0 or negative mid-analysis - the analysis keeps running to completion; open Top up and add more (by card for a Google account, USDC for a wallet account) 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.

I paid by card but my balance hasn't changed - it updates when you return from Stripe's page. If you closed the tab before returning, the payment still credits within a few moments: reload the app. Your Stripe receipt email confirms the payment went through.

"Payment processing. Your balance updates shortly." - Stripe sent you back before it finished confirming the payment. The app checks again for about 20 seconds. If the notice is still showing after that and your balance has not changed, reload the app a minute later. You are never charged twice for one checkout.

"That would go over today's top-up limit" - card top-ups have a daily limit per account. Try a smaller amount, or try again tomorrow.

"Please sign out and sign in again, then top up" - your sign-in needs refreshing before a card payment. Open the balance menu, choose Sign out, sign in with Google again, and retry. Nothing was charged.

"This account is on hold" - a card payment on this account was disputed with your bank, so new analyses and top-ups are paused. Email rob@oculr.xyz to resolve it.

"Continue with Google" does nothing - allow pop-ups and third-party sign-in for oculr.xyz in your browser, then try again. Make sure you are on https://www.oculr.xyz.

Related