Build with the Premely Integration SDK

Create a signed, capability-declared adapter for review by the Premely plugin directory.

What it is

The Integration SDK creates and verifies bounded Ed25519-signed adapter manifests. A manifest declares the adapter profile and requested capabilities before any directory submission can be accepted.

Why use it

Use the SDK for a provider adapter that does not belong in the browser tracker or an existing first-party connection.

Before you start

Install @premely/integration-sdk only after its current package version is publicly published.
Create and secure an Ed25519 signing key outside source control.

How to use it

1
Declare one approved profile
Choose the canonical browser, revenue, search, destination, ads, CRM or social profile that matches the evidence your adapter can prove.
2
Build the bounded manifest
Declare only required capabilities, HTTPS endpoints and safe public metadata.
3
Sign and verify
Sign the canonical manifest bytes with Ed25519 and verify them locally before submission.
4
Submit for directory review
Directory submission remains unavailable until the signed review service is deployed. A local signature test is not marketplace publication or Production acceptance.

What to expect

Capabilities are fail-closed

Unknown profiles, capabilities, algorithms, endpoint schemes and oversized manifests are rejected.

Directory publication needs review

A valid signature proves manifest integrity only. Premely review, hosted acceptance and public listing are separate required gates.

Chart behavior is inherited

An adapter must follow its approved canonical profile. It cannot create provider-specific chart calculations or infer identity.