> For the complete documentation index, see [llms.txt](https://wiki.purduesigbots.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.purduesigbots.com/software/vex-programming-software/pros/okapilib.md). # OkapiLib OkapiLib is a PROS library for programming VEX V5 robots. This library is intended to raise the floor for teams with all levels of experience. New teams should have an easier time getting their robot up and running, and veteran teams should find that OkapiLib doesn't get in the way or place any limits on functionality. It also helps to shorten some of the more repetitive parts of programming a robot out of the way for teams that have to start new code projects every season (Example: Operator Control Code, Main PID Algorithm) {% hint style="info" %} Documentation for the latest version is hosted on the Okapi website: [Current OkapiLib Docs](https://okapilib.github.io/OkapiLib/index.html) {% endhint %} {% hint style="warning" %} Documentation for OkapiLib versions 3.x.x and below hosted on the PROS site: [Older OkapiLib Docs](https://pros.cs.purdue.edu/v5/okapi/api/index.html) {% endhint %} ## Teams Contributed to this Article: * [BLRS](https://purduesigbots.com/) (Purdue SIGBots) --- # 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://wiki.purduesigbots.com/software/vex-programming-software/pros/okapilib.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.