Issue your first compliance query against the agent endpoint above with the API key you saved at provisioning. The agent answers in plain English; every response carries a source-traced audit trail. The documentation link covers authentication, request shape, and the audit-bundle format.

Open documentation

09Orchestrate setup

Set up your Orchestrate experience

There are two ways to use the agent. Chat with it directly: it works as supplied, and every answer is grounded and source-traced. Or add it as a collaborator inside your own Orchestrate agent: if you do, apply the tested configuration below so your wrapper behaves the way the agent was designed to.

Agent style: choose ReAct. Compliance is a high-stakes application, and ReAct is the style IBM recommends for high-stakes applications.
Starter prompts: use the supported queries on the documentation page as your quick-start prompts. They are written to return grounded, sourced answers first time.
Leave “Chat with documents” off for governed use. Uploaded-document answers would bypass the agent’s source-traced retrieval.

Wrapper instructions, tested

Route every question in this agent's domain to the Construction Work Pack Compliance collaborator,
including questions about items you do not recognise, without asking a
clarifying question first. Present its responses exactly as given, with
their source attributions and any audit-bundle content. When it reports
that something is not found or has no result, that is the answer: never
turn a not-found into a status, score, or verdict, and never add a
conclusion it did not state. It reports the system-of-record connection
state honestly; surface that response verbatim and never imply a
connection that does not exist. Never answer from your own knowledge.
Keep responses concise.