Agentize Websites

Use Agentize only inside a website repository controlled by the publisher. Its purpose is to turn owner-declared public content into an authoritative semantic index; it is not a command for crawling someone else's domain.

Ground the integration

Before changing anything, inspect the target repository for its package manager, Node version, framework, build scripts, existing agentize.config.*, and public content sources. Identify private or authenticated routes that must never enter the index.

Require Node.js 22 or newer. Follow the target repository's package-manager convention; examples below may use pnpm, but do not introduce pnpm into an npm or Yarn project solely for Agentize.

Check whether the @nicolasakf/agentize package and matching @nicolasakf/agentize-* packages are available from the configured registry or already linked in the workspace. Agentize's packages are versioned together. In a development checkout, prefer workspace linking; do not pack only the @nicolasakf/agentize CLI because its internal workspace dependencies are also required.

Install and configure

When the user authorizes installation: