AI Assistant Context

Use B3OS documentation as source context for AI coding assistants without exposing private credentials or internal notes.

B3OS docs are structured for human developers and AI coding assistants. Use the narrative pages for concepts and recipes, and use reference pages for exact action, trigger, and API schemas.

Quickstart

First workflow path for new developers.

Learn More
MCP Server

Connect Claude Code or Claude Desktop to B3OS via the MCP server.

Learn More
Workflow JSON

Graph structure, node IDs, payloads, connectors, and expressions.

Learn More
Action reference

Action, built-in action, logic action, and trigger schemas.

Learn More
API overview

REST API areas, authentication, pagination, and endpoint reference.

Learn More

Prompt Template

text
Use the B3OS docs as the canonical reference. Start with /quickstart, /examples/workflow-json, /actions/reference, /actions/trigger-reference, and /api/introduction. Do not invent action payload fields, trigger result fields, connector types, or API paths. If a workflow can move funds or call an external provider, call out the required connector, wallet, simulation, and review steps.

What Not to Include

Give agents links to B3OS docs pages, action references, trigger references, and API references.

Do not paste raw API keys, connector credentials, private wallet material, customer data, or internal deployment notes into third-party assistants.

The fastest way for Claude to interact with B3OS is through the MCP server. Install it once and Claude can build, run, debug, and query workflows directly — no copy-pasting API keys or docs into prompts.

bash
npm install -g @b3dotfun/b3os-mcp && b3os-mcp-setup

AI-Readable Endpoints

HolyDocs publishes AI-readable docs files for deployed sites. After deployment, use:

text
https://docs.b3os.org/llms.txthttps://docs.b3os.org/llms-full.txt

Use the published references when asking assistants about actions, triggers, or API schemas.

Ask a question... ⌘I