An AI agent that asks ShieldTrade before paying.

The agent surface is two things:

A Node SDK that any program can import to submit transactions through the same Gateway a human cashier or wallet would.
An MCP server (stdio transport) that exposes three tools — submit_evm_transfer, submit_card_payment, submit_protocol_bound — so an MCP-compatible agent runtime (Claude, etc.) can call ShieldTrade as a tool.

Three examples ship with the demo:

EVM — agent submits a 1 ETH transfer (end-to-end via the existing EVM simulator).
x402 — agent pays for a 402-protected resource (contract-only per ADR-0021 PR 3+ deferred).
ACT/A402 — agent submits an Alipay Machine Pay intent (contract-only).

MCP server config (drop into Claude / Cursor / any MCP client)

loading…

SDK config

loading…

Run the three examples

pnpm --filter @shieldtrade/agent-demo example:evm
pnpm --filter @shieldtrade/agent-demo example:x402
pnpm --filter @shieldtrade/agent-demo example:act-a402

What you are looking at

The SDK never sends skipSimulation, forceAllow, notApplicable, or any other caller-bypass field. Capability resolution is server-owned (ADR-0004).
The MCP server exposes the SDK as three JSON-RPC tools over stdio. Tools accept only the canonical fields.
Contract-only channels (x402, ACT/A402) demonstrate the SDK's type surface. The capability resolver currently returns Unsupported channel for these, so the decision is BLOCK until the sandbox verifier lands.
No signing material is held by the agent. The SDK mints a demo JWT for the pre-registered phase3-e2e tenant only.