> For the complete documentation index, see [llms.txt](https://docs.spearbit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spearbit.com/spearbook/anatomy-of-a-spearbit-review/form-submission.md).
# Form Submission
## Inbound Leads
Clients that are looking for a security review **by industry-leading web3 security professionals** across the Spearbit network can reach out to Spearbit in a multitude of different ways. \
\
The primary means of requesting a security review is via the [**Spearbit website**](https://spearbit.com/)**.**
Upon requesting a security review - clients are taken to a form in which they are prompted to provide the following for the Spearbit team to review:
* *Project Name*
* *Project Details*
* *Contact Information*
* *Source of Knowledge about Spearbit*
* *Relevant Code Repositories*
* *Extent of Services Requested*
* *Budget*
* *Timeline*
Additionally, clients can also reach out to us on [**Spearbit Twitter**](https://twitter.com/SpearbitDAO) via a direct message, however, we highly encourage the submission of a formal request for review via our website so the team can begin to assess the needs and requirements of your project.
To schedule a direct call with our COO (Mike Leffer) regarding your potential security review from Spearbit - you can schedule time directly on his calendar [**here**](https://calendar.app.google/P3WHa3pxBtTygP439)**.**\
\
Prior to reaching out through other mediums - the Spearbit team highly recommends clients reach out via our request form as mentioned above so we may cater to the needs that suit a particular project or protocol as best as possible.
### Time to Response
Spearbit prides itself in being timely in all forms of the engagement process and we strive to set that precedent from the very beginning. All inbound form submissions can expect a response within **24 hours** of receipt by the Spearbit team.
{% hint style="info" %}
**Note:** For quality assurance and security reasons - the core team will perform due diligence on the client request prior to proceeding with any subsequent steps of the security review process.
{% endhint %}
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.spearbit.com/spearbook/anatomy-of-a-spearbit-review/form-submission.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.