@oobe-protocol-labs/sap-mcp-server 0.9.22 → 0.9.36

package/skills/sap-defi/SKILL.md

@@ -1,8 +1,8 @@
 # SAP DeFi
 
-Use this skill for Jupiter swaps, DCA, limit orders, Drift, Adrena, Lulo,
-Raydium, Orca, Meteora, OpenBook, Manifest, Pump.fun, Jito, bridges, and
-staking protocols.
+Use this skill for Jupiter swaps, DCA, limit orders, perps planning, chart
+analysis, Lulo, Raydium, Orca, Meteora, OpenBook, Manifest, Pump.fun, Jito,
+bridges, and staking protocols.
 
 ## Jupiter
 
@@ -24,8 +24,14 @@ staking protocols.
 
 ## Protocol Tools
 
-- `drift_*`
-- `adrena_*`
+- `sap_perp_trade_plan`
+- `sap_perp_markets`
+- `sap_perp_position_info`
+- `sap_perp_funding_history`
+- `sap_perp_liquidation_zones`
+- `sap_chart_ohlc`
+- `sap_chart_long_term`
+- `sap_chart_volume_profile`
 - `lulo_*`
 - `raydium-pools_*`
 - `orca_*`
@@ -52,6 +58,37 @@ staking protocols.
    use `sap_preview_transaction`, `sap_sign_transaction`, and
    `sap_submit_signed_transaction`. Do not write ad-hoc signing scripts.
 
+## Professional Perps Flow
+
+For perps or leveraged trading tasks, start with hosted SAP analytics and
+planning tools before any value-moving action:
+
+1. Call `sap_perp_markets` to inspect supported markets, mark prices, funding,
+   and open interest.
+2. Call `sap_perp_position_info` when the user has an existing wallet position.
+3. Call `sap_chart_ohlc`, `sap_chart_long_term`, or
+   `sap_chart_volume_profile` for trend, timeframe, and liquidity context.
+4. Call `sap_perp_liquidation_zones` to understand liquidation distance and
+   crowded-risk areas.
+5. Call `sap_perp_trade_plan` with market, side, collateral amount, leverage,
+   entry price, stop loss, take profit, max slippage, and max account-risk
+   policy.
+
+`sap_perp_trade_plan` is analysis-only. It returns trader-grade risk flags,
+liquidation estimate, reward/risk, and an execution checklist. `sap_perp_markets`
+may return `dataAvailability.status="unavailable"` when the configured RPC does
+not serve the required perps account indexes; treat that as missing data, not as
+proof that markets do not exist. Do not create temporary signing scripts, do not
+guess perps account graphs, and do not execute a perps transaction unless SAP MCP
+exposes a typed unsigned builder or a local SAP payments/signing tool for that
+exact action.
+
+Direct Adrena signer tools may exist in some local AgentKit builds, but hosted
+SAP MCP blocks them before x402 payment because the hosted server is
+accountless. Do not route `adrena_openPosition`, `adrena_closePosition`, or
+collateral-changing Adrena calls through `sap_payments_call_paid_tool`; there is
+no payment challenge and no unsigned transaction to finalize.
+
 ## Safety
 
 DeFi execution can lose funds through slippage, MEV, wrong decimals, or bad

package/skills/sap-discovery-indexing/SKILL.md

@@ -18,7 +18,7 @@ indexes, and filtered agent discovery.
 
 ## Rules
 
-- Start with free orientation when possible:
+- Start with low-cost micro-read orientation when possible:
   - `sap_agent_context` for a one-shot compact context read and routing hints.
   - `sap_get_agent` or `sap_get_agent_profile` for a known owner wallet.
   - `sap_is_agent_active` for a known owner wallet status check.
@@ -31,8 +31,9 @@ indexes, and filtered agent discovery.
 - Use `sap_list_all_agents` for global directory requests or when the user asks
   for the whole SAP ecosystem. Keep the first page small and follow
   `pagination.nextCursor` only when the previous page is useful.
-- Use paid discovery only when the user needs search, enrichment, full rows,
-  large pages, analytics, or global enumeration beyond the free compact page.
+- Use read-premium discovery only when the user needs search, enrichment, full
+  rows, large pages, analytics, or global enumeration beyond the compact
+  micro-read page.
 - Prefer exact filters before broad scans: `wallet` when a wallet is known,
   `query` for an agent name such as `XONA`, and `capability` for one exact
   capability such as `creative:imageGeneration`.

