> For the complete documentation index, see [llms.txt](https://docs.solhuger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solhuger.com/resources/faq.md).

# FAQ

**Which blockchains do you work on?** Solana is our main focus. We also build on Ethereum, Base and BSC, and can bring the same product to several chains.

**What products can you build?** Presale platforms, staking, DEXs, crypto games, launchpads and trading or analytics bots.

**Do you handle the whole stack?** Yes. Smart contracts, backend and frontend are built in-house by one team.

**How long does a project take?** It depends on scope. A presale or staking platform usually takes a few weeks. We give a firm timeline after scoping.

**Can you integrate with Raydium and pump.fun?** Yes. We build launchpad flows that create SPL tokens, set authorities, create markets and add liquidity on Raydium, plus pump.fun integrations.

**Do you offer support after launch?** Yes: fixes, monitoring and new features.

**Can I see a working example?** Yes. See the [Portfolio](https://docs.solhuger.com/portfolio/portfolio.md).

**How do I start?** See [Start a Project](https://docs.solhuger.com/working-with-us/start-a-project.md).


---

# 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.solhuger.com/resources/faq.md?ask=<question>&goal=<user_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.
