hunch.What is live today
Hunch is an independent project building RWA decision intelligence, starting on Robinhood Chain. The public console and read-only API are live. JavaScript, TypeScript declarations, Python and MCP entry points are available in the integration guide.
No wallet connection, custody, signing or transaction broadcast.
Reports carry sources, observation times, coverage and reasons.
The context API returns review or block. It never grants signing clearance.
Use the intelligence workspace · Check the current service response · Read the machine-readable capabilities
The health response confirms that the application is responding at that moment. It is not an uptime history or a guarantee that every upstream data source is available.
How a decision is supported
- Identify the asset. Compare its address and chain against the official RH registry or documented canonical contracts. A familiar ticker does not establish identity.
- Reconcile financial meaning. For recognized stock tokens, compare instrument interfaces, corporate-action multipliers, reference-price identity, freshness and pause or halt signals.
- Inspect the dependencies. Read recognized contract-forwarding patterns and available market pools. The context API uses the counter asset the caller selects.
- Keep the action separate. Optional EVM simulation examines a supplied call at an observed chain state. The integrating application still validates intent, policy and signing.
Every result must be read with its coverage. An official address match is an identity observation, not an endorsement or a safety rating. A successful simulation is not proof of sellability, future execution or acceptable risk.
Where the evidence comes from
| Source | Used for | Interpretation |
|---|---|---|
| Robinhood Chain RPC | Code, interface and storage reads; EVM simulation. | Observed chain state, subject to provider availability and reorganization. |
| Official RH instrument APIs | Stock-token registry, metadata and USD reference prices. | Identity and reference context; not a trading quote or redemption entitlement. |
| DexScreener | Indexed pools and reported market activity. | Coverage is not exhaustive; pool liquidity includes both sides. |
The RWA thesis separately cites market research and dates its figures. Those global market figures are not Hunch usage, Robinhood Chain activity or measured agentic-DeFi market size.
Known limits and development priorities
Current checks do not establish a complete permission graph, verified source-code audit, holder concentration, liquidity locks, transfer taxes, redemption eligibility or decoded transaction asset flows. On-chain oracle rounds and sequencer uptime are not independently checked. Different components may be observed at different times and blocks.
Reports are unsigned. A request fingerprint identifies normalized inputs; it does not prove who issued the report or what calldata will do. Browser watchlists run while the page is open and are not a persistent monitoring service.
Simulation has a 5,000,000 gas cap. Calls needing more gas, including some venue-specific hook routes, are outside current coverage. No venue adapter or protocol partnership is represented as verified.
Our development priorities are deeper permission and holder evidence, oracle checks, validated adapters and dependable monitoring. The context contract explains today's behavior so teams can evaluate it before relying on it.
Data handling and service controls
No analytics or advertising trackers are installed. Checks are processed on the server; network and market queries go to the providers described in the Privacy notice. Saved evidence and watchlists stay in your browser unless you export or share them. Submitted text is checked deterministically and is not sent to an LLM.
The public site uses HTTPS. The application restricts browser resource origins, blocks framing, limits request size and rate, and exposes read-only network operations. These are specific controls, not a claim that Hunch has completed an independent audit or certification.
Public access currently has no paid service-level agreement. Source failures, rate limits and gaps are reported for review. Keep independent controls and handle errors explicitly in an integration.
Project, token and commercial status
The console and API currently offer free public access. Paid billing, persistent monitoring, a token launch, buybacks and burns are not enabled. No official HUNCH contract address has been published. The economics page distinguishes the proposed model from active functionality.
Hunch is not affiliated with or endorsed by Robinhood, Hookr, Pons or the protocols discussed in our research. Names and links identify sources, technologies or prospective integration workflows. They do not establish partnerships.
Service use is governed by the Terms of use. Any future commercial offering or token launch needs separately published terms and verified details.
Report a security issue
Email info@hunchagents.xyz with the subject “Hunch security report.” Include the affected page or endpoint, a concise description and a minimal reproduction using non-sensitive data.
For sensitive technical details, request a suitable sharing method first. Do not send private keys, recovery phrases or other people's personal data. Test only resources you are authorized to use, and avoid disruption or access to others' data. No bug-bounty reward or response-time commitment is currently published.
The contact is also available in security.txt.
Questions, corrections and integrations
Use info@hunchagents.xyz for product questions, source corrections, privacy requests and integration inquiries. Include a report ID, source and observation time when reporting evidence problems; omit confidential transaction details unless needed.
Our official website is hunchagents.xyz and our public X account is @hunchagents. Check official pages for launch information and updates. Hunch does not need your signing secrets to provide intelligence.