BioFlow / Developers / AI tooling
Every page of the BioFlow developer surface has a machine-readable counterpart — plain-text indexes, markdown twins, a downloadable spec, and a remote MCP server. Point your assistant at any of them.
/llms.txt is the compact site index (llmstxt.org convention). /llms-full.txt goes further: the entire API reference — every operation, every error code — as one plain-text document an agent can ingest in a single fetch.
Append .md to any developer page URL and you get the same content as clean markdown:
https://getbioflow.com/docs/api.md
https://getbioflow.com/docs/api/webhooks.md
https://getbioflow.com/docs/api/operations/list-pages.md
https://getbioflow.com/docs/api/errors/rate-limited.md
https://getbioflow.com/developers.md · https://getbioflow.com/changelog.mdThe exact document the /v1 surface is generated from — every operation, schema, scope, and quota-cost annotation:
https://getbioflow.com/docs/api/openapi.jsonFor agents that should operate a workspace rather than call REST: a remote MCP server with 12 tools behind OAuth 2.1 at https://app.getbioflow.com/api/mcp. Full docs on /mcp. Connect from Claude Code:
claude mcp add --transport http bioflow https://app.getbioflow.com/api/mcpA ready-made prompt that points the agent at the markdown docs and sets a safe key-handling ground rule:
You're helping me build on the BioFlow API. Read https://getbioflow.com/docs/api.md for the full surface (auth, quotas, errors, all 22 operations), then help me write code against https://app.getbioflow.com/v1. My API key is in the BIOFLOW_API_KEY env var — never print it.REST docs live on the API docs hub; the human-facing platform overview is /developers.