Discover entitled pools

For approved 0Pools partners, discover which pool-backed liquidity paths the partner account can use.

0Pools is an approved partner liquidity surface for entitled partners that need headless pool-backed quote and trade workflows. Most public integrations should use 0Gate unless 0Bit has enabled 0Pools for the partner account.

Use 0Gate unless 0Pools is approved

Most public integrations should stay on 0Gate. Do not present 0Pools as a shortcut around hosted 0Gate, product approval, KYC/KYB review, or compliance review.

Product boundary

What discovery answers

Question	Safe answer
Which pools can this partner see?	Only pools tied to the partner entitlement.
Is the pool currently usable?	A partner-safe availability flag.
Should the user continue?	Continue only when your app and 0Pools both allow the path.
Why is a pool unavailable?	Show a generic unavailable state unless 0Bit approves more detailed wording.

Implementation shape

Confirm product approval before exposing 0Pools UI.
Discover pools from your server or trusted backend flow.
Store the pool id, availability result, checked timestamp, and partner account context.
Show only entitled pools to the user or internal operator.
Request a quote only after availability is true for the selected pool.

async function choosePoolPath(input: { partnerId: string; requestedPair: string }) {
  const approval = await partnerApprovals.require('0pools_headless_liquidity');
  if (!approval.allowed) return { route: '0gate_hosted' };

  const pools = await poolsClient.listEntitledPools();
  const pool = pools.find((item) => item.id === input.requestedPair);

  if (!pool || !pool.available) {
    return { route: 'unavailable', reason: 'pool_unavailable' };
  }

  return { route: '0pools_quote', poolId: pool.id };
}

Public-safe guardrails

Do	Avoid
Say that 0Pools is for approved headless liquidity partners.	Publishing provider, venue, treasury, routing, reserve, or balance mechanics.
Treat availability as dynamic.	Promising a pool is permanently available.
Keep unavailable copy generic.	Showing internal disable switches, inventory causes, or operational diagnostics.
Store discovery checks for support.	Logging secret credentials or raw operational responses.