Using Binho Support with AI Agents
Every page in this documentation can be read by an AI assistant as clean Markdown, so an assistant can be asked about Binho host adapters, Mission Control or the SDKs and have it answer from the current documentation instead of from memory.
What is available
Section titled “What is available”| Address | What it gives an assistant |
|---|---|
https://support.binho.io/llms.txt | An index of every page with its title, a link to the Markdown version, and a one-line description. Start here. |
Any page URL with .md added | That page as plain Markdown. For example, https://support.binho.io/support/contact-us.md. |
https://support.binho.io/llms-full.txt | The whole documentation in a single file. It is large, so use it with tools that index a URL or with assistants that have a big context window. |
https://support.binho.io/llms-small.txt | A shorter version of the whole documentation with non-essential content removed. |
How to use it
Section titled “How to use it”Coding assistants (Claude Code, Cursor and similar). Ask the assistant to read the index first and then open only the pages it needs. For example:
Read https://support.binho.io/llms.txt, then use the Binho docs to show me how toenumerate a Supernova and run an I2C read with the Python SDK.Chat assistants. Paste a page’s .md address into the conversation, or paste the Markdown itself, and ask a question about it.
Tools that index documentation from a URL. Add https://support.binho.io/llms-full.txt as the source.
Getting better answers
Section titled “Getting better answers”- Name the hardware and versions. Say whether the device is a Nova, Supernova or Pulsar, and which firmware and Mission Control or SDK versions are in use. Features differ between devices.
- Ask for the page it used. If the assistant cites a page, open it and confirm the answer.
- Give it the exact error. Paste the full message or log output rather than a summary.
Report a problem
Section titled “Report a problem”If an assistant gives an answer that does not match the documentation, or a page is out of date, tell us at [email protected] and include the page address. See Contact Us for other ways to reach the team.

