Two different jobs, two separate scopes
MCP is an interface that lets supported agent tools use a connected service. The value depends on the material the tools can retrieve and the work they are permitted to do.
Read-only reference pilot
ACD Knowledge Access
For practitioners and teams who want attributable ACD references in their agent tools. The proposed pilot starts with one curated, versioned collection of public or licensed material cleared for that customer.
- Search summaries and read selected references with their source, version, evidence standing, and limits.
- Evaluate relevance, traceability, response size, and usefulness on agreed practice questions.
- Discuss a workspace subscription with a defined usage allowance, maintained references, release notes, and support.
This pathway would not operate customer systems or include the full research estate. It does not automatically grant redistribution or consulting-delivery rights.
Request ACD knowledge pilot accessScoped operations evaluation
Parallax Operations Access
For organizations that need supported agent operations in a bounded customer environment. The proposed pilot begins with observation of permitted project, decision, and operational records.
- Inspect one workflow with a named operator, reviewer, and agreed evidence of fit.
- Consider individual actions only after permissions, isolation, logs, and recovery have been verified.
- Discuss setup plus workspace or deployment and support subscriptions, with explicit usage costs.
Operations access requires its own scope and validation. Internal connectivity does not establish a customer-ready hosted service or authorize actions in your environment.
Request a Parallax operations evaluationBring a useful task and an accountable owner
For knowledge access, bring the questions your team needs to answer, the agent tools you use, and your intended use of the material. For operations access, also identify the workflow owner, technical operator, customer environment, data boundaries, and actions you want to evaluate.
The scope should name supported clients, included collections or tools, onboarding, hosting responsibility, usage allowances and metering, data handling, updates, and available support. Backup and recovery responsibilities, record export, cancellation, and access revocation must also be clear before a paid pilot begins.
Pricing follows scope and support capacity. Neither pathway offers immediate connection or unlimited usage.
What must be demonstrated before access
Knowledge stays within the agreed collection
Pilot checks must show separation between customer accounts, denial after access is revoked, exclusion of restricted content, source attribution, bounded retrieval, and clear behavior when a query fails.
Actions stay within current authority
Operations checks must additionally show denial across workspace boundaries, refusal of stale or revoked authority, action logs, safe handling of duplicate requests and retries, recovery, and owner intervention.
These are pilot readiness requirements, not claims that every proposed service or deployment has passed them. Customer environments must be isolated from Build TBD’s internal records and other customers.
Leave the pilot with an adoption decision
Agree the closeout outputs before starting: a record of the tasks evaluated, useful results and failures, measured usage and support burden, known limitations, and a recommendation to continue, revise, or stop.
Knowledge-access review focuses on useful, traceable answers. Operations review also covers authority, intervention, and recovery in the agreed environment. Continuing service depends on demonstrated fit and a separate agreement.
Explore the Parallax operating approachCompare use rights and support
