Taskbond
NEAR Intents

Fund a job from any chain.

Posters shouldn’t need to bridge. The quote below is live from NEAR Intents’ 1Click API, using its real token list. It is a dry quote: Taskbond’s escrow is on testnet, and Intents runs only on mainnet, so no deposit address is requested and nothing moves.

⇄
Fund this job from any chain
NEAR Intents · 1Click API · live mainnet quotes
Dry quote · nothing settles

Quote asks the solver network for the exact 0.13 wNEAR output, so a poster on any chain knows what to send. Refunds route back to the same Intents account.

Live solver quote
Why dry? NEAR Intents runs on mainnet only and the escrow lives on testnet, so Taskbond prices the route live but never requests a deposit address. A real settlement would set dry:false, send the quoted amount to the issued deposit address, and poll /v0/status until SUCCESS.
01
Pick what you hold

Any of the assets NEAR Intents supports: USDC on Base, SOL, BTC, ETH, USDT on Tron and many more.

02
Live exact-output quote

Taskbond asks the 1Click solver network what you must send so exactly the job reward arrives as wNEAR.

03
Deposit (mainnet only)

On mainnet, 1Click issues a one-time deposit address. You send once; solvers fill the swap in seconds.

04
Escrow funded

wNEAR lands in the poster's Intents account and funds create_job. Refunds route back automatically if the swap fails.

What a real settlement would need
  • Escrow deployed on NEAR mainnet (the testnet contract cannot receive mainnet wNEAR).
  • A quote with dry: false, a real refund address, and the poster sending the quoted amount to the returned deposit address.
  • Polling GET /v0/status?depositAddress=… until SUCCESS, then ft_transfer_call of wNEAR into the escrow (or unwrap and attach NEAR).
  • Smallest practical test: about 1–2 USDC from Base or Arbitrum, above the solver’s minimum.