Designed scope
- provider-neutral adapter
- usage limits and audit
- role-authorized context
Planned product · enquiries only
RDCopilot Copilot
Assistance limited to an agreed use case and data policy.
01 / Workflow
From intent to a verifiable trail
A user starts a bounded task; the adapter applies policy, records cost, and grants no additional access.
Every operation retains company identity, actor, and source linkage.
Acceptance requires tests against the actual authorized version, integration, and data.
02 / Scope
Capabilities and boundaries
Not yet validated
- Provider, key and use case are not approved.
- External usage cost belongs to the customer and is not implicitly included.
03 / API
Controlled integrations
Connections use authenticated APIs and durable events. Single sign-on does not replace data synchronization, and each service retains its declared authority.
- Product APIs
- Identity
- LLM provider
04 / Docs
Public integration notes
Working contract
Commands require an idempotency key, legal company, actor, source, and timestamp. Corrections use linked reversals and never silently rewrite history.
Access and availability
There is no validated application entry yet. The /app route does not redirect until origin, path, license, and release evidence are approved.
Price and inclusions
No price is published. Commercial, tax, refund, and support policies are unapproved; this page supports enquiries only.
05 / FAQ
Factual answers
Is the product available now?
No. Its status is planned and the offer is enquiry-only.
Can I purchase online?
No. There is no approved price or checkout.
What does this page prove?
It describes planned public scope and its boundaries; it does not prove production availability, certification, or acceptance.