Emitters and keys
An emitter is a signing identity for one agent service. This page covers registration, key handling, rotation and revocation.
Registration
Register from the app's Setup page or over the API (see Account and emitter API). The platform generates an ECDSA P-256 keypair and returns the private key once, in the response. It is never stored; if you lose it, rotate to a new emitter. Because Provantix made the key, proof under it is only Provantix's own attestation; to make it independent, register your own key instead (see The emitter proof).
You can also bring your own key (BYOK): generate a keypair locally with the SDK's AgentEmitter.generateKeys() (or openssl ecparam -genkey -name prime256v1), and register only the public key. The private key then never touches our systems at all.
import { AgentEmitter } from '@provantix/agent-sdk';
const keys = AgentEmitter.generateKeys();
// keys.publicKeyPem → paste into the registration dialog
// keys.privateKeyPem → keep in your own secret store
Why signatures instead of tokens
Batches authenticate by ECDSA signature. The control plane verifies the signature against the public key recorded at registration before anything is stored. A leaked emitter id is useless without the private key, and a tampered batch is rejected at the edge. No bearer token travels with your telemetry.
Rotation
Rotation is register + revoke:
- Register a new emitter.
- Deploy its key to the agent service.
- Revoke the old emitter (Setup page, or
DELETE /api/account/emitters/:id).
Ingest rejects revoked emitters with 403 immediately. Historical batches stay verifiable because the public key and the signed batches are retained.
Deleting a revoked emitter
A revoked emitter that never shipped a batch can be fully deleted (Setup page shows a Delete button, or DELETE ...?purge=1). Deletion removes the registration, its connector row and the routing mapping. It is refused with 409 if any batch exists: shipped batches are signed, hash-chained evidence, and the registration row is what keeps them verifiable.
Operational guidance
- One emitter per service and environment. Don't share an emitter across prod and staging; shared signing identities blur the evidence chain exactly where you need it sharp.
- Store private keys in your secret manager, not in code or CI logs.
- Spool directory (SDK) is local state: point it at a persistent volume so an offline agent can drain queued batches after restart.