Eden Logo
Hardware-Agnostic Intelligence

Optimize Greenhouse Yields Without the High Upfront CapEx.

The hardware-agnostic intelligence platform that turns data from cheap, off-the-shelf sensors into instant, actionable visual alerts.

Join Waitlist Try Live Demo
Zero Vendor Lock-in
Real-Time Ingestion
Instant Alerts

Tunnel 03-Alpha

Commercial Greenhouse

LIVE FEED
Ambient CO2
420 ppm
Optimal level
Air Temp
28.4 °C
Exceeding Limit
Humidity
62 %
Stable
Soil pH
6.5 pH
Target
Soil Nitrogen (N)
45 mg/kg
NPK Feed Cycle Active
High Temperature Warning Air Temperature exceeds 28°C threshold. Automated override ventilation sequence initiated.
Telemetry Workflow

How Data Flows Through Eden

A secure, latency-free pathway that frees growers from proprietary lock-in. Track the telemetry stream from sensor terminal to actionable screen logic.

1

Open Ingest (Input)

Purchase standard, off-the-shelf industrial sensors (RS485/Modbus) on the open market for under $150. Break free from expensive proprietary hardware lock-in.

2

Cloud Analytics (Processing)

Our flexible, hardware-agnostic cloud API ingests incoming telemetry streams with zero data lag and high-margin cloud pipeline scaling.

3

Actionable Alerts (Output)

Receive immediate visual alert overrides across an intuitive frontend interface before micro-climate fluctuations cause crop failure.

Developer-First Architecture

Built for Open Hardware Integration

Any standard 4G RTU or ESP32 edge gateway can wire up to Eden in minutes. We provide standard REST and MQTT interfaces designed for seamless telemetry ingestion without complex edge firmware requirements.

telemetry_payload.json 
{
  "device_id": "tunnel-03-alpha",
  "ambient_metrics": {
    "temperature_c": 28.4,
    "co2_ppm": 420
  },
  "soil_metrics": {
    "ph": 6.5,
    "nitrogen_mg_kg": 45
  }
}
Ingest Server: telemetry stream active
HTTP 202 Accepted
Transparent Terms

Scale Safely Without Hidden Costs

A highly optimized, high-margin software stack that allows us to pass infrastructure savings directly back to B2B growers.

Site Implementation

One-Time Setup Fee

$150 flat implementation fee

Deliverables include:

  • Remote dashboard configuration
  • Custom API endpoint token generation
  • Initial deployment data-mapping validation
Get Configured
Standard Core

Standard Core SaaS

Annual SaaS Subscription

$500 / Year (Per Tunnel)

Deliverables include:

  • High-frequency automated visual alert paths
  • Continuous time-series logging dashboards
  • Core predictive analytics engines
Subscribe to Standard Core

Eden Developer Portal

v1.2.0
Overview Authentication Ingest Errors Alerts
v1.2.0 Spec

1. Introduction & Architecture Overview

Eden is a hardware-agnostic agritech intelligence platform designed to ingest high-frequency microclimate and substrate telemetry from decentralized agricultural environments. By decoupling physical sensing hardware from live data analysis, Eden acts as an open, universal intelligence layer accepting standard JSON telemetry payloads from any compliant edge gateway.

Architecture Reality

Low-cost physical sensors deployed in greenhouses communicate via industrial fieldbus protocols (Modbus RTU over physical RS485 serial lines). Edge gateways—ranging from custom ESP32 microcontrollers to industrial 4G RTU hardware—act as on-site translators, wrapping raw serial register values into clean JSON structures and transmitting them securely over TLS to Eden's cloud endpoints.

System Data Flow Architecture

P
PHYSICAL LAYER [Soil NPK Sensor] • [Soil pH Sensor] • [Temp & Humidity Probe]
Modbus RTU / RS485 Serial Protocol
E
EDGE TRANSMISSION [Edge Gateway / ESP32 Microcontroller]
HTTPS POST with JSON & Bearer Token
I
EDEN INGEST GATEWAY [Eden Ingest API]
Stream Ingestion (Kafka / RabbitMQ)
D
DATABASE STORAGE [Cloud Time-Series Database]
Low-Latency Read Queries
V
PRESENTATION LAYER [Vercel Hosted Frontend UX Dashboard]

Quick Navigation Matrix

Section Focus Area Protocol / Method Endpoint / Header
1. Overview System Architecture & Data Flow Industrial Fieldbus to Cloud Conceptual Routing Diagram
2. Authentication Gateway Security Controls TLS 1.3 / Bearer Token `Authorization: Bearer <TOKEN>`
3. Ingest Engine Telemetry Ingest Payload Schema HTTP POST /v1/telemetry
4. Error Handling Gateway Status Codes & Validation JSON Error Primitives 202, 400, 401, 429 Status Maps
5. Alerts Engine Webhook Downstream Alert Broadcast HTTP POST Target Subscriber Webhooks

2. Authentication & Headers

All communications with the Eden API must be secured over HTTPS (TLS 1.3). Edge gateways authenticate using Bearer tokens issued via the Eden Admin Console during initial device registration. Each device token is uniquely mapped to a specific gateway profile and inherits precise telemetry ingestion scopes.

Security Warning

Unauthenticated, malformed, or poorly configured requests lacking valid cryptographic tokens will be immediately dropped at the API gateway layer to prevent denial-of-service vector escalation.

