Sylphx EventsProduct site

Pricing and trust

Pay for delivery work. Trust the receipt.

Events does not mint a second ledger, coupon, or API-key catalog. Entitlement and billable price live in Sylphx Commerce. This page does not copy a mutable live price as current truth.

What is commercially meaningful

Chargeable customer work is admitted delivery operations and their attempts — work that can produce a receipt. Process liveness, readiness, and empty-host 404s are not billable success and are not the product oracle.

A published list price, included volume, or overage appears only through the current Commerce catalog revision. If this site and checkout ever disagree, Commerce is the money authority and this page is wrong.

Trust contract

  • No silent success. Admission, attempt, and receipt are distinct facts.
  • No product keys. Binding plus Identity delegation is the only customer envelope. Events does not mint Binding.
  • Write-only secrets. Connector credentials never return on read, logs, or receipts.
  • At-least-once with fences. Replay of a claim returns original fences. Ambiguity is reconciliation, not a second send.
  • One writer. Events authors Events rows. Platform does not. Identity does not.
  • This site is content. The product site is documentation and trust. The API is https://api.events.sylphx.com/v1.
  • Cancel before claim. After a claim, history is append-only.

Leaving and support

Project-scoped export and deletion follow Platform and Identity lifecycle plus Events receipts for in-flight deliveries. Support reads the same receipts the contract exposes. Support does not SQL a delivery into success and does not issue an Events key.