Configure and export your policy from Check a trade. The API prepares unsigned proposals; preflight binds evidence to the exact call. Your installed signer adapter revalidates before signing.
Let’s Hunch!
Your agent proposes a trade. Your rules decide what can be signed.
- 01 Propose a trade
- 02 Check your rules
- 03 Enforce before signing
What should your agent do?
A decision you can inspect.
Choose an asset and wallet to check the exact trade, costs and live dependencies.
Read complete evidence
What the policy covers
Exact native input, output floor, wallet, venue, fees, deadline and supported live dependencies. The SDK verifies a signed receipt and rechecks immediately before asking your signer to sign.
This page prepares and tests calls without signing or moving funds. Community tokens require an explicit allowlist and acceptance of missing permission, concentration and TWAP evidence. A passing result is scoped to your policy.
03 / Connect this policy to your agent
03 / TAKE IT TO YOUR AGENT
Same policy. Your signer.
Export the exact mandate for the JavaScript SDK, REST API or MCP proposal tools. Keep your policy, key pin and signing account outside the model’s control.
Integration guide ↗import { createExecutionClient }
from './hunch-execution-sdk.mjs';
const hunch = createExecutionClient({
operatorPolicy: policy
});
const routes = await hunch.prepare({
outputAsset, amountInWei
});
// The trusted runtime approves exact intent
// and installs createExecutionSigner.Supported assets, venues and execution scope
Native ETH exact-input buys into the published stock-token and community-token pools. V3 fee tiers are compared within your fee limits. Availability still depends on liquidity, fresh references, restrictions and simulation. Sell routes, ERC-20 approvals, multihop and smart-account execution are not enabled. Venue adapters are integrations, not partnerships or independent security audits.
Read the current whitepaper ↗ · Service economics ↗Give every move a Hunch.
Understand the asset, its dependencies, and the evidence your agent needs before moving capital.
The decision behind the data
On-chain controlsResolve recognized forwarding contracts and inspect runtime evidence.
Agent briefWhat the observed controls mean, and what to check next.
Market contextPool dependencies and official RH instrument identity.
Save a baseline. Compare the next observation.Start with an address.
Get a decision brief, market dependencies,
and a shareable card with a link to run the check.
Know what a token represents.
An agent sees a balance. Hunch reconciles the financial meaning behind it.
One token is not always one share.
Identity firstMatch the chain and contract against the official registry.
Corporate actionsReconcile shares per token with on-chain state.
Price semanticsREST share prices need one multiplier. Chainlink stock-token feeds already include it.
Financial context belongs in the decision.
Check corporate actions, oracle pauses,
trading halts and reference-price freshness.
An explicit second look.
Evaluate a proposed action against a published, fixed policy profile.
Intent meets policy.
Missing required data returns a review decision.
It never silently becomes a passing check.
Simulate the next move.
Simulate an EVM call against RH mainnet state without broadcasting it.
Execution has context.
Inspect execution status, returned bytes, and an optional gas estimate.
Simulation success is not signing approval.
Keep instructions in place.
Inspect external text for six recognizable prompt-injection and secret-request patterns.
External text stays data.
Review matched patterns and the exact excerpts.
No match cannot establish that text is safe.
Keep the important ones close.
Your watchlist stays in this browser. Refresh to observe new evidence; save a report to establish a comparison baseline.
Up to 10 contracts. Monitoring stops when this page is closed. This is not a background alert service.
A record of the decision.
Reports are saved only when you choose. Storage is local to this browser.
Give your agent a Hunch.
One policy from your workspace to your agent. JavaScript signer enforcement; REST and MCP for preparation and preflight.
The same policy works in the workspace and JavaScript SDK. Add the signer adapter to the runtime that already controls your wallet. Research methods remain available through the same SDK.
Download JavaScript clientDownload the stdio adapter and add this configuration to your MCP client. The policy file is set by the operator, outside the model’s tool arguments. MCP tools cannot sign or change that policy.