> 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/resources/glossary.md). # Glossary The terms you meet inside Lid in plain words: digital dollars (USDC), commission, sharer, pool, challenge, campaign, membership, agent. The handful of terms you will meet inside Lid, in plain words. ## Digital dollars The money you earn and spend on Lid. On Lid they are USDC: each one is worth one US dollar. ## Commission The share of a sale, set by the seller between 1% and 50%, that goes to the person whose link led to the purchase. ## Sharer Anyone who shares a product link and earns the commission when someone buys through it. The API calls a sharer an affiliate. ## Share link Your personal link to a product; when someone buys through it, you earn the commission. ## Tracked link A short link that counts clicks and results. Campaigns are built from them. ## Payout For a seller, the money that lands in your account the moment a sale happens, automatically. For a sharer, the commission assigned to you in that same moment, which you claim when you want. ## Refund window A period the seller chooses, from 1 to 90 days, during which the payment is held and the buyer can release it early or open a dispute. ## Pool Where a challenge or campaign budget sits, in the funder's control, until a result verifies. Everyone can see it. ## Challenge A competition with a prize. The prize sits in a pool while people compete; when the person who posted it chooses who gets each prize, each prize is assigned to its holder and they claim it from their dashboard. Challenges were called bounties until August 2026. The API still says bounty. ## Campaign A reward pool that pays sharers for verified results, like signups or sales. Anyone can generate their own link and earn from the pool when their visitors deliver the result and the funder approves it. ## Course A product made of lessons that buyers unlock when they purchase. ## Membership A paid space your members subscribe to, monthly or yearly: posts only they can see, messages with you, and your own page, billed on a recurring subscription. ## Service Being built. Work you will sell with protected payment: the money is held until the buyer confirms the work was delivered. ## Agent Software that works on Lid through the agent connection: it creates products, shares, runs challenges and campaigns, and reads its sales. See [Agents on Lid](/agents.md). ## Lida The help built into Lid. You focus on your business; Lida helps with the rest. She answers your questions, drafts your products and reads your sales; where the Builder is switched on, she builds your site. ## Your own site A site with your brand, built with Lida and hosted by Lid, on a Lid address or on your own domain. Its products are paid through the Lid checkout. ## Prize holder The person a challenge prize is assigned to. Only they can claim it. ## Claim Taking money that is assigned to you, like a sharer's commission or a challenge prize. Only you can do it. ## Dispute What a buyer opens during a refund window when something went wrong. The payment stays frozen until our team decides where it goes: to the seller, or back to the buyer. ## Referral Inviting someone to Lid with your invite link, from **Referrals** in your dashboard. Their activity earns you 0.50%. --- # 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/resources/glossary.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.