Skip to content

internet-court/internet-court-skill / vendored/near/near-intents

near-intents

Verified

Cross-chain token swap integration using NEAR Intents 1Click API. Use when building swap widgets, bridge interfaces, or multi-chain transfers across EVM, Solana, NEAR, TON, Stellar, and Tron.

FileKindSize
LICENSEother329 B
SKILL.mdskill md3.7 KB
references/concepts.mdmarkdown2.1 KB
rules/api-any-input-withdrawals.mdmarkdown2.1 KB
rules/api-deposit-submit.mdmarkdown1.4 KB
rules/api-quote.mdmarkdown8.3 KB
rules/api-status.mdmarkdown2.0 KB
rules/api-tokens.mdmarkdown1.2 KB
rules/deposit-evm.mdmarkdown847 B
rules/deposit-near.mdmarkdown1.6 KB
rules/deposit-solana.mdmarkdown1.7 KB
rules/deposit-stellar.mdmarkdown1.6 KB
rules/deposit-ton.mdmarkdown1.5 KB
rules/deposit-tron.mdmarkdown1.0 KB
rules/intents-balance.mdmarkdown1.9 KB
rules/passive-deposit.mdmarkdown1.5 KB
rules/react-hooks.mdmarkdown3.8 KB
rules/react-swap-widget.mdmarkdown14.2 KB
rules/server-example.mdmarkdown9.1 KB

references/concepts.md

View on GitHub
# 1Click API Concepts

## How It Works

1Click simplifies NEAR Intents by temporarily transferring assets to a trusted swapping agent that coordinates with Market Makers to execute your intent. The REST API abstracts intent creation, solver coordination, and transaction execution.

## Swap Lifecycle

```
Request Quote → Deposit Tokens → Submit Tx Hash → Monitor Status → Success/Refund
```

1. **Request a quote** - POST `/v0/quote` with your intent parameters
   - `dry: true` for preview (no deposit address)
   - `dry: false` to commit and receive deposit address (~10 min validity)

2. **Deposit tokens** - Send tokens to the unique deposit address
   - 1Click automatically begins processing upon receipt

3. **Submit deposit tx** (optional) - POST `/v0/deposit/submit`
   - Speeds up processing by notifying 1Click immediately

4. **Monitor progress** (optional) - GET `/v0/status`
   - Poll until terminal state

5. **Result** - Swap succeeds with tokens delivered, or fails with automatic refund

## Swap Statuses

| Status | Terminal | Description |
|--------|----------|-------------|
| `PENDING_DEPOSIT` | No | Waiting for deposit at deposit address |
| `PROCESSING` | No | Deposit detected, Market Makers executing |
| `SUCCESS` | Yes | Tokens delivered to recipient |
| `INCOMPLETE_DEPOSIT` | Yes | Deposit below required amount |
| `REFUNDED` | Yes | Swap failed, funds returned to refund address |
| `FAILED` | Yes | Error occurred |

## CEX Deposit Warning

Centralized exchanges (CEXes) often use intermediate or per-user deposit addresses. These may not credit deposits sent via NEAR Intents until they are recognized or whitelisted.

**Recommendation:** Send a small test amount before attempting full-scale transfers to CEX addresses.

## Authentication

Register on the [Partners Portal](https://partners.near-intents.org/) to obtain an API key and avoid the 0.1% (10 basis points) fee.

```typescript
headers: { Authorization: `Bearer ${apiKey}` }
```

## Display vs Logic

The `amountOutUsd` field in quote responses is for **display purposes only**. Never use it in business logic or calculations. Always use actual token amounts (`amountOut`, `amountIn`).
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall