Skip to content

Stock-token trading via Bankr

user

Trade Robinhood Chain Stock Tokens with Bankr: the three command surfaces, USDG settlement, Bankr's console verification, and proof-only receipts.

The lane, in one sentence

Trade Robinhood Chain Stock Tokens with Bankr: trades settle onchain against USDG, Bankr executes, and HISS validates commands, canonical addresses, and caps — then records receipts that only ever advance on proof.

Who does what

  • You pick one of the 15 canonical tokenized stocks/ETFs, set an amount, and acknowledge the two lane facts (tokenized exposure, Bankr executes).
  • HISS validates the intent — canonical address, explicit on robinhood venue, slippage and notional caps — and compiles a deterministic plan (with hash) plus the three-surface Bankr command pack.
  • Bankr executes: social, CLI, or Agent API. Bankr routes through USDG automatically; trades settle onchain against USDG on Robinhood Chain (4663).
  • Receipts reconcile after the fact: a Bankr job status can substantiate a job state; only a transaction receipt read from Robinhood Chain can confirm settlement.

The three Bankr surfaces

Tag the bot on X with a natural-language command:

social — @bankrbot on X
@bankrbot buy $100 of NVDA on robinhood
@bankrbot swap $50 of USDG to SPY on robinhood
@bankrbot sell half my AAPL on robinhood

Or run the Bankr CLI non-interactively:

cli
bankr --ni "buy $100 of NVDA on robinhood"

Or call the Bankr Agent API — POST https://api.bankr.bot/agent/prompt with an X-API-Key header (key from your own BANKR_API_KEY) and body { "prompt": "buy $100 of NVDA on robinhood" }. The API is asynchronous: it answers with a jobId you poll at GET /agent/job/{jobId} (statuses: pending, processing, completed, failed, cancelled).

Canonical addresses only

Address is identity. The lane recognizes exactly 15 tokens — AAPL, AMD, AMZN, COIN, GOOGL, META, MSFT, NVDA, PLTR, TSLA, SPY, QQQ, SGOV, SLV, CUSO — at the addresses in the canonical registry, each with a verified Chainlink feed. A same-ticker token at any other address is rejected everywhere: intents, command packs, and receipts.

Bankr’s console verification

Bankr may require console verification before Robinhood stock-token trades. When Bankr answers with a verification error, HISS surfaces it as exactly what it is — Bankr’s own external requirement, completed in Bankr’s console. HISS never collects your location, never performs the verification, and never gates the lane on jurisdiction.

Receipts: proof or nothing

A prepared plan is status prepared. A Bankr job status maps to a job_* state — and a completed job is still job_completed_unconfirmed, because job completion is Bankr’s word, not settlement. Only a transaction receipt read from Robinhood Chain 4663 over RPC produces onchain_confirmed (or onchain_reverted). There is no synthesized fill state anywhere in the lane.

Try it: the token table, per-token command previews, and the lane tool with the reconciliation panel. Developer reference: Bankr stock-token lane.

$HISS is independent research software in pre-execution readiness checks — not investment advice, and not affiliated with Robinhood, Bankr, or Chainlink.

Stock-token trading via Bankr · HISS