GulfOne routing surface for bridges and swaps

Config-driven providers, normalized quote and execution plans, local-only EVM signing.

Get started

HTTP API

Provider-neutral

Generic HTTP mappings and native adapters produce a common quote and action-plan model.

Key-safe server

The HTTP API prepares transactions and proxies RPC calls. It never receives signing keys.

Operationally explicit

Inspect configured routes, obtain a live quote, review every action, then submit locally.

Start with intent, inspect the plan

Gulf resolves configured chains, tokens, providers, fees, and recipient data from TOML. Use the CLI for a local EVM execution, the Rust library in an application, or the HTTP API to prepare an externally signed transaction.

Quotes, liquidity, gas, fees, and settlement timing are volatile. Treat every live result as route-specific rather than a guarantee.

Read the security guidance before submitting an irreversible transaction, and the live-test record for evidence captured July 10, 2026.

GulfOne routing surface for bridges and swaps

Provider-neutral

Key-safe server

Operationally explicit

Start with intent, inspect the plan ​

Start with intent, inspect the plan