Quickstart: first event in minutes

This walkthrough ships one signed event from your machine to your organization's Provantix database and confirms it landed.

Prerequisites

  • A Provantix organization. If you don't have one, join the waitlist at provantix.tech or sign in if your organization is already provisioned.
  • Node.js 20 or later (for the SDK path) or any HTTP client (for the direct path).

Step 1: Register an emitter

Sign in at app.provantix.tech, open Setup, and click Register an emitter. The platform generates an ECDSA keypair and shows you the private key exactly once. Copy it somewhere safe; it is never stored on our side. Because Provantix generated it, a seal under this key is Provantix's own attestation rather than proof from your system, which is fine for a trial; for production, register your own key (see The emitter proof).

You can also register over the API:

curl -X POST https://app.provantix.tech/api/account/emitters \
  -H "authorization: Bearer <your session token>" \
  -H "content-type: application/json" \
  -d '{"name":"prod"}'

The response gives you emitter_id, tenant_id, the ingest endpoint, and the one-time private_key_pem.

Step 2: Send your first event

With the Node.js SDK (recommended for real agents):

npm install @provantix/agent-sdk
import { AgentEmitter, buildAAR } from '@provantix/agent-sdk';

const emitter = new AgentEmitter({
  emitterId: 'emi_01m…',
  tenantId: 'ten_org_01m…',
  privateKeyPem: process.env.PRIVATE_KEY.replace(/\\n/g, '\n'),
});

emitter.emitAAR(buildAAR({
  tenantId: 'ten_org_01m…',
  emitterId: 'emi_01m…',
  system: 'internal-tools',
  agent: { vendor: 'acme', vendorAgentId: 'support-copilot' },
  action: { type: 'execute', targetSystem: 'erp', targetEntityId: 'po-123' },
}));

await emitter.flushAndDrain('https://app.provantix.tech');
console.log('shipped');

With plain HTTP, build the batch envelope yourself (signature included) and POST it. Most teams use the SDK because it handles signing, batching and offline retries; the envelope format is documented in POST /v1/batches.

Step 3: Confirm it landed

In the app, open Investigate. Your event appears within seconds, chained and attributed. If you created a matching agent record (same vendor + vendor_agent_id), attribution confidence is 0.95 by explicit platform id; otherwise the record is stored as unknown and surfaces in Candidates for you to claim.

The Setup page also shows per-emitter counters: records shipped and batch sequence, so you can watch the pipeline move after every flush.

What's next