Tidepool: a 1Click-compatible testnet sandbox for NEAR Intents
- privacieOP
The problem
NEAR Intents and the 1Click API are great to build on, but there’s no testnet. Testing an integration (quotes, deposits, status polling, refunds) means using real mainnet funds. This keeps coming up in Discord.
What I built
Tidepool is a community-built, 1Click-compatible sandbox on NEAR testnet. It’s live and free to use: www.usetidepool.tech
- Same API as 1Click.
/v0/tokens,/v0/quote,/v0/deposit/submitand/v0/status, with the same fields. The official 1Click TypeScript SDK works by changing one line (OpenAPI.BASE). - Real on-chain settlement. Swaps settle through a deployment of the official, unmodified Intents verifier (v0.4.2) on testnet. A maker bot fills quotes, and a test swap goes from deposit to SUCCESS in about 7 seconds.
- Failure paths like mainnet. Partial deposits, expired quotes and overpays are refunded correctly, with the matching statuses and refund reasons. There’s a guide with real testnet transactions: www.usetidepool.tech/docs/guides/failure-cases
- Test-token faucet. USDC, USDT, wNEAR, wBTC, ETH and XAUT.
- Docs AI agents can read. llms.txt, copy as Markdown, and open in ChatGPT/Claude: www.usetidepool.tech/docs
The workflow it enables
Build and test your full integration on Tidepool for free. Then point the SDK at mainnet 1Click and do one final run with small amounts.
What’s next
Based on community feedback, the roadmap includes app fees, ANY_INPUT, memo deposits and test bridges from Base Sepolia and Ethereum Sepolia: www.usetidepool.tech/docs/resources/roadmap
Tidepool is community-built and not affiliated with NEAR. I’d love feedback from builders and the Intents team: what’s missing, what breaks, and whether this is useful enough to support long term.
- Same API as 1Click.