> For the complete documentation index, see [llms.txt](https://handbook.opencoreventures.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.opencoreventures.com/founder-experience/vendor-deals.md). # Vendor Deals OCV's vendor perks and discounts live on [GetProven](https://wstc.getproven.com/vendors), our private marketplace for portfolio companies. Founders will receive an email invitation to join; once you're in, you can browse vetted vendors across the tools and platforms most commonly used by early-stage companies and claim offers directly. The OCV Ops team keeps GetProven up to date and adds new vendors as we build new partnerships. If you haven't received an invite, or you know of a tool or partnership that would be valuable to the portfolio, let the OCV Ops team know. If you're selling B2B, you can also create a verified profile on GetProven and list an offer for other companies in the OCV portfolio. Offers can be extended to other VC and PE marketplaces in the GetProven network, subject to their review. If you'd like to explore that, the OCV Ops team is happy to introduce you to the GetProven team. --- # 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://handbook.opencoreventures.com/founder-experience/vendor-deals.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.