package/skills/sap-market-data/SKILL.md

@@ -24,11 +24,15 @@ trending assets, token metadata, and security/intelligence checks.
 
 ## Flow
 
-1. Resolve token mints with `jupiter_searchTokens` when the user gives only a
-   ticker.
-2. Use Pyth for oracle-style price feeds.
-3. Use CoinGecko for market data, OHLCV, pools, trending, gainers, and losers.
-4. Use `jupiter_shield` and `jupiter_getTokenInfo` for token risk context.
+1. If the mint/feed id is already known, start with free single-asset snapshots:
+   `jupiter_getPrice`, `pyth_getPrice`, or `coingecko_getTokenPrice`.
+2. Resolve token mints with `jupiter_searchTokens` only when the user gives
+   a ticker or ambiguous asset name; this is broader discovery and may be paid.
+3. Use `jupiter_getQuote` for executable route pricing, not as a generic price
+   check. Quotes are fresh, paid, and must not be cached as truth.
+4. Use Pyth history, CoinGecko OHLCV/pools/trending/gainers/losers, and Jupiter
+   token lists only when the user needs broader market context.
+5. Use `jupiter_shield` and `jupiter_getTokenInfo` for token risk context.
 
 ## Safety
 

package/skills/sap-mcp/SKILL.md

@@ -9,6 +9,7 @@ safe signing behavior.
 If the user says "Start SAP MCP", "Initialize SAP MCP", "Load SAP", or "SAP
 mode", treat it as the activation command. Call `sap_agent_start` when it is
 available, then call `sap_agent_runtime_status` with the closest intent and
+`sap_prepare_action` when the request is more than a status check. Then call
 `sap_skills_bundle` with `includeContents: true`. Load the returned SAP MCP
 skill contents into context before selecting advanced tools.
 
@@ -22,18 +23,19 @@ Always inspect runtime context through MCP tools, not by reading config files:
 
 1. `sap_agent_start`
 2. `sap_agent_runtime_status` with `intent: "connection"`, `"paid-call"`, `"registry-write"`, `"transaction-finalize"`, `"escrow"`, `"identity"`, or `"general"`
-3. `sap_agent_context` for free compact agent/directory orientation before paid discovery
-4. `sap_skills_bundle` with `includeContents: true`
-5. `sap_pricing_catalog` before estimating hosted paid call tiers
-6. `sap_agent_next_action` before retrying after any SAP MCP error or partial write result
-7. `sap_skills_upgrade_plan` when local skills are missing or stale
-8. `sap_runtime_repair_plan` when hosted tools are connected but `sap_payments` is missing
-9. `sap_protocol_invariants` before SAP registry writes or when treasury, protocol fee, hosted write routing, or local signer routing is unclear
-10. `sap_agent_identity_plan` before agent registration, profile-image updates, Metaplex identity, SNS linking, or full identity setup
-11. `sap_profile_current`
-12. `sap_profile_list`
-13. `sap_profile_public_key`
-14. `sap_network_stats`
+3. `sap_prepare_action` with the closest intent before paid calls, swaps, registry writes, identity updates, Escrow V2, external x402 agents, premium streams, or transaction finalization
+4. `sap_agent_context` for compact micro-read agent/directory orientation before broad discovery
+5. `sap_skills_bundle` with `includeContents: true`
+6. `sap_pricing_catalog` before estimating hosted paid call tiers
+7. `sap_agent_next_action` before retrying after any SAP MCP error or partial write result
+8. `sap_skills_upgrade_plan` when local skills are missing or stale
+9. `sap_runtime_repair_plan` when hosted tools are connected but `sap_payments` is missing
+10. `sap_protocol_invariants` before SAP registry writes or when treasury, protocol fee, hosted write routing, or local signer routing is unclear
+11. `sap_agent_identity_plan` before agent registration, profile-image updates, Metaplex identity, SNS linking, or full identity setup
+12. `sap_profile_current`
+13. `sap_profile_list`
+14. `sap_profile_public_key`
+15. `sap_network_stats`
 
 For simple "are you connected?" checks, do not dump tool counts or inspect
 local files. Use `sap_agent_runtime_status` first and answer with the hosted
@@ -57,8 +59,14 @@ and error strings unchanged.
   agent profile reads as fresh data. Do not rely on old chat memory when the
   user asks for current state; use exact lightweight reads first, then paid
   discovery only when enrichment or broad search is needed.
