> For the complete documentation index, see [llms.txt](https://docs.lid.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lid.pro/developers/integrations.md). # Integrations What integrates with Lid today (Privy, MoonPay, Alchemy, Pinata, Solana Pay, USDC, webhooks, MCP), what is being built, and how to propose an integration. Lid is designed to play well with the tools creators and developers already use. This page covers what integrates today, what's planned, and how to propose a new one. ## What integrates today **The live stack** * **Privy** · embedded wallet and auth. Live. * **Alchemy** · Solana RPC. Live. * **Pinata** · IPFS metadata storage. Live. * **Solana Pay** · checkout UX. Live. * **USDC SPL Token** · settlement asset. Live. * **MoonPay** · card in: card, Apple Pay or bank transfer into digital dollars. Live. * **Bridge** · bank out. Being built. * **Helius webhooks** · transaction monitoring. Planned. * **x402 / ACP** · long-term horizon. **Payment inputs** * USDC on Solana (native) * Card, Apple Pay or bank transfer on the buyer side, through MoonPay where MoonPay operates: the buyer adds digital dollars (USDC) and pays in USDC **Delivery targets** * Direct file delivery (PDF, ZIP, video, any file type) * URL-based delivery (Notion, Google Drive, YouTube, Discord, Telegram, any link) **Social sharing** * Share links are plain URLs, so they work on every platform. X, LinkedIn, Instagram, TikTok, Threads, email, newsletter, Discord, Telegram, community forums, blogs. **Agent surface** * The agent connection over MCP, live. Agents create products, share links, challenges and campaigns, read sales, and build sites with Lida where the Builder is switched on. Purchases from the agent wallet are in preview. See [Agents on Lid](/agents.md). **Webhooks** * Live. Signed deliveries for `purchase.completed`, `prize.claimed`, `conversion.approved`, `subscription.created` and `bounty.submission.created`. See [Webhooks and events](/agents/webhooks.md). **Verification** * Every sale produces a Solana transaction signature that can be verified on any block explorer. ## On the roadmap **Bank out.** Being built on Bridge rails, five countries first. Card in is already live through MoonPay. **SDK (JavaScript, Python).** Client libraries for reading Lid state and creating products or share links programmatically. **Embeddable checkout.** Drop-in checkout flow for sellers who want to run the product page on their own site. ## Integration principles we hold to **Don't break the trust layer.** No integration is allowed to touch the money flow. External systems read state, receive events, or trigger actions. Settlement stays on-chain. **Don't expose Web3 complexity.** Any integration Lid endorses must preserve the abstracted UX. If an integration adds wallet prompts or chain selectors to the end-user flow, it's not on-brand. **Don't add hidden fees.** Integration partners can charge their own fees visibly, on top of Lid. They cannot skim Lid's 3% or take commission from the seller's share without explicit disclosure. ## Proposing an integration If you want to integrate Lid with a product you're building, we want to hear from you. Especially if you're building: * AI agent frameworks * Creator toolkits (content platforms, newsletter tools, community platforms) * Analytics or attribution tools * Marketplaces or aggregators * Crypto wallets or exchanges Email with: 1. What you're building 2. How you'd integrate Lid 3. What API or event surface you'd need 4. Timeline Selected partners get early API access and design input. ## Partnership posture We do not do prestige partnerships for the sake of prestige. Every integration we endorse has to produce measurable benefit for sellers or sharers. Big-partnership theater gets filtered out. Lightweight, practical, measurable. That's the standard. Next: [Vision](/company/vision.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.lid.pro/developers/integrations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.