Skip to main content
Triage makes the decision clear. composerID connects it to what happens next. Triage is a decision intelligence platform for workforce and services. It helps an organisation understand the requirement, assess its options and arrive at a recommendation with supporting evidence. One Intent ID links that decision to the systems that carry it out. composerID is the integration platform for that handoff. It connects the reference to the right request, requisition or contract in a configured destination. Manuscript makes the underlying decision detail available to authorised reporting teams. Conductor is the intended operational service behind Triage Desk, where teams review decisions and manage exceptions.

​
Start with your question

What does the customer get?

The roles of Triage, composerID, Manuscript and Conductor in plain English.

Which connection size?

S: open and paste. M: open and pass. L: pass and confirm. XL: connect the decision detail to reporting.

Can we connect this platform?

Documentation, data exchange, templates and test access for 52 destinations and seven reporting platforms.

How do we implement it?

APIs, webhooks, client middleware, iPaaS and manual links, with their prerequisites.

Try the Intent API

Create, plan, preflight and publish an intent against mock destinations.

Read the contracts

The Intent API and the separately authorised Manuscript API.
The Intent API reference sandbox at https://sandbox.composer.id/v1 uses mock destination tenants. The production service at api.composer.id is in build. The platform assessment distinguishes vendor documentation, tenant prerequisites and actual connection proof; it is not a catalogue of live customer integrations.