Trading via Robinhood
The integration connects an eligible BLEEEP Agent signal to broker execution through Robinhood Agentic Trading. This is separate from Robinhood Chain anchoring: the chain carries BLEEEP’s proof commitment, while Robinhood Agentic Trading is a broker interface whose order and fill claims require authenticated broker evidence.
Robinhood offers eligible users a Trading Model Context Protocol (MCP) interface for compatible third-party agents and a dedicated Agentic Account. Availability depends on Robinhood’s released product, region, account, and asset support. BLEEEP must publish its own supported scope and cannot describe the integration as a partnership, endorsement, or live connection unless separately established.
The workflow
- Decide and commit. BLEEEP produces an eligible action signal or
TRADE_ABSTENTION; the signal’s accepted anchor must reach the required finality before the registered deadline. - Authorize. The user creates and funds the dedicated Agentic Account, connects the integration, and creates a single-use or continuing execution mandate within BLEEEP’s bounded permissions and Safety Vault controls.
- Route or abstain. At routing time, BLEEEP checks the current effective routing authority. Each submitted instruction records its originating decision and mandate identifier and version. An abstention produces no order.
- Capture broker evidence. BLEEEP records the broker identifier, status, fills, fees, and timestamps exposed through an integrity-protected broker receipt or authenticated account-history record.
- Anchor the event record. The broker event enters a later event-evidence batch under its evidence-source label. That anchor makes subsequent alteration of the registered record detectable; it does not independently prove the broker event.
The user retains responsibility for the dedicated brokerage account, and BLEEEP does not custody the brokerage funds. Proof-class and evidence-source labels continue to distinguish a pre-outcome signal, a paper fill, an onchain transaction supported by ON_CHAIN_TRANSACTION_RECORDS, and a broker fill supported by VENUE_AUTHENTICATED evidence.
Neither public proof verification nor BLEEEP Prop participation depends on this integration.
Next: User strategies covers ownership, the collective record, and the learning boundary.