Loading…
Docs-Led Customer Use Case
CoolDeal completed Decionis onboarding from the API docs alone
CoolDeal's Swarm is an agentic micro-SaaS product for deal discovery, charge recovery, and logistics coordination. The first Decionis wedge was the Resolve pillar, where governed decisions sit directly in the path of disputes, recovery, and operational actioning.
The important signal is not just that the integration worked. It worked from the public API docs and zero-config flow alone: sponsor verification, mapping session, sample upload, bundle issuance, and callback registration without turning the motion into a Decionis services engagement.
Launch Snapshot
Docs only
Resolve · swarm_resolve_gate
- CoolDeal completed onboarding from the Decionis API docs alone. No Decionis dashboard handoff or custom operator path was required.
- The Resolve pillar workflow `swarm_resolve_gate` was created, uploaded, confirmed, and bundled through the self-serve public onboarding flow.
- The callback integration was also registered in the same motion, proving that docs-led onboarding can cover both ingress and governed callback delivery.
The Hunt
CoolDeal's Swarm hunts for better marketplace prices and routes live opportunities into the operator's preferred channel.
The Resolve
Its Resolve pillar focuses on billing disputes, charge recovery, and tracked recovery outcomes with an audit trail.
The Bridge
The Bridge coordinates real-world pickup, delivery, and logistics work where proof of completion matters.
What completed live
1. Verify the sponsor and capture the onboarding grant
CoolDeal started through the public register and verify flow, then moved straight into the mapping session using the returned onboarding grant.
2. Switch to a flat onboarding sample
Using `sample_events_flat.jsonl` kept the first-run mapping simple and removed unnecessary nested payload ambiguity during setup.
3. Issue the deployment bundle
Decionis returned the org API key, connector ID, webhook secret, webhook URL, and policy version through the standard deployment-bundle route.
4. Register the outbound callback
The callback destination was registered through the first-class `WEBHOOK` provider, keeping the Resolve workflow self-serve from ingress through decision delivery.
Why this matters for future partners
Docs as product surface
The public API docs are now strong enough to carry a real partner from OTP verification to live bundle issuance and callback registration.
Flat-sample first run
A flat event sample is the best first-run reference path. Partners can still map nested events later, but flattening the first sample reduces onboarding drag.
Minimal runtime contract
CoolDeal only needed the deployment bundle env set plus an optional callback secret, which keeps integration setup clear and repeatable for future partners.
Workflow onboarded
Resolve was onboarded first, which is the right wedge for dispute and charge-recovery operations before expanding into hunt or logistics workflows.
No probe-file dependency
Temporary probes and secrets were removed after validation, which means the final path is a clean contract rather than a debugging artifact.
Reference path for new partners
CoolDeal now serves as the clearest example of zero-onboarding through the API docs alone, not a consulting-led implementation path.
The product signal for buyers
CoolDeal proves a stronger product claim than a guided pilot: a new partner can use the public API docs, a flat sample, and the zero-config workspace contract to get through onboarding without a bespoke implementation track.