Capture
Receive critical revenue and access events through a stable managed endpoint.
- Provider signature verification where supported
- Idempotency and duplicate suppression
- Metadata retained separately from raw payloads
Managed proof-bearing operations
Revenue events should not disappear into dashboards.
Slops is being developed to capture critical webhooks, retry failed deliveries, replay dead letters, and issue receipts that show what happened without exposing private payloads.
Stripe first
Replay and DLQ
Receipt per action
Short payload retention
What a first pilot would prove
The first Slops product would not be another automation canvas. It would protect the revenue-event path you already depend on and leaves a trail a human can inspect.
Recover
Bounded retry, dead-letter handling, and replay for the events that missed.
- Destination response and attempt history
- Replay after endpoint fixes
- Operator-reviewed admin actions for pilot traffic
Prove
Every ingest, retry, replay, and admin action can leave a customer-scoped receipt.
- Receipt id, timestamp, action class, and evidence hash
- Public-safe verification view
- No claim that a receipt alone proves business correctness
Design-partner availability
This is a preview surface, not an online offer. Slops is not presently accepting orders through this site. A future engagement would begin with a separate signed agreement identifying the provider, scope, fees, and data terms.
Single provider, one destination, up to 100k events, weekly proof review.
- Stripe or generic webhook intake
- Replay, DLQ, and receipt demo
- Retention/deletion policy agreed before live payloads
Managed operations would follow only after pilot validation and written terms.
- Included 100k events and 10k receipts
- Usage units and operator work stated in a signed proposal
- No live payloads before retention and deletion terms are agreed
Agent Change Control and Spend Fuse attach after the revenue ledger is under pressure. That expansion path is deliberate: validate the bounded proof first, then widen the control plane.
From revenue proof to agent control
Slops is the public product surface. The private ethOS harness stays protected; customers see receipts, route boundaries, and managed operating proof.
01 / Safety Net
Protect revenue-event delivery
Hosted ingest, replay, DLQ, deletion, and proof receipts for a single-tenant pilot.
02 / Spend Fuse
Attach cost and usage controls
Meter model, runner, receipt, and operator costs against tenant-level commercial state.
03 / Agent Control
Govern agent work through receipts
Policy gates, change receipts, deploy evidence, and customer-scoped verification.