Developer Guides
Integrate grapl with an RPC endpoint, a wallet, and explicit transaction control.
Use the TypeScript SDK to prepare protocol operations in your application. RPC reads and transaction preparation run off-chain; the Solana program enforces settlement and pool rules. The grapl API is optional.
SDK
Connect directly to RPC and prepare unsigned token, pool, liquidity, swap, and fee operations.
API Guides
Discover pools, compare direct quotes, and observe transaction outcomes through HTTP.
Hooks
Build authenticated lifecycle policies, custom fees, eligibility rules, and rewards.
API Reference
Explore the full public OpenAPI contract, grouped by resource.
On-chain Reference
Find instruction accounts, layouts, errors, math and the hook ABI.
Each section has its own guides and navigation. Start with the SDK for wallet execution, add the API when you need its optional services, or use Hooks to author a pool policy.
Protocol areas
| Area | Start here | Reference |
|---|---|---|
| AMM | Pricing and CLMM math | Integer math |
| Hooks | Lifecycle and examples | Hook ABI |
| Market creation | Build a market | Instructions |
| Routing | Metis adapter | Wallet context |
| Data services | Optional API | Accounts |
For larger compositions, read Address Lookup Tables. Use AI documentation tools to copy Markdown or provide context to an assistant. Current capabilities are recorded in Protocol status; source availability does not imply npm publication, public deployment, or Jupiter admission.
The grapl application uses the development sandbox, with verified RPC/faucet connections, a persistent validator restart and a completed public UI flow on the previous application hostname: two claims plus seven SDK actions. The test covers CLMM with classic SPL tokens, no hook and an ephemeral wallet. The current backend endpoints and discovery of the newest test pool were verified on October 12, 2026. External wallet compatibility remains unverified, and the indexed receipt history still has an explicit gap.
Protocol revenue
Fees and revenue explains mandatory protocol retention, immutable remainder splits, treasury and beneficiary claim authorization, and why accrued tokens are not an automatically converted USDC balance.