Skip to main content
Avana logo

AppKit

How partners embed Avana LP-backed credit while Avana keeps responsibility for borrowing, risk, and settlement.

Overview

AppKit is for third-party products that already own the user relationship, such as DEXs, wallets, and portfolio apps where LP positions are already visible. The partner product frames the moment, captures context, and decides where the borrow entry appears. Avana runs the actual loan path.

AppKit is for partners that already own the user relationship — DEXs, wallets, and portfolio apps where LP positions are already visible. The partner controls placement and handoff. Avana runs the actual loan path.

Integration Model

Intent capture

AppKit belongs where users already understand their LP positions, portfolio state, or swap context, so the borrow entry appears next to existing intent instead of forcing a brand-new flow.

Protocol handoff

The partner passes wallet and market context into Avana. The borrow flow can then open with that context already set instead of asking the user to rebuild it by hand.

Partner economics

Partners may use referral, routing, or integration revenue structures, but they do not become the lender or the risk engine. Avana keeps credit, risk, and settlement.

Partner Controls

AppKit does not force one presentation model. Partners control the entry points and the amount of surrounding guidance, while leaving protocol decisions inside Avana.

  • Where the credit surface appears in the product
  • Which user segments see the borrow entry point
  • How much education or explanation appears alongside the handoff
  • Whether the product uses a full embedded handoff or a lighter context-preserving entry point

Implementation Notes

The best integrations feel like a continuation of the existing product flow, not a hard jump into an unrelated lending app. These notes are the practical baseline for getting that handoff right.

Place the credit entry near the LP position or portfolio view the user already trusts.

Pass wallet and market context into the borrow flow so the handoff does not feel like a reset.

Leave risk and settlement on Avana. Do not rebuild spoke valuation or liquidation logic in the partner UI.

Decide copy, placement, and launch gating before go live because they shape the integration, not just the polish layer.

Launch Notes

Launch AppKit as an integration project, not just a link placement. Confirm the user path, review where the entry sits, and make sure the Avana credit path stays clearly separated from the partner shell where responsibility changes.

Also check what happens when the credit surface is hidden, whether deep links into the borrow flow are safe, and how missing wallet, market, or collateral context is handled.