GET /lotes

The /lotes endpoints give you read and write access to the informes_lotes and lote_historial tables in the AgroIA PostgreSQL database. The two GET endpoints require no authentication, making them suitable for dashboards and monitoring tools. The DELETE endpoints require Bearer token authentication and are irreversible — deleted data cannot be recovered.

Returns a summary of every lot registered in informes_lotes, ordered alphabetically by lote_id. No authentication required.

Response

total

integer

Total number of lots in the database.

lotes

array

Array of lot summary objects.

Show lotes item fields

lote_id

string

Unique lot identifier.

cultivo

string

Declared crop for the lot (e.g. maiz, soja, trigo, girasol). May be null if not set.

score_total

number

AgroIA Score (0–100) combining Vigor, Stability, Cleanliness, and Climate components. May be null for newly ingested lots awaiting pipeline enrichment.

ndvi_promedio

number

Average NDVI value at the critical growth window for the declared crop. May be null.

fecha

string

Report date in YYYY-MM-DD format. May be null.

superficie_ha

number

Lot area in hectares. May be null.

Example

curl http://localhost:8000/lotes

Response

{
  "total": 26,
  "lotes": [
    {
      "lote_id": "INTA_PIVOTE_001",
      "cultivo": "maiz",
      "score_total": 81.4,
      "ndvi_promedio": 0.72,
      "fecha": "2025-11-15",
      "superficie_ha": 48.3
    },
    {
      "lote_id": "POLIGONO_1",
      "cultivo": null,
      "score_total": null,
      "ndvi_promedio": 0.0,
      "fecha": "2026-05-12",
      "superficie_ha": null
    }
  ]
}

GET /lotes/

Returns the full consolidated informe and the paginated historical series for a single lot. No authentication required.

Path parameters

lote_id

string

required

The unique identifier of the lot to retrieve. Must match a value in informes_lotes.lote_id.

Query parameters

limit

integer

default:"5"

Maximum number of historical year records to return from lote_historial, ordered by anio ascending.

Response

lote_id

string

The requested lot identifier.

informe

object

Consolidated agronomic report for the lot.

Hide informe fields

integer

Database primary key from informes_lotes.

fecha

string

Report date in YYYY-MM-DD format.

ndvi_promedio

number

Average NDVI value (0.0–1.0).

gdd_acumulados

number

Accumulated growing degree days.

score_total

number

AgroIA Score (0–100).

cv_espacial

number

Coefficient of spatial variation of NDVI — the inverse of this value contributes to the Stability score component.

cultivo

string

Declared crop type.

superficie_ha

number

Lot area in hectares.

metadata

object

Full JSONB metadata stored during ingestion, including zonificacion_activa, puntos_zona_c, and any extra fields provided by the pipeline.

historial

array

Historical year records from lote_historial, limited to limit rows.

Show historial item fields

anio

integer

Year of the record (ASCII key — no accented characters).

cultivo

string

Crop grown that year.

ndvi_critico

number

NDVI at the critical growth window for the crop.

horas_calor

number

Accumulated heat hours computed with the sinusoidal NASA POWER formula.

score_total

number

AgroIA Score for the year (0–100).

score_vigor

number

Vigor component (40% weight).

score_estabilidad

number

Stability component (30% weight).

score_limpieza

number

Cleanliness component (20% weight), based on IsolationForest anomaly filtering.

score_clima

number

Climate component (10% weight).

valido_para_score

boolean

Whether this year’s data passes validation and is included in score computation.

Examples

# Get lot with default 5 history records
curl "http://localhost:8000/lotes/INTA_PIVOTE_001"

# Get lot with up to 10 history records
curl "http://localhost:8000/lotes/INTA_PIVOTE_001?limit=10"

Response

{
  "lote_id": "INTA_PIVOTE_001",
  "informe": {
    "id": 7,
    "fecha": "2025-11-15",
    "ndvi_promedio": 0.72,
    "gdd_acumulados": 1450.5,
    "score_total": 81.4,
    "cv_espacial": 0.12,
    "cultivo": "maiz",
    "superficie_ha": 48.3,
    "metadata": {
      "zonificacion_activa": true,
      "puntos_zona_c": 3
    }
  },
  "historial": [
    {
      "anio": 2023,
      "cultivo": "maiz",
      "ndvi_critico": 0.68,
      "horas_calor": 1380.0,
      "score_total": 78.2,
      "score_vigor": 32.1,
      "score_estabilidad": 24.5,
      "score_limpieza": 15.8,
      "score_clima": 5.8,
      "valido_para_score": true
    }
  ]
}

DELETE /lotes/

Deletes a single lot and all of its historical records. Removes rows from both informes_lotes and lote_historial. Requires Bearer token authentication.

Path parameters

lote_id

string

required

The unique identifier of the lot to delete.

Response

status

string

Always "deleted" on success.

lote_id

string

The deleted lot identifier.

historial_eliminado

integer

Number of rows deleted from lote_historial for this lot.

Example

curl -X DELETE http://localhost:8000/lotes/TEST_LOTE_99 \
  -H "Authorization: Bearer your_secret_key"

DELETE /lotes

Deletes all lots from informes_lotes and all rows from lote_historial. This operation is irreversible. Requires Bearer token authentication.

This endpoint empties both tables entirely. There is no confirmation prompt and no rollback. Use only in development or when a full database reset is intentional.

Response

status

string

Always "cleared" on success.

lotes_eliminados

integer

Total number of lots that were deleted from informes_lotes.

Example

curl -X DELETE http://localhost:8000/lotes \
  -H "Authorization: Bearer your_secret_key"

REST API

Python Modules

GET /lotes — query and delete lot records

GET /lotes

Response

Example

GET /lotes/

Path parameters

Query parameters

Response

Examples

DELETE /lotes/

Path parameters

Response

Example

DELETE /lotes

Response

Example

Build docs developers (and LLMs) love

REST API

Python Modules

Documentation Index

​GET /lotes

​Response

​Example

​GET /lotes/

​Path parameters

​Query parameters

​Response

​Examples

​DELETE /lotes/

​Path parameters

​Response

​Example

​DELETE /lotes

​Response

​Example

Build docs developers (and LLMs) love

GET /lotes

Response

Example

GET /lotes/

Path parameters

Query parameters

Response

Examples

DELETE /lotes/

Path parameters

Response

Example

DELETE /lotes

Response

Example