Framework, package manager, deployment boundary, environment conventions, CI, audit patterns, existing TECRID code, organization role, and source system.
Agent-guided onboarding
Open the repo.
Type integrate.
The public TECRID Connect repository contains instructions for Codex and Claude Code, a machine-readable role manifest, a read-only preflight, the API client, MCP tools, LIMS starter profiles, and a required completion report.
Four steps
The shortest safe path from repository to working connection.
- 01Open both codebases
Give the coding agent access to TECRID Connect and the portal, LIMS connector, or service that will receive the integration.
- 02Select maximum capability
In Codex, use GPT-5.6 Sol with max reasoning when available. In Claude Code, choose the highest-capability coding mode exposed to your account.
- 03Type “integrate”
The agent reads
AGENTS.mdorCLAUDE.md, inspects the stack, and asks once for any role, target, or LIMS fact it cannot discover. - 04Review the receipt
The agent implements and tests the connection, then creates
TECRID-INTEGRATION-REPORT.mdwith verified work, open human gates, and rollback steps.
What the agent does
Discovery, implementation, validation, and a durable handoff.
The checked-in instructions make “integrate” a defined workflow rather than a vague prompt.
Secret placeholders, typed client, role-specific APIs, native audit storage, structured errors, retries, and integration tests.
Public API health, local checks, target tests, authorization behavior, failure handling, and the exact boundary between completed work and human approval.
Files changed, events and endpoints connected, checks actually run, human gates, deployment approval, rollback, and a no-secrets-in-source attestation.
Role-aware setup
One trigger. Four bounded outcomes.
Laboratory
Maps the controlled LIMS release event, report template, final-PDF fingerprint, canonical signature, finalization, audit trail, and failure tests.
Brand or supplier
Connects the evidence portfolio, SKU-specific laboratory routing, recipient permissions, historical-report intake, and optional public profile.
Retailer or certifier
Connects scoped requests, intake, authority validation, frozen version receipts, exception handling, and portfolio monitoring.
Government program
Uses the same recipient boundary while preserving program-specific reliance rules, access limits, and append-only submission evidence.
Deliberately not automated
The agent handles implementation. People retain authority.
- IdentityA person signs in, creates or selects the organization, and completes any issuer or program verification.
- SecretsA person places the TECRID API key and any laboratory signing key into approved custody. Keys are never requested in chat.
- Release authorityA laboratory owner approves the mapped release event; a brand approves disclosures; a recipient approves its reliance rules.
- ProductionDeployment and the first production write require explicit approval after the integration report is reviewed.
Start free
Create the workspace first—or let the agent build until it reaches the credential gate.
TECRID account creation, public resolution, laboratory verification, and the founding pilot are free.