✣PollinationTechOPEN INFRASTRUCTURE
POLLINATIONTECH OPEN / PUBLISHERS

Identity travels
with the data.

Each organization gets its own publisher identity and scoped API key. The server binds that identity to every accepted observation so clients cannot impersonate another publisher by editing JSON.

01 / MODEL

Publisher → Key → Record

01PUBLISHER

Stable slug, name, website, active state, and optional contact metadata.

02API KEY

Hashed at rest, labeled, revocable, scoped, and associated with exactly one publisher.

03INGESTION

POST /observations authenticates the key before accepting the record.

04ATTRIBUTION

The server overwrites publisher provenance with the authenticated organization identity.

02 / ADMINISTRATION

Simple command-line provisioning.

python publisher_admin.py create-publisher \
  --slug example-university \
  --name "Example University"

python publisher_admin.py create-key \
  --publisher example-university \
  --label "field-research-2026"

The plaintext API key is shown once. Only its SHA-256 hash is stored.

03 / SCOPE

Start narrow.

Version 0.3.0 supports the observations:write scope. The model is intentionally ready for narrower future scopes such as dataset administration, publisher metadata, moderation, or read access to restricted records.

Public map/explorer endpoints still hide records marked private.

SYNTHETIC PUBLISHER DIRECTORY

See the publisher model in practice.

SYNTHETIC DEMONorth Country Field Lab

Hive telemetry + crop visitation

SYNTHETIC DEMOOrchard Sensing Collaborative

Computer vision + pollen transfer

SYNTHETIC DEMOPrairie Pollination Network

Sunflower visitation + weather context

SYNTHETIC DEMOPollinationTech Demonstration

Schema examples + interoperability