Governed agentic trading on Robinhood - #117
Merged
Merged
Conversation
…x402 endpoints, mcp bridge, guard proxy
mizuki0x
force-pushed
the
feat/robinhood
branch
from
August 1, 2026 18:42
38854f7 to
c3658d9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a trust and governance layer for agent trading on Robinhood: a policy gate in front of every order, a signed on-chain receipt for each decision (placed or blocked), and portable trading reputation. Built on Robinhood's public Crypto Trading API (Ed25519), plus a Guard MCP proxy for the hosted agentic endpoint.
What's here
agent-os/crates/covenant-robinhood— Ed25519 request signer, a read/order REST client over a swappable transport, theTradingPolicygate (per-order/daily caps, allow/deny universe, sides, order types, rate, cooldown, daily-loss stop, human-approval threshold),GovernedTrader(price → authorize → execute/block/approve, emitting a signedTradeReceiptfor every decision), atradingreputation signal, and a mock/replay harness. 28 unit tests.covenantdwiring —robinhood.*tools (account, holdings, quote, estimated_price, place_order, cancel_order, receipts, reputation) behind the existing capability gate. The trading key never enters the daemon: signing is delegated to anenv_clear()covenant-robinhood-signersidecar (same isolation as the metaplex/x402 signers). Every decision is anchored on-chain through the metaplex signer, with an optional Telegram approval gate.services/robinhood-mcp-bridge— exposes the governed tools over MCP.services/robinhood-guard-proxy— a self-contained MCP-to-MCP proxy in front ofagent.robinhood.com/mcp/trading: reads pass through, order tools run the local policy first (fail-closed), decisions are signed. Published as@covenant-org/robinhood-guard-proxy.services/x402-seller-base— two paid endpoints:POST /x402/robinhood/governed-orderandGET /x402/proof/:agent/trading.Status
Interface-complete and unit-tested;
covenantdbuilds against current main. The live legs (Robinhood crypto-REST reads, and the proxy's Robinhood upstream tool names + auth passthrough) are env-gated and need a US Robinhood agentic account to validate end-to-end. The governed-trading demo runs dry-run against a mock with real on-chain-anchored receipts (cargo run -p covenant-robinhood --example anchored_demo).Enable via
COVENANT_ROBINHOOD_{SIGNER_BIN,API_KEY,KEYPAIR,ATTESTOR_KEYPAIR,POLICY}(plusTELEGRAM_TOKEN/CHAT_IDfor approvals). Not a broker, adviser, or custodian: infrastructure the operator runs on their own account with their own key.