OpenOcean: wallet swaps, API fees, recurring orders and execution authority

OpenOcean offers a direct token-swap application alongside APIs, an SDK and embedded integrations. It aggregates liquidity from external sources rather than maintaining one universal customer order book. The direct client makes it more than a software supplier for other exchanges, but a route still depends on its underlying pools, market makers, token contracts and network.[2]

The website also links bridge and other trading products. This profile’s established service is token exchange through the documented swap and order routes; a link to a leveraged product or prediction market does not establish that every product has the same operator, custody, fee schedule or regional availability.[1]

The V4 API reports estimated price impact but does not enforce a maximum price-impact block. Integrators must implement their own threshold. Its slippage parameter accepts 0.05%–50%, defaulting to 1%; that setting is a tolerance, not a prediction of the loss on a trade.[5]

This public Swap API schedule is distinct from negotiated Pro arrangements and an unestablished universal website tariff. Pair classification determines the rate.[4]

For same-category pairs, collection is in the output token. For mixed categories, the page gives collection priority as Stable, Correlated, Common, then Exotic. Check the current token classification and quote before treating a percentage as a particular token debit.[4]

On 10,000 value units, 0.01% equals 1 and 0.50% equals 50. These illustrate rates, not a particular mixed-pair collection asset.[4]

The partnership programme describes revenue sharing and negotiated integration support. It does not establish an unconditional retail cash bonus, a fixed referral payout or withdrawable credit for merely connecting a wallet. Any separate promotion needs its own eligibility, calculation and claim terms.[15]

The normal swap flow starts from tokens already in a compatible wallet: check the network and allowance, approve the relevant spender if needed, obtain a quote, build the transaction, then sign and broadcast. There is no conventional exchange cash balance to fund and later withdraw in this documented route. A bank purchase or bank cash-out would require a separately identified provider.[6]

DCA intervals must be at least 60 seconds. The total allocation, execution count and optional minimum/maximum price bounds are distinct instructions. A recurring strategy is not a savings balance with a guaranteed conversion time: a particular slice may fail or remain unexecuted. Its execution-history route includes transaction hashes and reasons, which should be checked separately from the overall strategy status.[19]

The network guide requires an authorized API key and whitelisting for Solana access. Its broad multi-chain headline therefore does not mean every API feature is public on every network. Ethereum, Base, BNB Chain and Arbitrum also use different gas assets, token deployments and product-specific permissions.[21]

OpenOcean describes its swap service as noncustodial: the user authorizes movement from a wallet through the relevant contracts to the destination. This removes the ordinary hosted-exchange withdrawal queue from that route but leaves approval, smart-contract, wallet, token and underlying-liquidity exposure. The security page’s audit links are version-specific; they do not establish a personal insurance policy or an unconditional reimbursement promise.[7]

A disconnected wallet interface should not be treated as proof that allowances or signed orders have been revoked. This follows from the separate approval, expiry and cancellation mechanisms. Check the actual spender allowance and order state when ending access. A one-time wallet connection and an ongoing permission are different things.[8][16]

The linked De1 privacy policy says wallet addresses, public-chain information and identity information required for compliance may be processed. A wallet-based service is therefore not automatically anonymous. That policy names De1’s platform; its application to each legacy OpenOcean page was not established.[25]

A complete country matrix and operative client contract for the legacy OpenOcean application were not established from its current public pages. Network support describes technical availability, not legal eligibility. Integrators should identify both their own service terms and the terms governing the route presented to the customer.[2]

The linked De1 terms require adults and exclude the United States, North Korea, Syria, Iran, Cuba, Venezuela, Crimea, Luhansk, Donetsk and other sanctioned locations. They also prohibit use where unlawful. Those conditions are retained for De1 services; the documents do not expressly name the legacy OpenOcean client.[24]

For API 429 or server-error responses, the prerequisites guide recommends progressively longer retry waits. Higher throughput requires the relevant API arrangement. Retrying a read request is different from resubmitting a signed transaction; check its hash and status before assuming it never reached the network. No guaranteed retail response time or emergency telephone-dealing route was established.[13]

De1’s terms provide a 30-day informal dispute period before SIAC arbitration and a separate 30-day arbitration opt-out window. Singapore law governs. These contractual clocks are not a support-response SLA; the terms also disclaim an ongoing support obligation.[24]

The address-based event stream reports DCA and limit-order fills. A disconnected stream can interrupt notifications without cancelling orders. Reconnect, review order history and reconcile transaction hashes; an absent screen update is not proof that no execution occurred.[20]

No independently verified financial permission or customer-compensation entitlement was established for this profile. The security documentation describes technology and custody characteristics, not a regulator’s authorization. Likewise, the linked De1 contract’s choice of Singapore law does not establish incorporation there or a MAS licence.[7][24]

The GitHub organization linked from OpenOcean’s documentation still uses the openocean-finance address but now displays De1 and links de1.ai. This is evidence of overlapping public identities. It is not, by itself, a corporate register entry, a dated novation of customer contracts or proof that every old product has migrated.[22]

De1’s privacy policy identifies Deluthium Ltd. as its operator. The inspected materials do not establish that company as the counterparty for every legacy OpenOcean transaction, and its incorporation jurisdiction was not verified. An exact OpenOcean client counterparty therefore remains unestablished from the inspected evidence.[25]

On 20 October, OpenOcean’s homepage displayed more than 20 million total trades and 2.8 million under a total-active-users label, alongside 40-plus chains and 1,000-plus liquidity sources. These are company-displayed cumulative or undefined-period metrics, not a verified monthly-active-trader count. A liquidity source is also different from a distinct exchange operator or a customer account.[1]

The linked De1 homepage presents additional execution and model-training products with separate app and legal-document links. Its counters are not added to OpenOcean’s counters: the inspected pages do not establish whether the populations overlap or share a consistent measurement period.[23]

Operator

OpenOcean brand; legacy client contracting entity not established

Exchange model

Decentralised

Service scope

Direct wallet-based token swaps and routed order services; API, SDK and AI integrations.

Client types

Retail clients; Professional clients

Pricing publication

Public and quoted pricing

Other names

OpenOcean Finance

Funding scope

Tokens and network gas in a compatible wallet; no custodial cash account established.

Custody and asset handling

User-controlled wallets authorize router operations; token allowances and signed orders can persist.

Client eligibility

Complete legacy-client country terms not established; linked De1 services have separate exclusions.

Support

Official API Telegram and partnership channels; no guaranteed retail response or dealing clock established.

Authorisation and registration scope

No verified financial permission or customer compensation entitlement established.

Exchange metadata checked 20 Oct 2026Source 1Source 2Source 3Source 4Source 6Source 7Source 8Source 15Source 21Source 22Source 24

The agent integration guide separates four workflows, from quotes to immediate execution. A conversational request can therefore become either market information or an onchain instruction depending on the enabled workflow. The authority resides in the configured signer and permissions; the existence of natural-language tooling does not establish an advisory service or a mandate to select investments.[12]

API records include transaction status, sender, recipient, token amounts and transaction costs. Preserve both order hashes and onchain transaction hashes when reconciling a recurring or limit strategy. This is operational data, not a promised tax form.[5]

The limit-order guide and reference use inconsistent numeric status examples. Integrations should reconcile the actual endpoint response with fill records and documented transaction hashes rather than assuming one copied status-number table is authoritative for all versions. Expiry is expressed in milliseconds and cancellation is a separately signed request.[17]