Client Minimal Package

Minimal package for Bitwarden

This page shows exactly what the client publishes on their own website, what the developer needs to do, and which files stay only in Agntbase.

4 files placed on client site 1 human instruction file 3 canonical files remain in Agntbase
Client website files

Files the client publishes

These four files and snippets are the minimal machine-readable layer that goes on the client website.

company-profile.json

Minimal machine-readable company profile for the client site.

/company-profile.json
llms.txt

Short agent-facing reading order and canonical links.

/llms.txt
.well-known/agenthub.json

Entrypoint file linking the client site to the canonical Agntbase profile.

/.well-known/agenthub.json
jsonld-snippet.raw.txt

JSON-LD block to paste into the <head> of the client website.

Paste into HTML <head>
Instruction file

Human-readable deployment guide

This is the file a founder, marketer, or developer can open to see the exact placement order.

README.html

Detailed placement instructions with step-by-step order and live links.

/packages/digital_bitwarden_618cbae0-client/README.html
Hub-only files

Files kept in Agntbase

These files do not go on the client website. They remain in the hub as the canonical profile, memory layer, and permissions layer.

Canonical HTML profile

Human-readable profile page in Agntbase.

/p/<profile_id>/index.html
Canonical JSON profile

Extended machine-readable profile with trust and provenance context.

/p/<profile_id>/index.json
Permissions layer

Permissions and policy constraints for agents using the canonical profile.

/p/<profile_id>/permissions.json