Subscribe to every metering and settlement event.

What you can do

• Subscribe any HTTPS endpoint with a per-destination signing secret.
• Verify each request with HMAC-SHA256 over the raw body — header is x-paid-signature.
• Filter by event type, function, or tenant when you only care about a subset.
• Inspect every delivery: request body, response status, retries, and timing.
• Automatic retry with exponential backoff on 5xx and network errors.

Event types

• compute.completed

  A pricing call ran. Includes the metering breakdown.

• compute.failed

  A pricing call failed. Includes the routed function and error.

• signal.created

  A new anomaly signal was detected.

• invoice.created

  A new invoice is ready for the tenant.

• invoice.paid

  A tenant paid an invoice.

• dispute.opened

  A dispute was opened against a compute charge.

• function.published

  A function was published or updated in the marketplace.

Verify a delivery

import crypto from "node:crypto"

export function verifyWebhook(rawBody: string, header: string, secret: string) {
  const expected = crypto
    .createHmac("sha256", secret)
    .update(rawBody)
    .digest("hex")
  // Constant-time compare to avoid timing leaks.
  const a = Buffer.from(expected, "hex")
  const b = Buffer.from(header, "hex")
  return a.length === b.length && crypto.timingSafeEqual(a, b)
}

// In your route handler:
const ok = verifyWebhook(rawBody, req.headers["x-paid-signature"], process.env.WEBHOOK_SECRET)

The signature is HMAC-SHA256 over the raw request body — not the parsed JSON, and no timestamp. Use a constant-time compare to avoid timing attacks. See packages/security/webhook.ts for the canonical implementation.