AI and agent access

Use Ownfold documentation from coding agents through static, private, machine-readable discovery without a hosted AI service.

Ownfold’s static documentation publishes machine-readable discovery surfaces without sending questions, source code, or usage data to an Ownfold service.

Available surfaces

• /llms.txt provides the structured documentation index.
• /llms-full.txt provides the complete public documentation corpus.
• Add .md to any documentation route to read its normalized Markdown; use .mdx for the source.
• /agent-readability.json describes the enabled machine-readable artifacts.
• Production builds publish /.well-known/agent-skills/index.json and the Ownfold integration skill with a verifiable SHA-256 digest. These generated files are not served by blume dev.
• WebMCP registers read-only search_docs, get_page, and list_pages tools in browsers that implement the emerging model-context API. It silently does nothing elsewhere.

These endpoints contain public documentation only. They do not expose vaults, user records, Recovery Kits, keys, application sessions, or private repository content.

Install the skill

Install ownfold-integration with the Skills CLI:

npx skills add DeepanshuMishraa/ownfold@ownfold-integration

The CLI prompts for the target agents and installation scope. Add --global for a user-level installation or --agent codex --yes for a non-interactive Codex installation.

Agents can also discover the skill from the production well-known index. The skill teaches package selection, integration order, ciphertext-only boundaries, recovery constraints, typed failure handling, security review, and required adversarial tests. Its source lives at skills/ownfold-integration/SKILL.md.

Deliberately disabled

Ownfold keeps the documentation build static. Hosted Ask AI and hosted MCP remain disabled because both require a live server endpoint. Web Bot Auth is not published because Ownfold does not operate an outbound signing agent with a public identity key.

These choices affect the documentation site only. Applications using the SDK still contact only the host application’s configured transports.