Field intelligence, routed through one gateway.

This gateway fronts management, agro, recommendation, remote sensing, alerting, notification, and platform operations APIs. Use it as the single entrypoint for docs, health, metrics, and authenticated service traffic.

Open API Docs Health Metrics

7 Primary backend domains behind Kong

64 Implemented use cases aligned in code and docs

/docs Unified OpenAPI and Swagger surface

Gateway Scope

Auth forwarding, request correlation, service routing, public docs, health probes, and shared entrypoint semantics.

Operational Notes

Public root stays informational. Authenticated business traffic remains under /api/*.

Current Docs Path

Swagger UI is served through Kong at /docs/, not through a separate host port.

Product Context

Qroplet turns parcel, season, remote sensing, weather, and alert flows into one operator-facing platform surface.

Quick Entry Points

Common operator destinations for inspection, verification, and integration work.

Swagger UIhttp://localhost:8000/docs/ OpenAPI Spechttp://localhost:8000/docs/openapi_kong.yaml Gateway Healthhttp://localhost:8000/health Gateway Metricshttp://localhost:8000/metrics

Public Gateway Links

These are the public routes currently exposed directly through Kong.

Landing Page http://localhost:8000/

Swagger UI http://localhost:8000/docs/

Health http://localhost:8000/health

Metrics http://localhost:8000/metrics

Operational Surfaces

Gateway-level checks for connectivity, telemetry, and documentation access.

Gateway Health

Public readiness surface

Use this route to confirm Kong proxy reachability and upstream health exposure.

Open /health

Metrics Stream

Prometheus scrape surface

Use this route for infrastructure-level scraping and operational visibility.

Open /metrics

API Docs

Unified public documentation

All major external API groups are discoverable through a single Swagger surface.

Open /docs/

Service-local probes

Internal-only operational paths

Service routes like /health/live and /health/ready remain internal unless explicitly routed.

Open spec

Gateway Request Flow

High-level path from client call to domain execution.

Client reaches Kong through the public gateway root or an authenticated /api/* path.

Kong applies request correlation, route matching, and auth policy before forwarding to the target service.

Domain services execute parcel, recommendation, remote sensing, alert, or notification logic.

Operators use /docs, /health, and /metrics as public inspection surfaces.

Core API Prefixes

/api/management Tenant, membership, invite, role, plan, and access management.

/api/agro Parcel lifecycle, crop plans, scorecards, climate and soil snapshots.

/api/recommend + /api/feature-store Recommendation, observations, exports, and feature sets.

/api/rs, /api/alerts, /api/notify Remote sensing, alerting, and delivery flows.

Health Notes

The gateway exposes public /health and /metrics links above. Service-local probe routes such as /health/live and /health/ready exist behind individual services and should be treated as internal operational endpoints unless explicitly routed through Kong.

Service Domains

Primary product-facing backend areas currently routed behind the gateway.

Management

Tenant structure, membership lifecycle, plan controls, role policy, and API access management.

/api/management

Agro

Parcel, parcel version, season, crop plan, scorecard, soil snapshot, and climate snapshot flows.

/api/agro

Recommendation + Feature Store

Crop suitability scoring, observation ingestion, feature sets, dataset exports, and ML model lifecycle.

/api/recommend /api/feature-store

Remote Sensing

NDVI/EVI snapshots, anomaly signals, phenology, zoning, and yield-oriented satellite workflows.

/api/rs

Alerts

Risk evaluation, rule versioning, scheduled evaluation, expiration, and retention lifecycle.

/api/alerts

Notifications

Inbox, emit, dispatch, preference, delivery attempts, and retention flows for downstream communication.

/api/notify