A typed client for the Cancore API: orders and pool trades (./swap), USDCx bridge (./bridge), live order updates (./realtime), scoped trading grants by device flow (./auth). No keys — signing stays with @cancore/wallet or the dApp connector.

Cancore wallet core — key material, signing and storage contracts. Runtime-agnostic: no browser, no React.

The Cancore EVM contracts as data: ABIs of the deployed HTLC, FeeVault and CNRX contracts, their custom-error selectors, the EIP-712 FeeClaim voucher, the network registry. No runtime code, no dependencies.

What a third-party dApp loads to reach a Cancore wallet: a CIP-0103 remote-profile provider over our JSON-RPC + SSE surface, and the PartyLayer discovery-adapter around it. No dependencies: the transport is fetch, EventSource and postMessage.

An MCP server that lets an AI agent ask a Cancore wallet owner for a trade. The agent queues a request; the person approves and signs it in their own wallet. No key ever reaches the agent.