Polymarket 
Event markets, sports, arb paths, and prediction flow under bounds you set. CLOB prepare shipped in the public plane.
01 · How it works
Not one bot. A mesh: Input / Command hits the oracle control plane, then fans out across venue profiles, multi-chain EVM, Bitcoin, Solana, and a protocol builder. The public plane is prepare-only. Your wallet signs.
Event markets, sports, arb paths, and prediction flow under bounds you set. CLOB prepare shipped in the public plane.
Native perps, HIP-3/4 asset resolve, TA, event risk, and HyperEVM when you need HL's EVM surface.
RH Chain markets, NFTs, names, token scans, and chain-local routing on 4663.
Swaps, research, Jupiter routes. The bounded lane decodes every instruction and bans delegation ops outright.
Ordinals, runes, and BTC research. Every PSBT input carries proven provenance, so fees are computed, not asserted.
DEX routes, LI.FI and Relay bridges, DeFi across ETH and L2s. Bounded evm-swap and evm-bridge lanes, prepare-only until you sign.
Stable mainnet launch radar and venue ops on chain 988, scanned straight from the chain's own logs.
Scaffold contracts, run security gates (Foundry + static checks), prepare unsigned deploys through pinned factories. You still sign every deploy.
Drop in another profile for a new chain or venue. Same custody model, your wallet, your limits, your revoke.
The model proposes. Policy bounds. You own signatures. Multi-profile desks, not one omniscient chatbot. Vaults, perps, bridges, and protocol scaffolds, not just swaps. Empty allowlists refuse everything until you configure them.
claims without receipts don't countMax value, chain, venue, destinations, and TTL. Outside the grant = hard refuse, not an agent with a free wallet.
hl, poly, evm-swap, evm-bridge, btc, sol. Each decodes its own envelope, proves every value-moving field, and refuses while its allowlists are empty.
Prepared actions ship as stamped, hash-bound envelopes. Money claims end in tx hash, receipt status, balance delta, and allowance state. No “looks filled.”
Labels your agent, your cold wallet, your counterparties. On by default. A label is never an authorization, and key material is hard-rejected by field name.
minOut, impact, spender, and decoded calldata before approval. Export unsigned artifacts for hardware wallets.
Destination allowlists stop silent router drift. New contracts stay blocked until you add them.
02 · Wallets
Use one wallet everywhere, or separate wallets per chain. Permissions are per wallet - change them, tighten them, or revoke them anytime.
One wallet across chains, or a dedicated wallet per chain. Same desk either way.
Caps, allowed actions, and scopes sit on each wallet, not a global free pass.
Edit permissions when risk changes. Revoke a wallet's access without killing the whole account.
03 · Chains
Live coverage grows with the profile mesh. Each chain maps to an agent, and new agents can join.