/evm-atlas

Layerswap Bridging

Overview

Use Layerswap as a read-only source for cross-chain swap quotes, transfer limits, supported networks/tokens, and swap status lookups by transaction hash, swap ID, or wallet address.

Default to the API base URL:

https://api.layerswap.io

Most Layerswap API calls work without an API key at lower rate limits. Add the key only when present:

-H "X-LS-APIKEY: $LAYERSWAP_API_KEY"

Never execute bridge steps from this skill. Do not sign messages, submit deposit transactions, call POST /api/v2/swaps or any gasless/deposit-action endpoint to create a swap, or broadcast a returned deposit address as a transaction target. Returned swap, quote, and deposit data are for inspection only.

Layerswap identifies networks by its own name strings (e.g. ETHEREUM_MAINNET, ARBITRUM_MAINNET), not by references/generated/target-mainnets.json's chainName. Call GET /api/v2/networks to resolve a Layerswap name to its chain_id, then match against references/generated/target-mainnets.json's numeric chainId. Layerswap returns chain_id as a JSON string (e.g. "1", "42161") — cast before comparing. Treat /networks as the live authoritative source; do not hardcode a name-to-chain-ID table.

Layerswap settles some transfers through shared service infrastructure rather than a per-user deposit address. The Ethereum address 0x2Fc617E933a52713247CE25730f6695920B3befe is Etherscan-labeled "Layerswap 1", a shared service address, not a specific user's deposit address. Do not attribute a transfer to a specific user solely because it touches this address; confirm the actual swap and counterparties via GET /api/v2/swaps/by_transaction_hash/{hash} or GET /api/v2/swaps?address=.

Read-Only Router

Use this router after the known origin and destination chains are confirmed against references/generated/target-mainnets.json.

1. Known source tx hash: call GET /api/v2/swaps/by_transaction_hash/{transactionHash}. The most useful lookup — connects a known source-chain transaction to its Layerswap swap and destination outcome.
2. Known swap ID: call GET /api/v2/swaps/{swapId} when a UUID swap ID is known, e.g. from a Layerswap explorer link.
3. Known sender/recipient address, no tx hash: call GET /api/v2/swaps?address=<address>; narrow with statuses, networks, or page.
4. Quote / fee estimate: call GET /api/v2/quote with source_network, source_token, destination_network, destination_token, and amount (all required).
5. Min/max transfer limits: call GET /api/v2/limits with the same four required network/token params.
6. Available source routes into a destination: call GET /api/v2/sources with destination_network and destination_token.
7. Supported networks and tokens: call GET /api/v2/networks; add network_types=evm to scope to EVM chains.

Example tx-hash lookup:

curl -sS "https://api.layerswap.io/api/v2/swaps/by_transaction_hash/0xTX_HASH"

Example quote inspection:

curl -sS "https://api.layerswap.io/api/v2/quote?source_network=ETHEREUM_MAINNET&source_token=USDC&destination_network=ARBITRUM_MAINNET&destination_token=USDC&amount=100"

If $LAYERSWAP_API_KEY is set, add -H "X-LS-APIKEY: $LAYERSWAP_API_KEY".

Request Fields

Do not invent wallet addresses. Use placeholders for hypothetical quotes and user-provided addresses for real lookups.

Report Fields

Extract and report these fields when present:

Unlike other bridge references in this skill, Layerswap amounts are already decimal, human-readable values scaled by the token's decimals — do not divide by 10^decimals again. chain_id fields are JSON strings, not numbers; cast before comparing to references/generated/target-mainnets.json.

Status Values

Interpret the swap.status field as:

Layerswap's refunds documentation additionally describes pending_refund and refunded states for retry-exhausted swaps with a refund_address — refunds are always sent on the source chain in the source token, minus gas. These do not appear in the core swap.status enum above; treat them as real but verify via data.swap.transactions[] entries with type: "refund" rather than assuming the exact status string. Separately, the GET /api/v2/swaps list endpoint's statuses filter uses a third, differently-cased vocabulary (PendingDeposit, Completed, Failed, Expired, PendingWithdrawal, PendingRefund, Refunded) — treat it as a distinct filter vocabulary, not a direct casing-only mapping of the values above.

For completed or a refund outcome, still verify the terminal destination or refund transfer with explorer or RPC data when the relevant chain is a target chain.

Failure Handling

• Missing $LAYERSWAP_API_KEY: use unauthenticated requests and respect lower public rate limits.
• Rate limit 429 or 5xx: back off, mention the limit, and continue explorer/RPC analysis.
• Empty /quote, /limits, or /sources result: report the API's error field when present; try only user-approved alternative tokens, chains, or amounts.
• Unknown swap ID or tx hash (empty data): report that Layerswap has no record and continue normal explorer/RPC analysis.
• Non-target chains in Layerswap results: report that the leg is outside this skill and ask for a feature request rather than continuing analysis on that leg.
• A transfer touching 0x2Fc617E933a52713247CE25730f6695920B3befe alone is not proof of attribution to a specific user; confirm via the swap-lookup endpoints.

Sources

• https://learn.layerswap.io/api/overview
• https://learn.layerswap.io/api/api-integration/quickstart
• https://learn.layerswap.io/api/api-integration/swap-lifecycle
• https://learn.layerswap.io/api/data/object-types
• https://docs.layerswap.io/api-reference/swaps/get-quote
• https://docs.layerswap.io/api-reference/swaps/get-swap-route-limits
• https://docs.layerswap.io/api-reference/swaps/get-sources
• https://docs.layerswap.io/api-reference/swaps/get-swap-details
• https://docs.layerswap.io/api-reference/swaps/get-swap-by-transaction-hash
• https://docs.layerswap.io/api-reference/swaps/get-all-swaps
• https://docs.layerswap.io/api-reference/swaps/get-networks