# Get building overview

Now that you’re up and running and have played around with the APIs and programmable card, you’ll be ready to bring your big ideas to life! Here are a few things to kick start your builds:

1. Take a look at the [Community GitHub repos](https://github.com/Investec-Developer-Community) and [open source projects](https://github.com/Investec-Developer-Community/Community-Projects%5C) for inspiration. Fork a repo if it looks like it could help you kick start your build.
2. Head over to [Community libraries and tools ](https://investec.gitbook.io/programmable-banking-community-wiki/get-building/community-libraries-and-tools)to find:
   1. **Wrappers for your language of choice.** 
      1. These have been created by community members. 
      2. If you want to create a new one and share it with others, please reach out on Slack and let us know. 
   2. **Tools to help you build**
      1. These have also been created by community members
      2. You will find the Postman collection [here](https://www.postman.com/investec-open-api/programmable-banking/overview), as well as things like auth components and emulators. 
3. Read through our community created [build tutorials and guides](https://investec.gitbook.io/programmable-banking-community-wiki/get-building/build-something-simple) if you want to sharpen your skills and understand more complex concepts related to the API and programmable card.
4. Challenge yourself and [sign up for a build event or challenge](https://investec.gitbook.io/programmable-banking-community-wiki/get-building/build-events). It’s a great way to learn quickly and give yourself a deadline.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://investec.gitbook.io/programmable-banking-community-wiki/get-building/get-building-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.