Skip to main content

Apps Overview

Apps are mini-dashboards and tools you describe in plain English — Bankr writes the manifest, the scripts, and the UI for you, then drops it into your terminal. No project scaffolding, no build pipeline, no hosting to set up. You talk, Bankr ships.

Build an app by asking​

Open the chat and tell Bankr what you want. The more specific you are about the data, layout, and refresh cadence, the closer the first build lands to what you imagined.

build me a polymarket alpha terminal — show curated picks bankr's
reasoning, trending markets, ending-soon markets, and my open
positions. refresh every 15 minutes. share it as a public link i
can post on twitter.

Bankr designs the data model, writes the backend scripts, drafts the HTML with charts and tables, picks a refresh schedule, and installs the app under your wallet. When it's done, the app shows up in your Apps sidebar — click it and the dashboard renders inside the terminal panel.

You can also ask for tools that aren't dashboards: a calculator, a step-by-step trade builder, a watchlist with a paste-in field, a portfolio snapshot. If the agent has the right permissions and the data is reachable, it can probably build it.

Refine by chatting​

Every installed app keeps the chat open right next to it. To change something, just say what you want changed.

add a column for entry price between symbol and size

change the schedule to every 5 minutes

split the curated section into two panels — long and short

show 24h volume next to each market

stop showing my solana positions, only base

Bankr edits the app in place. It only touches the parts you asked about — your existing layout, naming, and color choices stay. If something breaks, say so ("the trending panel is empty after the last edit") and Bankr will read its own scripts, find the issue, and patch it.

You don't need to think about which file to edit. The agent owns the manifest, the scripts, the HTML, and the schedule, and figures out the smallest change that satisfies your request.

Running scripts on demand​

Each app's backend logic lives in scripts — small functions that run on a server-side runtime when invoked. Most are wired up to a schedule that fires automatically (every 15 minutes, every hour, daily, whatever you ask for); some are triggered from buttons in the app's UI; some are run on demand.

If you own the app, the panel header has a Scripts button that opens a drawer listing every script. Each row has:

  • The script name and its schedule (or on-demand for unscheduled scripts).
  • An Open button that jumps you into the file editor with the script's source loaded.
  • A Run button that fires the script immediately, as if its schedule had just ticked. The result (or error) renders inline.

Useful for testing edits, refreshing data immediately instead of waiting for the next scheduled run, or seeing exactly what a script returns.

Apps can call paid HTTP endpoints from the iframe using the x402 payment protocol. When a button needs to spend money — an AI image generator, a premium per-query data lookup, a gated upstream feed — the app calls bankr.x402.fetch(url, options). The host pops a confirmation dialog showing the URL and the maximum USD, the visitor's wallet settles USDC on Base, and the upstream response renders. Each call goes through its own confirm; nothing settles silently.

build me an image generator app where each render charges the visitor
$0.10 to call x402.bankr.bot/0xowner/image-gen

The agent adds the pay:x402 permission, pins the endpoint hostname in an allowedHosts allowlist, and writes the iframe code. Per-(visitor, app) rate limits cap abuse: 10 calls/minute, $10/day.

If you want to publish a paid endpoint that other apps and agents can consume — not just consume one — see x402 Cloud. For the wire-level details on consuming x402 from inside an app see Permissions and the SDK reference.

Sharing & forking​

Apps default to private. To share one:

make this app public
make this app unlisted, give me the share link
  • Unlisted apps are accessible to anyone with the URL.
  • Public apps are listed in Bankr's app directory and discoverable by anyone.

Anyone visiting your shared dashboard sees the same data you see — by default, scripts run as the owner so visitors get a consistent view. If a visitor wants their own personalized copy, the app page shows a Fork button: one click duplicates the app under their wallet, where it now runs against their data.

For apps that genuinely need each visitor's own identity (per-user calculators, viewer-specific trade builders), you can ask Bankr to switch the app to "viewer mode" — the agent flips a single setting in the manifest. See Permissions for the details.

Before flipping an app to public or sharing the unlisted link, walk the public-app checklist — it covers the small set of rules that catch the most common breakage (most often: an iframe reads a key the manifest never declared, and anonymous viewers get a 403).

Fullscreen​

The app panel has a fullscreen icon next to Refresh. Click it and the app fills the viewport, hiding the terminal sidebar. Press Esc or click the icon again to return. Great for dense terminals — heat-maps, depth charts, long position tables.

Where to next​

  • Permissions — what an app can read, write, and execute on your behalf.
  • SDK Reference — the methods available to your app's frontend HTML and backend scripts, plus the manifest format and where app files live in your filesystem.