Bring your agent’s trade

Configure a trade →Install the SDK ↘Bring a workflow ↘

01 / CONFIGURE

Define the boundary.

Choose assets, spending caps, slippage, network budget and permitted hooks in the workspace. Export the policy and review it in your trusted runtime.

02 / CHECK

Inspect the whole plan.

Prepare supported V3, V4 or mixed swaps. Check exact approvals, call recipients, amount floors and relevant stock-token units against current evidence.

03 / ENFORCE

Keep the signer in control.

Approve the complete plan and install the signer wrapper beside your account. It checks locally and revalidates signed evidence before each signature.

One install. Your existing agent.

Node 22+. No API key or HUNCH token required. The public service is currently free, subject to rate and shared capacity limits.

npm install --save-exact https://hunchagents.xyz/hunchagents-sdk-0.9.1.tgz

This is Hunch’s first-party package download, with TypeScript declarations and a bundled MCP adapter. Compare its published integrity and file list, and retain your package lockfile. It is not yet listed on the npm registry. The client package is MIT licensed; included dependencies retain their licenses.

Make your first read-only request

import { HunchClient } from '@hunchagents/sdk';

const hunch = new HunchClient();
const evidence = await hunch.inspectToken(
  '0x0bd7d308f8e1639fab988df18a8011f41eacad73' // RH WETH
);
console.log(evidence);

Then export your own reviewed policy from Check a trade. Run the included check against your actual wallet, input and output addresses, and raw input amount:

node node_modules/@hunchagents/sdk/examples/check-trade.mjs   /operator/policy.json INPUT_ADDRESS OUTPUT_ADDRESS RAW_AMOUNT

This command prepares and evaluates an unsigned plan. It outputs a local summary of outcomes and phase timings without wallet addresses, trade amounts or raw reports. It does not install enforcement or send that summary to Hunch. An unfunded wallet or unavailable evidence can prevent clearance. Follow the signer integration guide to install enforcement.

Prefer MCP?

{ "mcpServers": { "hunch": {
  "command": "node",
  "args": ["/YOUR_APP/node_modules/@hunchagents/sdk/mcp.mjs"],
  "env": {
    "AGENT_SECURITY_URL": "https://hunchagents.xyz",
    "HUNCH_EXECUTION_POLICY": "/operator/policy.json"
  }
} } }

Use an absolute path and a reviewed version 2 policy. MCP can prepare and check; it cannot sign or change the configured policy. You can also download the standalone MCP adapter, use REST / OpenAPI, or integrate the portable JavaScript module. Hosted API calls from third-party websites should go through their backend.

OPEN BUILDER REVIEW

Bring your agent’s trade.

Bring a proposed supported swap and the rules it must obey. Together, we can examine its approval sequence, evidence gaps, policy refusal and changed-call behavior. We’re seeking independent, reproducible integration case studies.

Start asynchronously by sending your framework, public asset pair, protocol or PoolKey, the policy controls you need and a reproducible issue. Share a redacted local summary if useful. Keep wallet addresses and strategy details out of the initial email unless you choose to disclose them.

Request a technical review →

Email info@hunchagents.xyz. This opens your email client; nothing is submitted until you send. We will agree any public attribution or case study with you first. Privacy notice.

A precise integration boundary.

Current scope: exact-input Uniswap V3, V4 and mixed swaps; native/ERC20 funding; bounded approvals and Permit2; up to three explicit hops. Nonzero hooks require reviewed runtime pins and empty hookData. Signing support is for undelegated EOAs.

Pons launch curves, PARE split/merge, lending, LP actions and smart-account modules need additional adapters. A technical request is not an accepted partnership. Full coverage · Live evidence.

Your agent’s trade.Your rules.