-- Use free exact/base reads first when the wallet, PDA, or a small orientation
-  page is enough: `sap_agent_context`, `sap_get_agent`, `sap_get_agent_profile`,
+- Treat session memory as operational context and proof tape, not cached market
+  or on-chain truth. It may store active profile names, public wallet keys,
+  runtime namespace availability, receipts, signatures, and error
+  classifications. It must not be used as truth for token prices, Jupiter
+  quotes/orders, balances, blockhashes, simulations, liquidity, routes, or SAP
+  account state.
+- Use low-cost exact/base micro-reads first when the wallet, PDA, or a small
+  orientation page is enough: `sap_agent_context`, `sap_get_agent`, `sap_get_agent_profile`,
   `sap_get_agent_stats`, `sap_is_agent_active`, `sap_get_global_state`, and
   `sap_list_agents` with `limit <= 20`, `view: "compact"`, and
   `includeProtocolIndexes: false`.
@@ -69,9 +77,9 @@ and error strings unchanged.
 - Use `sap_list_all_agents` when the user asks for all current SAP ecosystem
   agents. It performs global on-chain `AgentAccount` enumeration and returns
   `pagination.nextCursor` when more pages are available.
-- Use `sap_list_agents` for a free compact orientation page first. Larger
+- Use `sap_list_agents` for a compact micro-read orientation page first. Larger
   pages, `view: "full"`, hydration, protocol index summaries, and global scans
-  are paid read-premium.
+  are read-premium.
 - Use `sap_fetch_protocol_index` when a specific protocol ID is known.
 - If a capability lookup returns zero results, retry with `query` or `wallet`
   before saying an agent is absent. AgentAccount rows are canonical; indexes can
@@ -100,7 +108,7 @@ Use the bundled routing map for local MCP tool selection:
 
 SAP MCP startup and skill bootstrap tools are free context/setup tools. Call
 `sap_agent_start`, `sap_agent_runtime_status`, `sap_agent_context`,
-`sap_agent_next_action`, `sap_pricing_catalog`,
+`sap_prepare_action`, `sap_agent_next_action`, `sap_pricing_catalog`,
 `sap_skills_list`, `sap_skills_bundle`, `sap_skills_upgrade_plan`,
 `sap_runtime_repair_plan`, and local `sap_skills_install` directly. Do not
 route startup, runtime status, pricing catalog, skill listing, bundling,
@@ -184,13 +192,15 @@ the local `sap_payments.sap_payments_readiness` bridge when it is configured.
 Use `sap_payments.sap_payments_profile_current` only as a narrower compatibility
 profile check.
 
-Basic wallet reads are free on hosted SAP MCP. Call `sol_get_balance`,
-`spl-token_getBalance`, `spl-token_getTokenAccounts`, and `magicblock_balance`
-directly on the hosted server. Do not send these balance checks through
-`sap_payments_call_paid_tool`, and do not summarize a balance read as a
-facilitator `BlockhashNotFound` problem unless a paid tool actually returned
-that error. Use `jupiter_getHoldings` only when the user needs enriched paid
-portfolio context.
+Basic wallet and price-readiness checks are free hosted reads. Call
+`sol_get_balance`, `spl-token_getBalance`, `spl-token_getTokenAccounts`,
+`sap_x402_get_balance`, `magicblock_balance`, `jupiter_getPrice`,
+`pyth_getPrice`, and `coingecko_getTokenPrice` directly on the hosted server
+when the user needs fresh readiness data. Do not send these checks through
+`sap_payments_call_paid_tool`, and do not summarize a readiness read as a
+facilitator `BlockhashNotFound` problem unless a paid x402 tool actually
+returned that error. Use `jupiter_getHoldings` only when the user needs enriched
+read-premium portfolio context.
 
 Before any paid tool call, use `sap_estimate_tool_cost` with the tool name to
 get the exact pricing tier, estimated USD cost, and recommended `maxPriceUsd`.
@@ -198,6 +208,9 @@ This prevents silent cap aborts and failed x402 attempts on local-signer-only
 tools. For local-signer-only tools (e.g. `sap_register_agent`), the estimate
 will say `tier: "local-signer-only"` and tell you to use the local
 `sap_payments_*` equivalent instead of `sap_payments_call_paid_tool`.
