SolProbe: POST /exit/cross-check
Can a Base/Arbitrum/Optimism/Polygon/Ethereum agent exit this Solana token back to USDC on its OWN chain — and at what all-in cost? Extends sol_exit_check with a quote-only Li.Fi bridge leg: the full Solana-side exit (sellable, expected USDC, price impact, blockers) plus a bridge block (route, cost %, est. duration) and a composite net_home_output_usdc / all_in_cost_pct. Nothing is signed — it prices the round trip so a non-Solana agent knows the true cost before acting.
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://api.solprobe.xyz/exit/cross-check", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"type": "http",
"method": "POST",
"bodyType": "json",
"bodyFieldNames": [
"home_chain",
"size_usdc",
"token_address"
],
"pathParamNames": [],
"queryParamNames": []
}),
});
console.log(response.status);
console.log(Object.fromEntries(response.headers));
console.log((await response.text()).slice(0, 1000));
// A valid 402 is a quote, not a completed paid call.Review the provider input schema before running this non-read-only method. No payment code is included.
- Exact route checked
not safely testable · potentially-mutating-method:POST
- Origin reachable
HEAD https://api.solprobe.xyz/ returned 200.
- Observed in cdp-bazaar
The registry record was observed and retained with provenance.
EVIDENCE
Each record has an exact-route quote outcome. Unresolved templates and potentially mutating methods are labeled instead of being invoked without provider-specific test input. A quote is still separate from a settled paid call.