> ## Documentation Index
> Fetch the complete documentation index at: https://docs.picon.finance/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> The shapes an integration with Picon DLMM can take

There are three broad ways to integrate with Picon DLMM, depending on what you're building and
which runtime you're building it in:

<CardGroup cols={1}>
  <Card title="Full SDK integration" icon="cubes" href="/sdk/quickstart">
    A TypeScript app, bot, or backend that owns the whole flow — fetching pool/position state,
    quoting, building and sending transactions. Use `@picon-finance/dlmm-sdk` directly. This
    covers most integrations: wallets, portfolio trackers, LP-management bots, simple trading
    bots.
  </Card>

  <Card title="Router / aggregator venue" icon="route" href="/integrations/aggregators-and-routers">
    You're plugging Picon DLMM into an existing multi-venue router as one routable pool type,
    likely from Rust, and likely need to quote fast against cached account state you already
    manage yourself rather than owning RPC fetching.
  </Card>

  <Card title="Quote-only, no SDK" icon="calculator" href="/integrations/quoting-without-the-sdk">
    You just need accurate swap-quote math — in Rust natively, or from any language via WASM —
    without pulling in the SDK's RPC/transaction-building layer at all. The quote engine that
    powers the TypeScript SDK is a standalone, dependency-free crate you can use directly.
  </Card>
</CardGroup>

## What's admin-gated vs. permissionless

Before integrating, it's worth internalizing one structural fact that differs from some other
DLMM designs: **pool creation is admin-gated**, not permissionless. If your integration assumes
it can spin up new pools on demand (e.g. an automated market-making bot that creates a pool for
a new token pair), that assumption doesn't hold here — pools are created by the Picon Finance
admin authority. Swapping, depositing, withdrawing, and claiming against *existing* pools are
all fully permissionless. See [Governance](/concepts/governance) for the full scope.

## A note on liquidity shapes

If your integration deposits liquidity on a user's behalf (an LP-management bot, a vault, a
"one-click Curve strategy" UI), remember that Spot/Curve/Bid-Ask shape generation isn't part of
the protocol or the SDK — you'll write that weight-curve logic yourself. See
[Positions and liquidity](/concepts/positions-and-liquidity#depositing-by-weight).