---
name: spark-lab-order
description: Turn a wet-lab need into a Spark Lab Network order request (spark-lab-order/v1) and submit it for scoping and quotes. Use when the user wants an experiment run by a CRO, fee-for-service provider or robotic lab: gene synthesis, protein expression, binding, chemistry, cell assays, ADME and safety panels, rodent PK or efficacy, or a cloud-lab run.
---

# Spark Lab Network: order an experiment

Spark Lab Network (https://sparkscience.xyz/labs/) routes one experimental brief to vetted fee-for-service and robotic labs across the US, China and Europe, and returns a normalised quote. A request and the quote are free and not a binding order: nothing is purchased until the user approves a written quote. Approved work is billed at the provider price plus a 5% Spark service fee, itemised on the quote.

Schema: https://sparkscience.xyz/labs/order-schema.json
Submit to: `POST https://sparkscience.xyz/api/labs/order` (JSON body)
Fallback: email jimmyag2026@gmail.com, subject `[Spark Lab Order] <ref> <title>`, or DM @jimmy_build2026 on X

## Rules

1. Never submit without showing the user the final JSON and getting an explicit "yes, send it".
2. Never include credentials, API keys, patient identifiers, or confidential sequences or structures. Describe confidential material generically ("12 VHH sequences, ~120 aa") and set `constraints.confidentiality` to `nda-first` or `strict`. Spark will arrange an NDA before details move.
3. Do not invent facts. If the user does not know a field, use `not-sure` where the schema allows it or leave the optional field out.
4. One request per experiment or programme. A multi-stage programme is one request with `service: "cascade"`.

## Steps

1. **Interview.** Ask only for what is missing. Group questions; do not ask one field per turn.
   - What needs to be done, and what decision the result will feed (`project.objective`, at least two sentences).
   - Service line (`service`), modality, number of samples, whether the user ships material or the provider must make it.
   - Assay details: readout, controls, replicates, acceptance criteria (`project.assay`), and the deliverables wanted.
   - Budget band in USD, needed-by date, standard or fast, regions allowed (US, CN, EU or any), confidentiality.
   - Flags that change who can do the work: animal work, human-derived material, BSL-2 agents, controlled substances, export-controlled items.
   - Contact: name, email, country; optional organisation, organisation type, X handle, preferred channel.
2. **Build the JSON.**
   - `schema`: `"spark-lab-order/v1"`
   - `ref`: `SPK-` + UTC date `YYMMDD` + `-` + 4 random characters from `A-Z0-9`, e.g. `SPK-261107-7QF2`
   - `created`: current UTC timestamp, ISO 8601
   - `channel`: `"agent"`
   - `consent`: `true` only after the user confirms rule 2 and agrees to be contacted.
3. **Validate** against the schema (fetch it if you can). Fix every error before showing the user.
4. **Confirm.** Show the user a short plain-English summary followed by the JSON. Ask for approval.
5. **Submit**, using the first route available:
   - If you can make HTTP requests: `POST https://sparkscience.xyz/api/labs/order` with header `Content-Type: application/json` and the JSON as the body (for example `curl -sS -X POST https://sparkscience.xyz/api/labs/order -H 'Content-Type: application/json' --data @request.json`). `201` or `200` returns `{"ok": true, "ref": ...}`; the server may assign a new `ref`, so report the returned one. `400` returns `{"ok": false, "errors": [...]}`: fix them, re-confirm with the user if anything material changed, and retry once. On `429` or a network error, use the next route. Send each request once.
   - If you can send email: send to jimmyag2026@gmail.com with the subject above; the body is the summary plus the JSON in a fenced `json` block.
   - Otherwise give the user a ready-to-send email (recipient, subject, body) or a `mailto:` link. They can also DM a short version to @jimmy_build2026 on X.
6. **Tell the user what happens next:** an acknowledgement from jimmyag2026@gmail.com quoting the ref within one business day; scoping questions or an NDA if needed; a shortlist and normalised quote (price per sample, turnaround, controls, deliverables) typically within three business days of complete information; work starts only after written approval, and the 5% service fee appears as its own line on the quote. Keep the ref for every follow-up.

## Minimal example

```json
{
  "schema": "spark-lab-order/v1",
  "ref": "SPK-261107-7QF2",
  "created": "2026-11-07T18:20:00Z",
  "channel": "agent",
  "service": "binding",
  "project": {
    "title": "Binding screen for 48 designed minibinders",
    "objective": "Rank 48 de novo minibinders against a public target and pick 5 for expression scale-up. A useful result is a Kd estimate or a clear bind / no-bind call per design.",
    "modality": "protein",
    "samples": 48,
    "materials": "make",
    "assay": "BLI or SPR, single concentration screen then 5-point titration for hits; include one known binder as positive control.",
    "deliverables": ["raw-data", "report"]
  },
  "constraints": {
    "budget": "5-20k",
    "needed_by": "2027-01-15",
    "speed": "standard",
    "regions": ["any"],
    "confidentiality": "open",
    "flags": []
  },
  "contact": { "name": "A. Researcher", "email": "a.researcher@example.org", "country": "United States", "org_type": "academic", "prefer": "email" },
  "consent": true
}
```