+For any intent-level workflow, call `sap_prepare_action` before execution. It
+returns the correct hosted/local route, fresh-data requirements, confirmation
+policy, retry rules, and proof-tape shape without charging x402.
 
 If a hosted paid tool returns `BlockhashNotFound`,
 `transaction_simulation_failed`, `smart_wallet_simulation_failed`, `node is

package/skills/sap-mcp/TOOL_REFERENCE.md

@@ -49,7 +49,7 @@ SAP registry and discovery:
 `sap_deactivate_tool`, `sap_reactivate_tool`,
 `sap_report_tool_invocations`, `sap_report_calls`.
 
-Use free exact/base reads before paid discovery when possible:
+Use low-cost exact/base micro-reads before broad discovery when possible:
 `sap_agent_context`, `sap_get_agent`, `sap_get_agent_profile`,
 `sap_get_agent_stats`, `sap_is_agent_active`, `sap_get_global_state`, and
 `sap_list_agents` with `limit <= 20`, `view: "compact"`, and
@@ -174,13 +174,9 @@ Jupiter protocol toolkit:
 `jupiter_getLimitOrders`, `jupiter_createDCA`, `jupiter_executeDCA`,
 `jupiter_cancelDCA`, `jupiter_getDCAOrders`, `jupiter_smartSwap`.
 
-`adrena_addCollateral`, `adrena_closePosition`, `adrena_getPositions`,
-`adrena_openPosition`, `adrena_removeCollateral`,
 `bridging_bridgeDeBridge`, `bridging_bridgeDeBridgeStatus`,
 `bridging_bridgeWormhole`, `bridging_bridgeWormholeStatus`,
-`drift_borrow`, `drift_closePerpPosition`, `drift_deposit`,
-`drift_getPositions`, `drift_lend`, `drift_openPerpPosition`,
-`drift_withdraw`, `jito_getBundleStatus`, `jito_getTipEstimate`,
+`jito_getBundleStatus`, `jito_getTipEstimate`,
 `jito_sendBundle`, `lulo_deposit`, `lulo_getBestRates`,
 `lulo_getPositions`, `lulo_withdraw`, `manifest_cancelOrder`,
 `manifest_createMarket`, `manifest_getOrderbook`,
@@ -201,7 +197,7 @@ Protocol routing shortcuts:
 
 | User intent | Most specific tools |
 | --- | --- |
-| SOL or SPL balance (free) | `sol_get_balance`, `spl-token_getBalance`, `spl-token_getTokenAccounts`, `magicblock_balance` |
+| SOL or SPL balance (micro-read) | `sol_get_balance`, `spl-token_getBalance`, `spl-token_getTokenAccounts`, `magicblock_balance` |
 | Enriched holdings (paid read-premium) | `jupiter_getHoldings` |
 | Pre-call cost estimate (free) | `sap_estimate_tool_cost` |
 | Pricing catalog (free) | `sap_pricing_catalog` |
@@ -209,7 +205,7 @@ Protocol routing shortcuts:
 | Token launch/mint/burn | `spl-token_deployToken`, `spl-token_mintTo`, `spl-token_burn` |
 | Jupiter quote/swap | `jupiter_getQuote`, `jupiter_smartSwap`, `jupiter_swap`, `jupiter_swapInstructions` |
 | Jupiter limit/DCA | `jupiter_createLimitOrder`, `jupiter_getLimitOrders`, `jupiter_createDCA`, `jupiter_getDCAOrders` |
-| Perps/lending | `drift_*`, `adrena_*`, `lulo_*` |
+| Perps/lending | `sap_perp_trade_plan`, `sap_perp_*`, `sap_chart_*`, `lulo_*` |
 | Liquidity pools | `raydium-pools_*`, `orca_*`, `meteora_*` |
 | Orderbooks | `openbook_*`, `manifest_*` |
 | Price data | `pyth_*`, `coingecko_*` |
@@ -223,3 +219,8 @@ Social, Blinks, bounties, gaming:
 `blinks_getAction`, `blinks_resolveBlinkUrl`, `blinks_validateActionsJson`,
 `gibwork_createBounty`, `gibwork_listBounties`, `gibwork_submitWork`,
 `send-arcade_listGames`, `send-arcade_playGame`.
+
+Perps note: SAP MCP hosted supports perps analytics and trader-grade planning,
+not direct hosted Adrena execution. If direct Adrena signer tools are visible in
+a local runtime, use them only with that local runtime's signer path and policy.
+Do not route direct Adrena writes through hosted x402 paid-call replay.

package/skills/sap-operations/SKILL.md

@@ -36,12 +36,13 @@ Use `sap_discover_agents` for targeted hosted directory reads by `query`,
 `wallet`, `agentPda`, `protocol`, `capability`, `capabilities`, or
 `hasX402Endpoint`. Use `sap_list_all_agents` for global current ecosystem
 requests, keep pages small, and continue with `pagination.nextCursor`.
-For first-pass orientation, prefer free reads: `sap_agent_context`,
+For first-pass orientation, prefer free control-plane tools, then low-cost
+micro-read exact/base reads: `sap_agent_context`,
 `sap_get_agent`, `sap_get_agent_profile`, `sap_get_agent_stats`,
 `sap_is_agent_active`, `sap_get_global_state`, and `sap_list_agents` with `limit <= 20`,
-`view: "compact"`, and `includeProtocolIndexes: false`. Use paid discovery
-only when the user needs search, enrichment, full rows, large pages, analytics,
-or global enumeration beyond the compact page.
+`view: "compact"`, and `includeProtocolIndexes: false`. Use read-premium
+discovery only when the user needs search, enrichment, full rows, large pages,
+analytics, or global enumeration beyond the compact page.
 
 Before registering or updating an agent profile, call free
 `sap_protocol_invariants` when treasury, registration fee, hosted write route,

package/skills/sap-payments-x402/SKILL.md

@@ -16,6 +16,7 @@ workflows, and hosted SAP MCP x402/pay.sh monetization.
 - `sap_payments_prepare_challenge`
 - `sap_payments_sign_challenge`
 - `sap_payments_verify_receipt`
+- `sap_prepare_action`
 - `sap_x402_paid_call`
 - `sap_create_subscription`
 - `sap_fund_subscription`
@@ -44,18 +45,19 @@ the non-custodial model: OOBE does not hold user keys. Paid and value-moving
 hosted calls still proceed through x402/pay.sh plus the user's local SAP profile
 or external signer.
 
-- Free: `tools/list`, `prompts/list`, `resources/list`, `sap_profile_current`,
-  `sap_agent_start`, `sap_agent_runtime_status`, `sap_agent_context`,
+- Free: MCP handshake, `tools/list`, `prompts/list`, `resources/list`,
+  `sap_profile_current`, `sap_agent_start`, `sap_agent_runtime_status`,
   `sap_agent_next_action`, `sap_estimate_tool_cost`, `sap_pricing_catalog`,
-  exact SAP agent/profile reads, compact `sap_list_agents` pages with
-  `limit <= 20`, `sap_get_network_overview`, core balance checks
-  (`sol_get_balance`, `spl-token_getBalance`, `spl-token_getTokenAccounts`,
-  `spl-token_getMint`, `spl-token_getSupply`, `magicblock_balance`,
-  `sap_x402_get_balance`). Enriched holdings such as `jupiter_getHoldings`
-  are paid read-premium.
+  repair/status tools, local payment bridge control, transaction
+  preview/finalization helpers, SOL/SPL/x402 balance readiness, single-asset
+  price snapshots, and memory/audit helpers.
+- Micro read: exact SAP agent/profile reads, compact `sap_list_agents` pages
+  with `limit <= 20`, `sap_get_network_overview`, SNS availability, escrow
+  state, and lightweight trader/perps context.
 - Read premium: `sap_discover_agents`, `sap_list_all_agents`, full/enriched or
-  large `sap_list_agents` pages, indexed discovery, network stats,
-  protocol/capability indexes.
+  large `sap_list_agents` pages, enriched holdings, indexed discovery, network
+  stats, protocol/capability indexes, DAS, token lists, quotes/routes, and
+  OHLCV/history.
 - Builder: batch SNS/domain checks, analytics, transaction builders.
 - Value action: fixed fee plus configured basis-points fee when public USD
   notional fields are present.
@@ -70,6 +72,15 @@ Before retrying `payment_required`, `hosted_local_signer_required`,
 signature, call `sap_agent_next_action`. Use its `safeToRetryNow`, `nextTool`,
 and `paymentCharged` fields as the retry guard.
 
+Before starting a paid or value-moving workflow, call the free hosted
+`sap_prepare_action` planner with the closest intent. It returns:
+
+- fresh data that must be fetched again before payment/signing;
+- whether to use hosted `sap`, local `sap_payments`, or a hosted unsigned
+  builder plus `sap_payments_finalize_transaction`;
+- max-price and confirmation guidance;
+- retry rules and the proof-tape fields to report back to the user.
+
 For fast x402 execution:
 
 1. Reuse the MCP session returned by `initialize`.
@@ -78,20 +89,24 @@ For fast x402 execution:
 3. Use `PAYMENT-SIGNATURE` first; use `X-PAYMENT` only for clients that require
    the alternate header.
 4. Cache only static MCP surface metadata such as `tools/list`, `prompts/list`,
-   and `resources/list` inside the runtime when useful. Do not cache on-chain
-   balances, SAP agent rows, pricing, SNS ownership, quotes, or settlement
-   state when the user expects fresh data.
+   and `resources/list` inside the runtime when useful. Session memory can
+   store operational context, receipts, signatures, and error classifications.
+   Do not cache on-chain balances, SAP agent rows, pricing, SNS ownership,
+   quotes, blockhashes, simulations, liquidity, routes, or settlement state
+   when the user expects fresh data.
 5. Treat `PAYMENT-RESPONSE` as the receipt bound to the tool output.
 6. If the client runtime cannot sign or attach x402 payment headers itself, use
    the local SAP MCP `sap_payments_call_paid_tool` bridge configured by the SAP
    MCP wizard instead of falling back to local stdio automatically.
 
-Do not use x402 for core balance reads. `sol_get_balance`,
-`spl-token_getBalance`, `spl-token_getTokenAccounts`, `magicblock_balance`,
-and `sap_x402_get_balance` are free hosted tools and should be called directly
-through the remote SAP MCP connection. Use `jupiter_getHoldings` only when the
-user needs enriched paid portfolio context. Always verify USDC and SOL balances
-before attempting paid calls — an agent without USDC cannot make paid calls.
+Do not use x402 for core balance or single-asset price readiness reads.
+`sol_get_balance`, `spl-token_getBalance`, `spl-token_getTokenAccounts`,
+`magicblock_balance`, `sap_x402_get_balance`, `jupiter_getPrice`,
+`pyth_getPrice`, and `coingecko_getTokenPrice` are free hosted tools and should
+be called directly through the remote SAP MCP connection. Use
+`jupiter_getHoldings` only when the user needs enriched paid portfolio context.
+Always verify USDC and SOL balances before attempting paid calls — an agent
+without USDC cannot make paid calls.
 
 Before any paid tool call, use `sap_estimate_tool_cost` with the tool name to
 get the exact tier, estimated USD cost, and recommended `maxPriceUsd`. This

package/assets/logos/drift.svg

@@ -1,12 +0,0 @@
-<svg width="256" height="256" viewBox="0 0 256 256" fill="none" xmlns="http://www.w3.org/2000/svg">
-<path d="M0 64C0 28.6538 28.6538 0 64 0H192C227.346 0 256 28.6538 256 64V192C256 227.346 227.346 256 192 256H64C28.6538 256 0 227.346 0 192V64Z" fill="#08AA18"/>
-<g clip-path="url(#clip0_354_3823)">
-<path d="M32 62.9677C32 45.8647 45.8647 32 62.9677 32H193.032C210.135 32 224 45.8647 224 62.9677V193.032C224 210.135 210.135 224 193.032 224H62.9677C45.8647 224 32 210.135 32 193.032V62.9677Z" fill="#08AA18"/>
-<path d="M105.764 71.4325C105.367 72.4792 106.14 73.599 107.259 73.5993H129.162C130.199 73.5993 130.962 74.5712 130.717 75.5786L116.825 132.535C116.424 134.18 118.518 135.239 119.606 133.941L169.692 74.1724C169.996 73.8097 170.446 73.5993 170.919 73.5993H203.043C204.411 73.5993 205.148 75.2066 204.256 76.2439L77.1854 224H65.261L92.329 110.773C92.5694 109.767 91.8069 108.8 90.7731 108.799H52.9722C51.6232 108.799 50.8805 107.233 51.7338 106.188L112.32 32H120.719L105.764 71.4325Z" fill="white"/>
-</g>
-<defs>
-<clipPath id="clip0_354_3823">
-<rect width="192" height="192" fill="white" transform="translate(32 32)"/>
-</clipPath>
-</defs>
-</svg>