---
name: ext-ops-panel
description: Connect Chrome extensions and web projects to Ext Ops Panel, set up hosted pages, events, feedback, the customer card endpoint, custom metrics and monitoring, place the Ext Ops Panel banner of any listed extension or AI plugin and turn on its verified author mark, and check an implementation against the current product contracts. Use it to integrate or configure Ext Ops Panel, not for general questions about Chrome development.
---

# Ext Ops Panel

Help connect a specific project to the panel and reach a result that can be verified. First find out what the user is connecting: a Chrome extension, a web project or both. Inspect the manifest, the service worker, the backend and the current project configuration; do not assume that every feature needs a server.

## Route

1. Read the [product map](references/product-map.md) to pick the features you need and to tell public Market data from the project's own data.
2. To connect an extension, follow the [practical route](references/integration.md): project, listing, hosted pages, install/uninstall links, Verify, events.
3. For custom metrics, monitoring, feedback or the customer card, open only the matching contract from the map. Before writing payload or endpoint code, check versions and fields against the OpenAPI files. In the Ext Ops Panel repository, the API sources and OpenAPI take precedence over this skill's summary.
4. To put a banner of a listed extension or AI plugin on a site or in a README, and, for its author, to make it say "Verified author", follow the [integration route](references/integration.md), "Ext Ops Panel banner and the verified author mark": any listed product can embed it at once; the mark needs a verified claim and the author's own consent. Full guide with every style, format and theme: https://extops.dev/docs/author-banners.
5. Change the project's code when the task allows it; check the manifest, the build and the observable result. Do not create fake install/uninstall/feedback events in production projects without a clear need.

## Boundaries

- Basic hosted pages and events need no backend of your own. Your own metrics need a GET endpoint; push heartbeat needs an agent or a server.
- Never put monitoring tokens or access keys into extension code, a public site or tool output. The public feedback widget key is meant for the browser; the widget identity secret (`wis_…`) is server-only. The conversation in the widget reads a visitor's history only with a valid signature from the owner's server: keep `exp` short (about an hour), and render replies as plain text.
- The customer card secret (`ccs_…`) is server-only, like `wis_…`: it lives in the configuration of the owner's server, never in page code, extension code, a repository or your output. Do not ask the user to paste it into the chat; let them put it into their server's configuration themselves. The card is requested only for verified people (a signed `identify()`), so a project without signed identity gets no card. Route: the [integration route](references/integration.md), "Customer card endpoint".
- There are **two different** heartbeat endpoints: monitoring of an extension registration and monitoring of a web project environment. Choose by project type; do not mix tokens and payloads without checking the contract.
- The feedback CRM (people, replies from the panel, the private note, the conversation in the widget, the customer card, keeping conversations with no time limit) comes with the owner's ACCOUNT plan on Indie, Studio or Fleet; a trial does not unlock it. Do not promise it on Free. Deleting a person with their messages, replies and note works on any plan. Details: the [integration route](references/integration.md), "People and replies in the panel".
- Banners: anyone can embed the banner of any extension or plugin listed in the catalog, with no account; it says "Listed on Ext Ops Panel". Only the product's verified author can make it say "Verified author", and only after they turn on "Publish me as the author" themselves. A product not in the catalog, or whose listing left its store or marketplace, gets the neutral plate (our logo only). Do not publish verification values or tokens anywhere but where the proof asks; do not add parameters, UTM tags or `rel` attributes to the banner link beyond the panel's options; do not edit the image, host a copy of it or change its `alt`. Never promise a figure on the banner: facts appear only above floors. Embedding needs nothing; verification and the mark work on every plan, including Free, with an account.
- Plan settings and limits change. Check them in the current panel or in the sources before promising availability.