Client
The @mure/sdk client wraps the lower-level @mure/api-v2 client and a blockchain adapter into one interface. It handles transaction creation, API communication, and on-chain submission in one call.
Installation
Creating a Client
Use createClient to instantiate the client. You must provide an Adapter — the SDK ships with a viem adapter out of the box.
import { createClient, viem } from "@mure/sdk";
import { http } from "viem";
import { sepolia } from "viem/chains";
import { privateKeyToAccount } from "viem/accounts";
const adapter = viem({
chain: sepolia,
transport: http(),
account: privateKeyToAccount("0x..."), // replace with your private key
});
const client = createClient({ adapter });API configuration
Pass API options under the api key. Both fields are optional, so createClient({ adapter }) stays valid.
const client = createClient({
adapter,
api: {
url: "https://api.mure.app/v2", // optional, defaults to this URL
apiKey: process.env.MURE_API_KEY, // optional
},
});createClient throws ClientConfigError synchronously when api.apiKey is a blank string. An absent key is allowed. See Authentication for credential semantics.
Transfer
The transfer method creates a transfer intent via the API and immediately submits the resulting transaction through the adapter.
import { eth } from "@mure/sdk/accounts/evm";
const hash = await client.transfer({
to: eth("0x8f664a25158021EFb4470f9036431664ce9f7895"), // recipient address
asset: "USDC",
amount: 10_000_000n, // 10 USDC (6 decimals)
});transfer resolves to the transaction hash as a bare hex string. It does not return an outcome array.
Parameters
| Field | Type | Required | Description |
|---|---|---|---|
from | Address | No | Source address and chain. Defaults to the adapter's connected account. |
to | Address | Yes | Destination address and chain (same chain as from). |
asset | string | { in: Address; out: Address } | Yes | Token symbol, CAIP-10 asset, or swap pair. See Swaps. |
amount | bigint | Yes | Amount to transfer as a bigint. |
deadline | string | No | Latest execution time (ISO 8601). Defaults to +1 hour. |
callData | string | No | Hex-encoded calldata forwarded to recipient. |
Explicit from
When from is omitted, the client uses the adapter's connected account. You can also provide it explicitly:
import { sepolia } from "@mure/sdk/accounts/evm";
const hash = await client.transfer({
from: sepolia("0x3165fd5B9D37Ac9619aC5895CA33F308aB02a053"), // sender address
to: sepolia("0x8f664a25158021EFb4470f9036431664ce9f7895"), // recipient address
asset: "USDC",
amount: 10_000_000n, // 10 USDC (6 decimals)
});Swaps
To swap one asset for another on the same chain, pass an { in, out } object instead of a single asset string.
Both fields accept the same address formats as from and to.
import { base, eth } from "@mure/sdk/accounts/evm";
const USDC = eth("0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48");
const NATIVE_ETH = eth("0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE");
const hash = await client.transfer({
to: eth("0x8f664a25158021EFb4470f9036431664ce9f7895"),
asset: { in: USDC, out: NATIVE_ETH },
amount: 10_000_000n,
});Cross-chain bridges
To move assets across chains, set to to an address on a different chain than from. The SDK submits a single transfer call and Mure selects a bridge route automatically.
import { base, eth } from "@mure/sdk/accounts/evm";
const USDC = eth("0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48");
const hash = await client.transfer({
from: eth("0x3165fd5B9D37Ac9619aC5895CA33F308aB02a053"),
to: base("0x8f664a25158021EFb4470f9036431664ce9f7895"),
asset: { in: USDC, out: USDC },
amount: 10_000_000n,
});Submission and confirmation
transfer is two operations in one call:
- POST a transfer intent to the API.
- Hand the returned transaction to the adapter.
The SDK adds no confirmation step of its own. Whether the user sees a prompt depends on the adapter's account. The examples on this page use privateKeyToAccount, so submission is silent. A browser-wallet transport prompts through the wallet.
Create without sending
transfer sends the transaction as soon as the API returns it. To inspect the intent — including the quote metadata — before you submit, call client.createTransfer. It creates the intent and resolves with the full response; it does not send.
const intent = await client.createTransfer({
to: eth("0x8f664a25158021EFb4470f9036431664ce9f7895"),
asset: "USDC",
amount: 10_000_000n,
});
console.log("Quote", intent.metadata.provider, intent.metadata.out);
console.log("Submit to", intent.tx.to);
// Submit only after you decide.
const [outcome] = await client.send(intent.tx);A batch moves value to more than one place in one order. Pass transfers and put
deadline and options.simulate at the root; an entry never carries either.
const intent = await client.createTransfer({
deadline: new Date(Date.now() + 60 * 60 * 1000),
transfers: [
{ from: account, to: payee, asset: "USDC", amount: 10_000_000n },
{
from: account,
to: base("0x8f664a25158021EFb4470f9036431664ce9f7895"),
asset: { in: "USDC", out: "USDC" },
amount: { out: 25_000_000n },
},
],
});
console.log("Records", intent.metadata.transfers.map((record) => record.type));createTransfer accepts the same arguments as transfer and resolves with the create response.
| Field | Type | Description |
|---|---|---|
id | string | Intent id. |
type | "transfer" | "swap" | "bridge" | "batch" | Inferred operation type. |
status | TransferStatus | Lifecycle status. |
orderId | `0x${string}` (optional) | On-chain order id. |
metadata | object | Chain id, gas, the per-transfer records, and — when the request routed to the quote service — the quote projection. |
metadata.transfers | array | One record per transfer, in request order: { type, recipient, token, amount, outputHash? }. A record carries that transfer's own type and no index; outputHash is absent on an intent created before the canonical-output table existed. |
tx | Transaction | The transaction to submit. |
createdAt / updatedAt | Date | Timestamps. |
Quote metadata
When the request routed to the quote service, metadata carries the quote projection:
| Field | Type | Description |
|---|---|---|
provider | "across" | "cow" | "mayan" | "relay" | "sushiswap" | "uniswap" | The protocol that produced the winning quote. |
route | array | The described path, in order. Each hop is { chainId, tokenIn, tokenOut, venue? }. |
costs | { total, sources, outputUsd } | The normalized costs on the one USD basis. |
in / out | { chainId, amount?, expectedAmount?, minAmount? } | The exact side carries amount; the quoted side carries expectedAmount and minAmount. |
slippageBps | number | The settlement band minAmount derives from. |
Amounts are bigint in the SDK; the wire carries base-unit strings. A plain same-chain transfer carries none of these fields.
Send
For transactions you have already constructed, use client.send to broadcast them through the configured adapter. Pass one transaction or an array.
const outcomes = await client.send([
{ to: "0x...", data: "0x...", value: 0n },
{ to: "0x...", data: "0x...", value: 0n },
]);send returns one outcome per input, in input order.
| Status | Payload | Meaning |
|---|---|---|
success | hash | The transaction was included in a block. |
reverted | hash | The transaction was included but reverted on-chain. |
failed | cause | The adapter rejected the transaction before inclusion. |
unknown | hash? | The adapter could not confirm the result within the poll bound. |
A single transaction resolves to a one-element outcome array.
const [outcome] = await client.send({ to: "0x...", data: "0x...", value: 0n });The adapter owns batching. When the wallet supports EIP-5792, send submits the batch with one call and polls the call status. When the wallet does not support batching, the adapter sends the transactions sequentially and reports each result. A batch does not fail as a whole because one transaction failed.
send is useful when you want to combine Mure-generated transactions with your own calls, or when you are using a wallet model such as account abstraction or EIP-7702 that is covered by Mure's Unified Entrypoint.
Reading transfers and tokens
List transfers
const transfers = await client.listTransfers(); // newest page
const swaps = await client.listTransfers({ type: "swap" }); // filtered page
const counted = await client.listTransfers({ totals: "true" }); // with the countThe args parameter is optional. Omit it to read the newest page.
| Field | Type | Required | Description |
|---|---|---|---|
type | "transfer" | "swap" | "bridge" | "batch" | No | Filter by transfer type. A multi-transfer intent appears only under batch. |
limit | number | No | Page size, clamped to 1–200. Defaults to 50. |
cursor | string | No | The nextCursor from the previous page. Must match the filter set. |
totals | "true" | "false" | No | Ask for the matching count in total. Defaults to false. |
Returns { items: TransferSummary[], total: number | null, nextCursor: string | null }.
total is a number only when totals was sent. nextCursor is null on the
last page; re-send it with the same filters to read the next page.
| Field | Type | Description |
|---|---|---|
id | string | Transfer id. |
type | "transfer" | "swap" | "bridge" | "batch" | Transfer type. |
status | "draft" | "pending" | "confirmed" | "failed" | "expired" | "finalized" | Transfer status. |
createdAt | Date | Creation time. |
updatedAt | Date | Last update time. |
orderId | `0x${string}` (optional) | Order id when the transfer has one. |
metadata | { chainId: "eip155:<ref>"; hash?: "0x<hex>"; transfers: TransferSummaryRecord[] } | Chain id, transaction hash, and the per-transfer records. |
Get one transfer
const transfer = await client.getTransfer({ id: "int_transfer_01..." });The args parameter is required and must contain id.
| Field | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Transfer id. |
Returns a single TransferSummary with the fields listed above.
List tokens
const page = await client.listTokens({ chainId: "eip155:1" }); // one page
const all = await listAllTokens((filter) => client.listTokens(filter), {
chainId: "eip155:1",
}); // every page, concatenatedlistTokens answers one page. The args parameter is optional; omit it to read
the first page of every chain.
| Field | Type | Required | Description |
|---|---|---|---|
chainId | `eip155:${number}` | No | Filter by chain. |
limit | number | No | Page size, 1–200. Defaults to 50. |
cursor | string | No | nextCursor from the previous page. |
search | string | No | Narrow the set; the order stays editorial. |
Returns { items: TokenDefinition[]; total: number | null; nextCursor: string | null }.
total is the matching count on the first page and null afterwards;
nextCursor is null on the last page.
listAllTokens is the SDK's one page walk. It stops at a null cursor, fails on
a read error, and fails on a repeated cursor. Pass an optional third argument to
bound the walk: { maxPages, timeoutMs }.
| Field | Type | Description |
|---|---|---|
symbol | string | Token symbol. |
chainId | string | Chain id. |
address | string | CAIP-10 account for the symbol and chain pair. |
decimals | number | Token decimals. |
metadata | object | null | Name, logo, CoinGecko id and description. |
EVM account helpers
The SDK ships with small helpers that build CAIP-10 identifiers for common EVM chains. They are available from @mure/sdk/accounts/evm.
import {
eth,
sepolia,
base,
baseSepolia,
hyperliquid,
hyperliquidTestnet,
} from "@mure/sdk/accounts/evm";
const mainnetAccount = eth("0x8f664a25158021EFb4470f9036431664ce9f7895");
// => "eip155:1:0x8f664a25158021EFb4470f9036431664ce9f7895"Use these helpers to keep addresses chain-scoped and avoid hand-written CAIP-10 strings in examples.
Imports
The SDK exposes one root entry and four documented subpaths.
| Import path | Exports |
|---|---|
@mure/sdk | createClient, ClientService, ClientServiceError, ClientConfigError, viem, ViemAdapter, AdapterService, AdapterServiceError, and the public types. |
@mure/sdk/adapters | AdapterService, AdapterServiceError, ViemAdapter, viem. |
@mure/sdk/accounts/evm | eth, sepolia, base, baseSepolia, hyperliquid, hyperliquidTestnet. |
@mure/sdk/chains | toCAIP. |
@mure/sdk/chains/evm | toCAIP. |
Error Handling
All SDK errors are surfaced as ClientServiceError. Wrap calls in try/catch to handle failures.
import { ClientServiceError } from "@mure/sdk";
import { eth } from "@mure/sdk/accounts/evm";
try {
const hash = await client.transfer({
to: eth("0x..."), // recipient address
asset: "USDC",
amount: 10_000_000n, // 10 USDC (6 decimals)
});
} catch (error) {
if (error instanceof ClientServiceError) {
console.error("Transfer failed:", error.message);
}
}Effect-TS Integration
For advanced use cases, you can access the client inside an Effect program.
import { Effect } from "effect";
import { ClientService } from "@mure/sdk";
import { eth } from "@mure/sdk/accounts/evm";
const program = Effect.gen(function* () {
const client = yield* ClientService;
const hash = yield* client.transfer({
to: eth("0x..."), // recipient address
asset: "USDC",
amount: 10_000_000n, // 10 USDC (6 decimals)
});
return hash;
});The ClientService is a Context.Service. Provide it via ClientService.layer combined with an Adapter and ApiClient.layer.
import { ClientService } from "@mure/sdk";
import { ApiClient } from "@mure/api-v2/client";
import { Effect } from "effect";
const runnable = program.pipe(
Effect.provide(ClientService.layer),
Effect.provide(adapter),
Effect.provide(
ApiClient.layer({
baseUrl: "https://api.mure.app/v2",
apiKey: process.env.MURE_API_KEY,
}),
),
);
Effect.runPromise(runnable).then(console.log).catch(console.error);