Lab go-time pack · sandbox first

If your laboratory says GO tomorrow, start here.

Run a sandbox issuance, authenticate a test API call, and exercise the candidate VLE sample-link contract today. Production authority remains locked until the laboratory passes every issuer-verification gate.

Create a laboratory sandbox key →Create the real lab workspace →

The object

A TECRID is the record—not a label pasted onto a file.

A TECRID is a persistent identifier for a laboratory-issued, structured, signed, and versioned report record. It binds issuer identity, findings, sample context, document fingerprint, status, and lifecycle history to a resolvable registry entry.

PDF/COA ≠ TECRIDA PDF or Certificate of Analysis does not become a TECRID merely because an identifier or badge appears on it. The authenticated laboratory must finalize the canonical registry record.

Mint and authenticate

From released result to maintained evidence.

Correction and revocation do not erase an issued record. They append traceable status history. If replacement evidence receives a new TECRID, every downstream system must explicitly bind and evaluate the replacement.

01
Reserve
Reserve the persistent identifier before the final report is rendered.
02
Render
Print the TECRID and resolver URL on the laboratory-controlled report template.
03
Fingerprint
Bind the exact final document to structured results, methods, dates, sample identifiers, lot or SKU context, and the source-document hash.
04
Sign
Sign the exact canonical UTF-8 payload with the verified laboratory Ed25519 key.
05
Finalize
Finalize the signed registry record so it can resolve, route, and later carry a correction or revocation without erasing history.

End-to-end sandbox

Request. Issue. Call. Match.

The test key is created inside your signed-in sandbox and shown once. Only its one-way hash is stored. It is limited to /api/sandbox/v1/* and cannot issue or read production records.

01
Request access and create a key
Open the laboratory role directly at API & integrations. Sign in, create a personal sandbox, and copy the tec_sandbox_… key when it is shown.
Open laboratory API settings →
02
Issue the fictional sandbox record
Use Evidence workflow to claim, confirm, and issue SBX·NORTHSTAR-26-AVO8F2C1. The fictional record has no production authority.
Run the issuance flow →

Make an authenticated test call

curl "https://tecrid.com/api/sandbox/v1/scenario" \
  -H "Authorization: Bearer $TECRID_SANDBOX_KEY"

Test the VLE sample-code match

curl --get "https://tecrid.com/api/sandbox/v1/vle-evidence" \
  -H "Authorization: Bearer $TECRID_SANDBOX_KEY" \
  --data-urlencode "tecridId=SBX·NORTHSTAR-26-AVO8F2C1" \
  --data-urlencode "expectedSampleCode=VLE-SAMPLE-AVO-260812-A"

The endpoint returns the candidate evidence envelope only after sandbox issuance and only when the expected Sample code matches.

TECRID × VLE

Link evidence to the sample. Keep the claims separate.

VLE owns the PhysicalLot, SamplingOrder, Sample, qualification profile, decision, and listing. The candidate contract asks TECRID to authenticate the evidence envelope and its laboratory-declared sampleCode; VLE then compares that value with its existing Sample before evaluation. This contract is sandbox-only today. Production schema and adapter activation require joint approval.

Request{ tecridId, expectedSampleCode }

TECRID response{ tecridId, sampleCode, issuer, status, results, payloadHash, authentication }

BoundaryA matching code links two records. It does not prove representative sampling, custody, analytical correctness, certification, or qualification.

VLE decisionVLE QUALIFIED is a separate deterministic outcome. It must never appear without authenticated TECRID-linked evidence and every applicable VLE requirement.

Open the current VLE laboratory page ↗vle.exchange laboratory page · use after domain cutover ↗

Lab says GO tomorrow

Six checks before the first live report.

01
Sandbox access
Create or sign into a personal sandbox and create a revocable tec_sandbox_… key under API & integrations.
02
Issuer verification
For production, submit legal identity, authority, competence or accreditation evidence, issuance scope, signing-key control, and conformance evidence. An account alone cannot issue live TECRIDs.
03
Configuration
Use https://tecrid.com/api/sandbox/v1 for testing. Do not configure or guess a production endpoint or secret until TECRID supplies approved production credentials.

Report payload

Prepare the currently supported report fields: sample name, product and matrix, lot or SKU, received/tested/released dates, methods, analytes, result text, units, qualifiers, detection limits, and the final document fingerprint. The VLE sampleCode remains part of the candidate handoff contract, not the live production issuance schema.

{
  "sampleName": "Organic cacao powder",
  "productSku": "CACAO-12OZ",
  "lotNumber": "C-240518",
  "matrix": "Food · Powder",
  "method": "ICP-MS",
  "receivedAt": "2026-09-05",
  "testedAt": "2026-09-06",
  "releasedAt": "2026-09-07",
  "sourceDocument": {
    "sha256": "SHA256_OF_FINAL_TECRID_MARKED_PDF",
    "filename": "final-report.pdf",
    "reportNumber": "LAB-240518"
  },
  "results": [
    { "analyte": "Lead", "resultText": "42", "unit": "µg/kg", "loqText": "10" }
  ]
}

Open the implemented reserve and finalize reference →

05
Dual ask with VLE
Ask the customer both whether this result needs a TECRID and whether VLE independent sampling has already assigned a Sample code. Reuse the exact VLE Sample code; never imply that matching a code proves sampling or chain of custody.
06
Support
Send the laboratory name, authorized contact, method family, proposed first customer workflow, and sandbox result to the Institute of Contaminant Standards.
ICS contact page ↗ · karen@paleofoundation.com

Test before production

Prove the handoff with one fictional record.

The sandbox proves integration behavior only. It does not verify a real laboratory, certify a report, grant production authority, or create VLE QUALIFIED status.

Start the lab sandbox ↗