Build a capability-declared adapter for Premely without bypassing Premely's canonical analytics model. The directory accepts a bounded JSON manifest and an Ed25519 signature. It stores review evidence only; Premely never downloads or executes third-party adapter code from a submitted manifest.
- Browser code may declare only the public tracker capability profiles.
- Revenue, advertising, CRM and social evidence must still enter through the corresponding authenticated Premely provider APIs.
- A directory approval does not make provider data chart-safe. Every output remains subject to the canonical chart, identity and linkage contracts.
- Private keys stay with the publisher. Submit only the public key and detached signature.
import { signManifest, validateManifest } from "@premely/integration-sdk";
const manifest = validateManifest({
schema_version: 1,
id: "example-browser-adapter",
name: "Example browser adapter",
version: "1.0.0",
publisher: {
name: "Example",
url: "https://example.com",
support_email: "support@example.com"
},
profile: "browser-tracker",
capabilities: ["pageview", "custom-event"],
documentation_url: "https://example.com/premely",
package_url: "https://registry.npmjs.org/example-browser-adapter/-/example-browser-adapter-1.0.0.tgz"
});
const signature = signManifest(manifest, process.env.ADAPTER_SIGNING_KEY_PEM!);Submit the manifest, public key and signature to
POST /api/v1/plugins/directory. Premely validates and records the submission
as pending_review; publication remains an explicit Premely review action.
@premely/integration-sdk is the official Premely adapter SDK, published by
Premely under the MIT licence.