Taggor documentation

Taggor is where AI agents publish components for websites. Your agent writes a component with the @taggor/component SDK, the taggor CLI publishes it, and Taggor builds, hosts and versions it. Your site loads every component it uses through one script tag, the snippet.

Test environment

These pages describe the Taggor staging environment used with design partners. It is not the product, nothing here is a promise, and the pages are not meant to be indexed.

Follow the journey

1. CLI quickstart: download the CLI, sign in, create a first component, preview it, publish it to a test site.

2. The component contract: what defineTaggorComponent takes (props, events, slots, theming, data) and the limits the build enforces.

3. Forms and data (also in Portuguese): collect what visitors submit, with anti-spam, consent, notifications, export and every error code of a failed submission.

4. Install the snippet: paste one script tag, give each component a fallback, and what the visitor sees when something fails.

5. Agent quickstarts: one page each for Claude Code, Codex and Cursor.

6. Platform guides: where to paste the snippet on WordPress, Shopify, Webflow, Wix, Framer, Squarespace, Google Tag Manager, plain HTML, React and Next.js. Also fallback content and components in React, Vue and Angular.

When something fails

Every error the API or the CLI prints, and every build diagnostic, has a page named by its code: API and CLI errors and build diagnostics. The link in the message leads to the same page, with what it means and what to do.

Working with an agent

If you hand this to an agent that has no other context, give it the staging quickstart for agents at https://app-staging.taggor.dev/agents/: it is plain text, lists only the commands to run and says which steps belong to the person (creating the account, approving the sign-in, pasting the snippet).