Integrations
The Chrome extension ships as a developer beta and is listed on the dashboard’s Connectors page. Checking can use the anonymous verification endpoint. Adding the opt-out field requires an API key and uses one API credit per successful image. Other connector cards show their actual status; anything marked Request is not available yet.
Chrome extension
Section titled “Chrome extension”Right-click any image on the web:
- Check AI opt-out signal — answers in a notification whether the image carries the machine-readable signal.
- Download a marked copy — uses your API key to add the standardized opt-out field and saves the returned copy to Downloads. The field is a signal, not a guarantee that every AI system will comply.
Install (public beta): download the Chrome beta package, unzip it, open chrome://extensions, enable Developer mode, choose Load unpacked, and select the unzipped folder. The production API is already configured. Open the extension’s Options only to use a local test server or add an API key for marking images. A Chrome Web Store listing is planned but is not available today.
WordPress prototype
Section titled “WordPress prototype”The repository contains a WordPress prototype, but the product currently lists this connector as Request, not available or beta. For developer testing, the prototype sends supported uploads to NoAI Shield after WordPress writes the upload and before the media item is finalized:
- JPEG, PNG, and WebP uploads up to 25 MB can be replaced by a marked copy when a valid API key is configured.
- When the API re-encodes to a different format, the file is renamed to match its real payload and WordPress metadata is updated.
- A failed API call does not block publishing: the original upload is kept and may therefore publish without the opt-out field. The failure is logged.
Developer test only: zip the plugins/wordpress/acp-protect folder from the project repository, upload it under Plugins → Add New → Upload Plugin, activate, then set the API base URL and a valid API key under Settings → NoAI Shield. An “Add opt-out signal” toggle pauses the plugin without deactivating it.
Building your own
Section titled “Building your own”These clients use the same checking and marking endpoints documented in the API reference. If you build a connector for your own stack, use the check-then-mark pattern and make API-key requirements and failure behavior explicit.