> For the complete documentation index, see [llms.txt](https://docs.amp.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amp.xyz/grants/request-for-proposal.md). # Request for Proposal The Amp Grant Program periodically issues Requests for Proposals (RFP) to direct builders towards high-impact areas within the digital payments ecosystem. These RFPs are open to anyone, including established teams and previous grant recipients. 1. Application process * Builders apply for grants using the same process and form as standard applications * Applicants must indicate on the form if they are responding to an RFP 2. Publication of RFPs * Requests will be posted on the grants section of the Amp GitBook * Each RFP will outline specific milestones and success metrics 3. Application timeline * RFP applications are open for 30 days * If no suitable proposals are received within this period, the application window may be extended as necessary 4. Evaluation and funding * Submissions will be reviewed, and a project winner will be funded based on its potential impact and alignment with the RFP goals *** --- # 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.amp.xyz/grants/request-for-proposal.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.