Build with Venue.
Read reviewed Arc assets, compare quotes and prepare unsigned swaps through the same engine as the Venue app.
Implemented API
The OpenAPI contract describes the current request formats and errors. Availability is restricted to the configured network. No public hosting or production service is implied.
| Method | Path | Result |
|---|---|---|
| GET | /api/v1/configuration | Reviewed execution capabilities |
| GET | /api/v1/tokens | Reviewed swap assets |
| GET | /api/v1/quotes | Exact-input quote comparison |
| POST | /api/v1/swap-preparations | Unsigned transaction or exact approval, with a preparation identity |
Review, prepare and confirm
Send raw amounts as decimal strings. Keep the minimum output the user reviewed in acceptedMinAmountOut. Preparation preserves that minimum during refresh or rejects the request. After approval, prepare again with the same accepted minimum and review the fresh transaction.
POST preparation currently requires the exact first-party application Origin and a UUID v4 Idempotency-Key. This is an origin-restricted wallet interface; workspace authentication and external builder access are pending. Retain the key and exact body when a response is lost. Same-key changed terms return a conflict. A failed, interrupted or expired preparation requires review before a new request identity.
Preparation records remain available for at least 30 minutes. After retention pruning, a reused key may create a new preparation. Check expiresAt every time: storage retention does not extend quote validity. A preparation ID identifies unsigned work; it is not proof of submission or settlement.
Wallet responsibility
The wallet reviews and signs each transaction. Verify network, account, recipient, assets, input, minimum output, spender, target, calldata and fees. Arc native USDC gas uses 18 decimals; the ERC-20 USDC representation uses 6. Never treat them as separate spendable balances.
Persist the exact intent before requesting a signature. An unknown submission blocks another trade until the original transaction is reconciled. Canonical receipt and token movement checks establish settlement.
Developer platform in progress
Workspaces, wallet sign-in, roles, scoped keys, quotas, attribution, usage, SDK, widget and authenticated operational MCP remain under development. Documentation tools will remain separate from wallet operations. The widget will share Venue's wallet engine and enforce allowed embedding origins. Secret keys must stay on the server.
Agents and advanced products
Automated strategies are not enabled. Dedicated agent wallets need explicit user-approved policies, enforceable spending and recipient restrictions, atomic budget reservations, revocation and qualified signing. Scheduled swaps come first; conditional swaps and rebalancing follow their own data and execution qualification.
Limit orders, vaults and liquidity positions require separate Arc contract and settlement acceptance. Fees and billing remain disabled until approved.