Skip to main content
FlowState is designed to be integrated as a liquidity source rather than used as a destination that buyers must visit directly. The same underlying C1 inventory can be reached through several technical paths. Which path is appropriate depends on whether the partner wants direct on-chain control, hosted quoting and calldata, low-latency RFQ or an intent-specific execution adapter.

​
Choose an integration path

Direct Market integration

Discover, quote and execute directly against the FlowstateMarket contract.

Machine-facing API

Use FlowState’s application API layer, including swapOTC, when the integration prefers hosted quoting and executable transaction data over constructing Market calls itself.

RFQ integration

Use the low-latency RFQ path for supported quote protocols and latency-sensitive request flows.

Intent / execution adapter

Source C1 output inventory inside a solver, filler or resolver settlement flow.
Other distribution adapters, including the FlowState Uniswap V4 hook, can expose the same underlying C1 inventory through venue-specific execution paths. These paths do not create separate copies of C1 token depth.

​
The common integration lifecycle

Regardless of integration shape, the core lifecycle is similar.
1

Discover inventory

Resolve the C1 Pool for the inventory token and identify the approved quote asset intended for the trade.
2

Quote current state

Query the Market directly or use the relevant hosted integration surface. A quote is an assessment of current executable state, not an inventory reservation.
3

Compare routes

Treat C1 as one execution source alongside AMMs, RFQ venues, order books or proprietary inventory. Include gas, external fees and route constraints in the comparison.
4

Execute

Submit the selected Market call directly or use the calldata / adapter path appropriate to the integration.
5

Handle fallback

Available inventory and oracle-derived pricing can change between quote and settlement. Integrations should maintain a fallback path where execution certainty is required.

​
Direct contract example

The Market exposes a non-reverting view quoter for normal route unavailability. The current signature is documented in full on Contract Interface, but the integration shape is intentionally compact:
The caller identifies the per-token pool, approved ERC-20 quote asset and requested inventory amount. When a route is unavailable because the pool is unavailable, paused, empty or the quote asset is not approved, the quote path reports unavailability rather than requiring the integrator to treat that C1 route as a failed quoting pass. The current Market exposes three buy entry points covering token-amount, exact-quote and exact-output execution. Exact-input execution is inventory-bounded and can spend less than the amount offered when available C1 inventory is smaller. Exact-output execution remains all-or-nothing. See Contract Interface for the current signatures and semantics.

​
API integration

Partners that do not want to construct Market calls directly can integrate through FlowState’s machine-facing API layer. The current architecture includes PoolParty_APIs, with swapOTC providing a partner-oriented path for quotes and executable transaction data around C1 liquidity. The API is a convenience and orchestration layer. It does not replace the on-chain execution authority: final settlement still occurs through the FlowState Market and Pool contracts. Exact public endpoints, request schemas, authentication and production rate limits should be taken from the current partner API reference when issued. They are intentionally not hard-coded into this page while the release interface is being finalised.

​
RFQ and intent paths

The FlowState execution stack also supports latency-sensitive and intent-driven integrations.
  • RFQ: a dedicated service can answer supported RFQ requests from an asynchronously refreshed pricing view and decline safely when FlowState cannot provide a quote.
  • Intent execution: fillers or resolvers can source the token being purchased from C1 during settlement, using the appropriate FlowState executor path.
  • V4 distribution: the FlowState V4 hook is another distribution adapter into shared C1 inventory rather than a separate liquidity pool.
These paths are documented at a conceptual level here. Partner-specific integration material should pin the exact deployed contract and service generation before implementation.

​
Quote behaviour

A C1 quote does not reserve inventory or guarantee later execution. Available inventory can change before settlement and protected oracle-derived pricing can move between blocks. Quote and execution use the same pricing path. When evaluated against the same block pricing state, they use the same unit rate rather than separate quote and execution pricing models. For direct on-chain integrations, simulate close to execution. For hosted or RFQ integrations, treat an unavailable or declined C1 quote as a normal routing outcome and maintain an appropriate fallback.

​
Current deployment status

FlowState remains pre-launch. Current staging networks, contract addresses and release state are maintained on Deployments. Security-review status is maintained on Audits & Security.

​
Go deeper

How C1 Pools Work

Pool mechanics, multi-asset settlement, FIFO and execution protections.

Contract Interface

Current quoter and execution signatures.

Settlement Patterns

Router, V4, intent-based and direct execution patterns.

Get Integration Support

Contact the team for current API, RFQ and staging integration material.