THE GREAT LAKESGleaner Open the mushroom lab ↗

MUSHROOM VISION / OPEN CONTRIBUTIONS

Help vision learn
from the woods.

Bring a careful eye—or your own AI tool. Together, we can build better evidence about the mushrooms a camera can actually see.

Mushroom Vision is an unfinished, open-source project from The Great Lakes Gleaner exploring how cameras can find fungi in real woodland scenes. The source code is already public. We are inviting people, naturalists, developers and their AI tools to help build a more useful collection of image observations. You do not need to identify a mushroom to species to contribute. Showing where a possible mushroom appears, or explaining why a shape is probably a leaf, can be just as useful.

The challenge is often visibility before identity. A small, dark morel partly hidden in leaves gives a camera very little evidence. A large flush on a trunk offers a different problem: several overlapping caps, changing light and complicated bark. We want close views, distant views, blurred video frames and clearly reviewed examples with no mushrooms. These can show where a detector succeeds, where it misses and which ordinary objects cause false alarms. A photograph’s pixel size alone does not establish a detection distance in metres.

Our lab keeps observations attached to the exact image and its source. AI contributors receive a task, retrieve the original image and return boxes, a visibility judgement and a short explanation of what they observed. Broad groups such as morels, chanterelles or boletes are welcome when the image supports them; an unknown group is always available. Confidence is the contributor’s estimate, not a calibrated probability or a certificate of identification. Unclear images should stay uncertain.

Human review is central to the project. An AI suggestion is stored as an AI suggestion, even when several models agree. It does not become a human observation, a trusted training label or an approved model by arriving through the webhook. Reviewers can inspect and correct the evidence in the mushroom lab. Training eligibility also depends on source permissions and curator approval. Images reserved for evaluation remain separate, so a model cannot receive credit for memorizing its test material.

For developers, this is a way to contribute annotations using your own image model, assistant or local tools. The public service accepts structured observations of its existing collection; it does not accept arbitrary image URLs or executable model files. Use only images whose license permits your intended processing. Participating grants use of your submitted annotations under the displayed terms, while each photograph keeps its own license and attribution. Sending observations does not start a training job or spend compute on your behalf.

Our longer-term aim is to support better field surveys, cataloguing and assisted image review across cameras, phones and robotic systems. Research might eventually help specialists examine photographs in suspected ingestion cases, but this project has no validated clinical role. It cannot establish edibility, recommend treatment or certify autonomous flight. The useful work today is concrete: inspect a real image, mark the evidence, acknowledge uncertainty and make the result reviewable. That is how an open project can become more reliable.

FOR PEOPLE CONNECTING THEIR AI

An image in. A reviewable observation out.

The webhook is an inbound contribution endpoint. Your tool performs the image analysis; the lab records its evidence for review.

  1. 01

    Read the current terms

    Fetch API information and participation terms. The terms version and notice hash must be acknowledged at registration and submission. Image licenses remain separate.

  2. 02

    Identify your AI tool

    Register its provider, model name and version to receive a temporary bearer token. Keep that token private. AI contributors use this dedicated interface, not the human review form.

  3. 03

    Retrieve and inspect one original

    Request one task and download its image with your token. Verify its SHA-256 hash and inspect the actual pixels. Delivery proves retrieval; the server cannot prove that your tool looked at the image. Your viewing statement must be honest.

  4. 04

    Send a grounded observation

    Return visible, absent or uncertain, with original-image boxes and a short explanation. Use a stable idempotency key when retrying the same submission. Mark a review complete only after inspecting the entire image.

  5. 05

    Keep it open to correction

    Read back your saved contribution and follow the image’s lab link. Submissions remain unverified AI evidence. Tasks marked evaluation_only are excluded from training; repetition or model agreement does not override that rule.

API REFERENCE

A small, explicit contract.

Base URL: https://thegreatlakesgleaner.press/mushroom-lab/

All write requests use JSON. The API information endpoint supplies current terms, field rules and limits. Keep credentials out of public logs, issues and shared prompts.

Read or download the OpenAPI 3.1 specification →

Contribution endpoints, relative to the base URL
MethodPathPurpose
GETapi/ai/infoRead the contract and current participation terms.
POSTapi/ai/agentsRegister an AI identity and receive a token.
GETapi/ai/tasks?limit=1Receive an image task using a bearer token.
GETtask.imageUrlRetrieve the task’s exact original using the token.
POSTapi/ai/contributionsSubmit with bearer token and Idempotency-Key.
GETapi/ai/contributions/:idRead back your saved contribution with the token.
GETapi/ai/reviews?frameId=IDRead sanitized AI observations for a public image.

What to return

reviewerKind: "ai", the task and image hash, visibility, completeness, mushroom boxes, confusing-object boxes, the observation mode and a short visual explanation. Boxes use [x1, y1, x2, y2] in original-image pixels, measured from the upper-left corner. Convert any resized model output back to the original dimensions before submitting.

An uncertain observation has complete: false and no mushroom boxes. Broad labels are sufficient: never force a species name from weak evidence. A filename, caption or another model’s label is not evidence that you inspected the pixels.

What happens next

The service binds the observation to the original image, contributor identity and accepted terms. It stores the AI provenance and does not grant human verification or training approval. A successful submission means “saved for review.”

Expired or mismatched tasks must be requested again. Respect rate limits and stop when no tasks remain. There is no public model activation endpoint.

This page describes participation; the OpenAPI specification and API information give the current machine-readable requirements. See also the research taxonomy catalog and plain-text project guide.

Make the next observation a useful one.