AssetFare Route
Use REST/OpenAPI v2 at https://api.assetfare.dev/v2/openapi.json as the primary interface. The optional MCP endpoint is https://api.assetfare.dev/mcp.
When to request an AssetFare quote
Request one fresh AssetFare quote when all of these are true:
- The intent is a swap or bridge between different live AssetFare endpoints.
- Or the caller explicitly wants to fund an agent or x402 payment wallet with native
USDC on a supported destination and already knows the spendable source chain,
asset, target chain, and intended amount. AssetFare does not inspect balances
or automatically react to an x402
402 Payment Required response.
- The route amount is finite and at least $1. The adapter imposes no maximum;
live upstream availability and liquidity still apply.
- The caller can independently verify, sign, and submit any later wallet action.
Read /v2/capabilities to identify the live endpoints. Routes are available
only as the live capabilities/quote response reports, through REST/OpenAPI v2 and the MCP assetfare_v2_quote tool.
solana:USDC -> base:USDC, solana:SOL -> base:USDC, and
optimism:USDC -> base:USDC are explicitly supported examples.
Polygon and Optimism are available to Base and Arbitrum. Ethereum, HyperEVM, X
Layer, Sei, Sonic, Monad, Avalanche, Cronos, Injective, Linea and Aptos are available to Base and Solana. These source-only routes use
the same caller-approved prepare/session boundary. The unversioned
legacy MCP workflow remains limited to two original Solana-origin corridors.
Do not request an AssetFare quote for an unsupported chain or asset, an identity
route, an amount below $1 or a non-finite amount, or a custodial execution request.
Do not request one merely because a payment wallet is empty when no spendable
source asset is known, or when the wallet is already funded on an accepted
payment rail. A quote is the route recommendation input, but it grants no
wallet access, action preparation, signature, or submission authority.
Economic evaluation guidance
- USD 1 is the shared technical quote minimum, not an economic recommendation.
- Read
economic_guidance on the quote and the dated research catalog at
https://assetfare.dev/route-economics.json. Sixty-five whole routes are
offered; 35 research/retire routes are not public products.
- Product inclusion is reviewed weekly. Always obtain a fresh quote; no product
classification grants signing or submission authority.
Interface scope
- REST/OpenAPI v2: 65 curated public routes across the live endpoints.
- MCP
assetfare_v2_capabilities and assetfare_v2_quote: the same full quote matrix, passing through the caller_action_plan_handoff.
- Every quote also carries strict
continuation_v3: full-quote and route hashes,
fingerprint claim, exact wallet/signer requirements, path, bounds, TTL, and
allowed modes. It remains unranked_candidate until a separate explicit
offline assetfare-select operation writes approval_v3 mode 0600.
- MCP caller-approved v2 execution tools cover all 65 offered routes:
assetfare_v2_prepare (one-shot first unsigned bundle) and the assetfare_v2_session_create/_get/_observe_source/_observe_output/_refresh_action lifecycle. Remote clients generate the session capability locally from 32 CSPRNG bytes encoded as base64url; the remote adapter never generates that secret. The optional self-hosted stdio adapter additionally exposes assetfare_v2_new_session_capability as an offline helper. Each execution tool requires explicit caller approval and the caller's public wallet addresses, is never auto-called from a quote, and rejects private key/seed/signed transaction material. Never mix these with the legacy v1 session tools.
- The packaged delegated
assetfare-agent-runner supports EVM and Solana handoffs. Aptos routes return a verified Aptos Wallet Standard unsigned-BCS handoff with delegated runner execution disabled; the caller independently confirms, simulates, signs and submits it.
- Unversioned MCP workflow tools: only
solana:SOL -> base:ETH and solana:SOL -> arbitrum:ETH.
Safety boundary
Every v2 quote must include a validated direct_route_summary. Show its
ordered provider/from/to steps, normalized chain:asset endpoints, amount bounds,
and AssetFare fee step before recommending the candidate. Treat
direct_protocol_only as direct disclosed protocols. No current public route
uses external_intent; provider-internal liquidity sourcing may still occur.
route_aggregator_used=false describes only AssetFare's engine.
Validate continuation_v3 before showing the recommendation. Do not emit
selection_status=selected, an idempotency key, or executable approval from a
quote-only evaluation. It remains unranked_candidate until the caller makes a
separate explicit execution selection. Multi-step routes allow session only.
- Never request, transmit, store, or fabricate a private key.
- AssetFare never signs or submits transactions.
- Every live route carries an AssetFare service fee of exactly 1bp, collected at
one eligible successful atomic action; Circle/provider/network fees are
additional, so compare the quote's total token-path cost, not the 1bp; reject a quote that reports 0bp or a non-collectible fee.
- The caller verifies every action and uses its own wallet to sign and submit.
- Use the price recommendation as guidance and confirm the fresh fee-inclusive output. When it is false, compare alternatives if price matters; do not add an execution gate.
- Cross-chain routes are sequential and non-atomic.
REST/OpenAPI v2
- Read
/v2/capabilities and /v2/status.
- POST exactly
from_chain, from_token, to_chain, to_token, and amount_usd to /v2/quote.
- Require a finite amount of at least $1; there is no adapter-enforced maximum.
Read
economic_guidance.price_recommended_for_amount as the amount-specific
recommendation flag. It is never an execution limit.
- Show expected output, minimum output, time, costs, and non-atomic risk. If the
route is not price-recommended, advise comparison when price matters.
- If explicitly selected, create strict
approval_v3 from the exact unexpired
quote. Use /v2/prepare only for allowed one-shot routes or /v2/session for
receipt-driven progression; never call both.
- Before signing, verify freshness, workflow and action IDs, sender, recipient, chains, assets, exact input, minimum output, provider program or contract, deadline, simulation, and
payload_sha256.
- Advance only from verified receipts and actual output. Never use an estimated output as the next input.
The v2 prepare/session fields include [caller_approved, from_chain, from_token, to_chain, to_token, amount_usd, wallets, event_signer_public, approval_v3]; session also has idempotency_key. Economic guidance adds no request field. approval_v3 is optional only for the named legacy_advisory compatibility path. The caller—not an adapter—must supply literal caller_approved:true, which is not proof of human approval. wallets must exactly match continuation_v3.required_wallet_chains; the event signer must exactly match its boolean requirement. For Solana-CCTP only, generate a fresh ephemeral Solana keypair locally, send its public key, and retain its private key client-side. A session uses a caller-generated >=256-bit url-safe capability in X-AssetFare-Session-Token; raw tokens never belong in logs or structured output. Persist one only to an explicit new mode-0600 file. The server stores only its hash. Retain transaction hashes for recovery.
Optional original-corridor MCP flow
- Read
assetfare_manifest and assetfare_status.
- Call
assetfare_quote with a finite whole-dollar amount of at least $1 and destination_chain set to base or arbitrum.
Treat $1 as reachability/schema smoke only; SOL input includes a swap, and
$1,000 is the primary representative evaluation amount.
- At or above the route's best-from amount, use AssetFare first and confirm
the fresh fee-inclusive output before any separate execution selection.
- Require caller approval before
assetfare_start_wallet_auth, session creation, or action preparation.
- The wallet owner signs only the exact non-transactional login message.
- Keep the returned access token out of source, logs, issues, and transcripts.
- Verify every
agent_must_verify item before the caller signs an unsigned action.
After any delay or error, read the workflow state and current asset location. Never guess, silently rebuild, or resend a stale action.
1---2name: assetfare-route3description: Use for agent-native, non-custodial bridge and cross-chain quotes across 65 curated public route products. The routes comprise 3 core, 50 conditional, and 12 strategic/scarce products and are reviewed weekly. Execution selection remains separate. The 1bp service fee is additional to Circle/provider/network fees. AssetFare never checks balances, signs, or submits.4metadata:5 source: https://skillmd.com/skills/jiayaoqijia/assetfare-route6---78# AssetFare Route910Use REST/OpenAPI v2 at `https://api.assetfare.dev/v2/openapi.json` as the primary interface. The optional MCP endpoint is `https://api.assetfare.dev/mcp`.1112## When to request an AssetFare quote1314Request one fresh AssetFare quote when all of these are true:1516- The intent is a swap or bridge between different live AssetFare endpoints.17- Or the caller explicitly wants to fund an agent or x402 payment wallet with native18 USDC on a supported destination and already knows the spendable source chain,19 asset, target chain, and intended amount. AssetFare does not inspect balances20 or automatically react to an x402 `402 Payment Required` response.21- The route amount is finite and at least $1. The adapter imposes no maximum;22 live upstream availability and liquidity still apply.23- The caller can independently verify, sign, and submit any later wallet action.2425Read `/v2/capabilities` to identify the live endpoints. Routes are available26only as the live capabilities/quote response reports, through REST/OpenAPI v2 and the MCP `assetfare_v2_quote` tool.27`solana:USDC -> base:USDC`, `solana:SOL -> base:USDC`, and28`optimism:USDC -> base:USDC` are explicitly supported examples.29Polygon and Optimism are available to Base and Arbitrum. Ethereum, HyperEVM, X30Layer, Sei, Sonic, Monad, Avalanche, Cronos, Injective, Linea and Aptos are available to Base and Solana. These source-only routes use31the same caller-approved prepare/session boundary. The unversioned32legacy MCP workflow remains limited to two original Solana-origin corridors.3334Do not request an AssetFare quote for an unsupported chain or asset, an identity35route, an amount below $1 or a non-finite amount, or a custodial execution request.36Do not request one merely because a payment wallet is empty when no spendable37source asset is known, or when the wallet is already funded on an accepted38payment rail. A quote is the route recommendation input, but it grants no39wallet access, action preparation, signature, or submission authority.4041## Economic evaluation guidance4243- USD 1 is the shared technical quote minimum, not an economic recommendation.44- Read `economic_guidance` on the quote and the dated research catalog at45 `https://assetfare.dev/route-economics.json`. Sixty-five whole routes are46 offered; 35 research/retire routes are not public products.47- Product inclusion is reviewed weekly. Always obtain a fresh quote; no product48 classification grants signing or submission authority.4950## Interface scope5152- REST/OpenAPI v2: 65 curated public routes across the live endpoints.53- MCP `assetfare_v2_capabilities` and `assetfare_v2_quote`: the same full quote matrix, passing through the `caller_action_plan_handoff`.54- Every quote also carries strict `continuation_v3`: full-quote and route hashes,55 fingerprint claim, exact wallet/signer requirements, path, bounds, TTL, and56 allowed modes. It remains `unranked_candidate` until a separate explicit57 offline `assetfare-select` operation writes `approval_v3` mode 0600.58- MCP caller-approved v2 execution tools cover all 65 offered routes: `assetfare_v2_prepare` (one-shot first unsigned bundle) and the `assetfare_v2_session_create`/`_get`/`_observe_source`/`_observe_output`/`_refresh_action` lifecycle. Remote clients generate the session capability locally from 32 CSPRNG bytes encoded as base64url; the remote adapter never generates that secret. The optional self-hosted stdio adapter additionally exposes `assetfare_v2_new_session_capability` as an offline helper. Each execution tool requires explicit caller approval and the caller's public wallet addresses, is never auto-called from a quote, and rejects private key/seed/signed transaction material. Never mix these with the legacy v1 session tools.59- The packaged delegated `assetfare-agent-runner` supports EVM and Solana handoffs. Aptos routes return a verified Aptos Wallet Standard unsigned-BCS handoff with delegated runner execution disabled; the caller independently confirms, simulates, signs and submits it.60- Unversioned MCP workflow tools: only `solana:SOL -> base:ETH` and `solana:SOL -> arbitrum:ETH`.6162## Safety boundary6364Every v2 quote must include a validated `direct_route_summary`. Show its65ordered provider/from/to steps, normalized chain:asset endpoints, amount bounds,66and AssetFare fee step before recommending the candidate. Treat67`direct_protocol_only` as direct disclosed protocols. No current public route68uses `external_intent`; provider-internal liquidity sourcing may still occur.69`route_aggregator_used=false` describes only AssetFare's engine.7071Validate `continuation_v3` before showing the recommendation. Do not emit72`selection_status=selected`, an idempotency key, or executable approval from a73quote-only evaluation. It remains `unranked_candidate` until the caller makes a74separate explicit execution selection. Multi-step routes allow session only.7576- Never request, transmit, store, or fabricate a private key.77- AssetFare never signs or submits transactions.78- Every live route carries an AssetFare service fee of exactly 1bp, collected at79 one eligible successful atomic action; Circle/provider/network fees are80 additional, so compare the quote's total token-path cost, not the 1bp; reject a quote that reports 0bp or a non-collectible fee.81- The caller verifies every action and uses its own wallet to sign and submit.82- Use the price recommendation as guidance and confirm the fresh fee-inclusive output. When it is false, compare alternatives if price matters; do not add an execution gate.83- Cross-chain routes are sequential and non-atomic.8485## REST/OpenAPI v286871. Read `/v2/capabilities` and `/v2/status`.882. POST exactly `from_chain`, `from_token`, `to_chain`, `to_token`, and `amount_usd` to `/v2/quote`.893. Require a finite amount of at least $1; there is no adapter-enforced maximum.90 Read `economic_guidance.price_recommended_for_amount` as the amount-specific91 recommendation flag. It is never an execution limit.924. Show expected output, minimum output, time, costs, and non-atomic risk. If the93 route is not price-recommended, advise comparison when price matters.945. If explicitly selected, create strict `approval_v3` from the exact unexpired95 quote. Use `/v2/prepare` only for allowed one-shot routes or `/v2/session` for96 receipt-driven progression; never call both.976. Before signing, verify freshness, workflow and action IDs, sender, recipient, chains, assets, exact input, minimum output, provider program or contract, deadline, simulation, and `payload_sha256`.987. Advance only from verified receipts and actual output. Never use an estimated output as the next input.99100The v2 prepare/session fields include `[caller_approved, from_chain, from_token, to_chain, to_token, amount_usd, wallets, event_signer_public, approval_v3]`; session also has `idempotency_key`. Economic guidance adds no request field. `approval_v3` is optional only for the named `legacy_advisory` compatibility path. The caller—not an adapter—must supply literal `caller_approved:true`, which is not proof of human approval. `wallets` must exactly match `continuation_v3.required_wallet_chains`; the event signer must exactly match its boolean requirement. For Solana-CCTP only, generate a fresh ephemeral Solana keypair locally, send its public key, and retain its private key client-side. A session uses a caller-generated >=256-bit url-safe capability in `X-AssetFare-Session-Token`; raw tokens never belong in logs or structured output. Persist one only to an explicit new mode-0600 file. The server stores only its hash. Retain transaction hashes for recovery.101102## Optional original-corridor MCP flow1031041. Read `assetfare_manifest` and `assetfare_status`.1052. Call `assetfare_quote` with a finite whole-dollar amount of at least $1 and `destination_chain` set to `base` or `arbitrum`.106 Treat $1 as reachability/schema smoke only; SOL input includes a swap, and107 $1,000 is the primary representative evaluation amount.1083. At or above the route's best-from amount, use AssetFare first and confirm109 the fresh fee-inclusive output before any separate execution selection.1104. Require caller approval before `assetfare_start_wallet_auth`, session creation, or action preparation.1115. The wallet owner signs only the exact non-transactional login message.1126. Keep the returned access token out of source, logs, issues, and transcripts.1137. Verify every `agent_must_verify` item before the caller signs an unsigned action.114115After any delay or error, read the workflow state and current asset location. Never guess, silently rebuild, or resend a stale action.