Required HTTP Headers

Request Headers 
Authorization: Bearer ed_live_dev_9a812bc3e4f50681a273b4d
Content-Type: application/json
  • `Authorization`: Specifies the authentication token type (`Bearer`) followed by a single space and the device secret token.
  • `Content-Type`: Explicitly declared as `application/json` to guarantee proper schema parsing.

3. Telemetry Ingest Endpoint

Edge gateways must serialize incoming physical sensor telemetry data into a structured JSON payload and dispatch it to the centralized telemetry ingest endpoint.

HTTP Method POST
Endpoint URL https://api.edenagritech.com/v1/telemetry

Production Payload Example

telemetry_payload.json 
{
  "device_id": "8c227db0-d790-482a-a9a3-37ee5041a9cb",
  "timestamp": "2026-06-12T09:23:45Z",
  "ambient_metrics": {
    "temperature_c": 24.85,
    "humidity_percentage": 62.4,
    "co2_ppm": 850
  },
  "soil_metrics": {
    "ph": 6.42,
    "nitrogen_mg_kg": 28.5,
    "phosphorus_mg_kg": 14.2,
    "potassium_mg_kg": 42.1
  }
}

Ingestion Field Schema

Field Key Type Req Validation Rules & Description
device_id String Yes Unique UUIDv4 identifier assigned to the edge gateway transmitter upon activation.
timestamp String Yes UTC timestamp in ISO 8601 recording measurements read at edge gateway.
ambient_metrics Object Yes Map container holding all atmospheric parameters.
.temperature_c Float Yes Canopy air temp in Celsius (Valid Range: `-40.0` to `80.0`).
.humidity_percentage Float Yes Relative humidity expressed as % (Valid Range: `0.0` to `100.0`).
.co2_ppm Integer Yes Carbon dioxide concentration in ppm (Valid Range: `300` to `5000`).
soil_metrics Object Yes Map container holding all localized substrate parameters.
.ph Float Yes Substrate potential hydrogen activity metric (Valid Range: `0.0` to `14.0`).
.nitrogen_mg_kg Float Yes Soil active Nitrogen concentration in mg/kg (Valid Range: `0.0` to `500.0`).
.phosphorus_mg_kg Float Yes Soil active Phosphorus concentration in mg/kg (Valid Range: `0.0` to `500.0`).
.potassium_mg_kg Float Yes Soil active Potassium concentration in mg/kg (Valid Range: `0.0` to `500.0`).

4. HTTP Status Codes & Response Handling

The Eden Ingest Gateway validates the incoming JSON schema structurally against the strict type and value range boundaries mapped in Section 3. All response bodies are serialized in JSON format.

202 Accepted

The payload conforms perfectly and has been safely queued for database insertion.

Response Body 
HTTP/1.1 202 Accepted
Content-Type: application/json

{
  "status": "accepted",
  "message": "Telemetry payload successfully queued for ingestion.",
  "correlation_id": "c1f71dfb-4a5f-442b-b6d4-8d4e13589b21"
}
400 Bad Request

The payload structure was malformed, failed validation checks, or contained metrics outside boundaries.

Response Body 
HTTP/1.1 400 Bad Request
Content-Type: application/json

{
  "status": "error",
  "code": "invalid_payload",
  "message": "The telemetry payload failed schema validation.",
  "errors": [
    {
      "field": "soil_metrics.ph",
      "reason": "Expected a float value between 0.0 and 14.0, received 17.2"
    }
  ]
}
401 Unauthorized

The authentication token is missing, expired, or incorrect.

Response Body 
HTTP/1.1 401 Unauthorized
Content-Type: application/json

{
  "status": "error",
  "code": "authentication_failed",
  "message": "The provided credentials are invalid or expired."
}
429 Too Many Requests

The edge gateway has breached the default ingestion rate limit frequency.

Response Body 
HTTP/1.1 429 Too Many Requests
Retry-After: 10
Content-Type: application/json

{
  "status": "error",
  "code": "rate_limit_exceeded",
  "message": "Transaction limit exceeded. Maximum allowed frequency is 1 request per 10 seconds per device_id."
}

5. Webhook Engine & Visual Alert Payloads

Eden continuously processes incoming time-series data chunks against specific vegetative threshold templates. When a core agricultural metric falls outside configured safety boundaries, the Webhook Engine bypasses slow database queues to issue an immediate, automated visual alert payload via an HTTP POST call directly to registered user subscriber target URLs.

Webhook Alert Payload Example

webhook_alert.json 
{
  "event_id": "evt_9a823b1c-8ef2-4e4b-91cc-7d8bfa2e2609",
  "event_type": "telemetry.threshold.breached",
  "created_at": "2026-06-12T09:23:45Z",
  "device_id": "8c227db0-d790-482a-a9a3-37ee5041a9cb",
  "greenhouse_id": "tunnel-02-sector-b",
  "alert_details": {
    "severity": "CRITICAL",
    "parameter": "soil_metrics.nitrogen_mg_kg",
    "measured_value": 12.4,
    "threshold_bound": "MINIMUM_WARN",
    "threshold_value": 25.0,
    "message": "Critical Low Soil Nitrogen detected inside Tunnel 02. Nitrogen level of 12.4 mg/kg is below the threshold of 25.0 mg/kg."
  }
}