UZEmarkets · DevPartner

The technical bridge for UZEmarkets data partners

UZEmarkets cannot depend on partner APIs staying online. This portal is the standardized way for our data partners — ADV Americas, BDCS and Effatha — to push spatial, soil, feedlot and agrotechnical data into the UZEmarkets A/D/R pipeline, and the public reference for how that data is validated, cached and consumed.

Language: en · pt-BR · es · pt-PT

How it works

1 · Public knowledge base

Documentation, diagrams and the OpenAPI specification — open to anyone, in English, Brazilian Portuguese, Spanish and European Portuguese.

2 · Gated REST ingestion

Partners push JSON payloads to the ingestion endpoint with a Bearer token (API key). Each token maps to exactly one partner, and every payload is validated against that partner's published JSON schema.

3 · The Snapshot Pattern

Every accepted payload lands in a staging area for engineering review. Once approved, it is timestamped and permanently cached in our ProviderSnapshot store. Lenders and our AI agents — GIRA (A N R & D) and SURA (HiCRE) — query our database, never the partner's API — so the market keeps working when a partner is offline.

Partner status

Every partner is UNVERIFIED until an agreement is signed and its API is reviewed. Snapshots are stored as partner-claimed data with provider status UNVERIFIED; a snapshot never triggers financing, treatment or auction execution on its own.

Ingestion API

Endpoint: POST /api/v1/partners/ingest

Authentication: Authorization: Bearer <API key>. The key identifies the partner; a payload whose partner_id does not match the key's partner is rejected.

Responses

`202`	Accepted — payload staged for review, staging_id returned
`401`	Missing or unknown API key
`403`	Key's partner does not match payload partner_id
`422`	Payload failed schema validation
`503`	Ingestion not configured on this deployment

Partner schemas

One schema per partner, version-controlled with this portal. Payloads that do not validate are rejected — nothing is silently repaired.

ADV Americas

Natural resources & agriculture — soil chemistry, ZARC climate risk, spatial mapping.

Schema: partners/schemas/agro-digital.json

Example payload:

{
  "partner_id": "AGRO_DIGITAL",
  "polygon_id": "BR-MT-36400",
  "geojson_polygon": {
    "type": "Polygon",
    "coordinates": [[[-56.1, -12.5], [-56.0, -12.5], [-56.0, -12.4], [-56.1, -12.4], [-56.1, -12.5]]]
  },
  "soil_profile": {
    "ph_level": 5.8,
    "nitrogen_ppm": 12.4,
    "phosphorus_ppm": 8.2,
    "potassium_ppm": 45.0,
    "organic_matter_pct": 2.1
  },
  "crop_suitability": {
    "crop_type": "CORN_SILAGE",
    "yield_potential_tons_per_ha": 14.5,
    "zarc_risk_score": "LOW"
  },
  "attestation": {
    "provider_timestamp": "2026-11-08T14:00:00Z",
    "cryptographic_hash": "sha256:a1b2c3d4...",
    "satellite_source": "Sentinel-2"
  }
}

BDCS

Agriculture — feedlot integration and cattle optimization.

Schema: partners/schemas/bdcs.json

Example payload:

{
  "partner_id": "BDCS",
  "polygon_id": "BR-MT-36400",
  "language": "pt-BR",
  "feedlot_context": {
    "cattle_head_count": 1500,
    "feed_type": "CORN_SILAGE",
    "target_slaughter_weight_kg": 550,
    "feed_optimization_index": 0.85
  }
}

EFFATHA

Agriculture — satellite frequency treatment and crop yield.

Schema: partners/schemas/effatha.json

Example payload:

{
  "partner_id": "EFFATHA",
  "polygon_id": "BR-MT-36400",
  "language": "pt-BR",
  "agrotechnical_context": {
    "delivery_mechanism": "SATELLITE_FREQUENCY",
    "treatment_protocol_id": "EFFATHA-CORN-01",
    "target_crop": "CORN_SILAGE",
    "activation_date": "2026-11-08T00:00:00Z"
  },
  "attestation": {
    "provider_timestamp": "2026-11-08T14:00:00Z",
    "cryptographic_hash": "sha256:e5f6g7h8..."
  }
}

Integration flow

Partner self-serve journey

Internal agentic architecture

Payload Generator

Fill in your values and the generator produces the exact ADV Americas JSON payload our schema expects. Copy it and POST it to the sandbox endpoint.

polygon_idsoil_profile.ph_levelsoil_profile.nitrogen_ppmsoil_profile.phosphorus_ppmsoil_profile.potassium_ppmsoil_profile.organic_matter_pctcrop_suitability.crop_typecrop_suitability.yield_potential_tons_per_haattestation.satellite_sourceattestation.provider_timestampattestation.cryptographic_hashcrop_suitability.zarc_risk_scoregeojson_polygon.coordinates[0] — one ring of [lng, lat] pairs

{
  "partner_id": "AGRO_DIGITAL",
  "polygon_id": "BR-MT-36400",
  "geojson_polygon": {
    "type": "Polygon",
    "coordinates": [
      [
        [
          -56.0728,
          -12.5453
        ],
        [
          -56.01,
          -12.5453
        ],
        [
          -56.01,
          -12.49
        ],
        [
          -56.0728,
          -12.49
        ],
        [
          -56.0728,
          -12.5453
        ]
      ]
    ]
  },
  "soil_profile": {
    "ph_level": 5.8,
    "nitrogen_ppm": 42,
    "phosphorus_ppm": 18,
    "potassium_ppm": 120,
    "organic_matter_pct": 3.4
  },
  "crop_suitability": {
    "crop_type": "soybean",
    "yield_potential_tons_per_ha": 3.6,
    "zarc_risk_score": "LOW"
  },
  "attestation": {
    "provider_timestamp": "2026-11-08T14:32:00Z",
    "cryptographic_hash": "sha256:9f2c…",
    "satellite_source": "Sentinel-2"
  }
}

GIRA Integration Assistant

Paste a payload that failed validation. GIRA applies the same deterministic checks as the API debug endpoint (POST /api/v1/agents/gira/debug): it lists every error with its field, fixes what can be fixed — numbers sent as text, a misplaced zarc_risk_score, keys the schema does not define — and returns the corrected JSON.

Interactive API Docs

The full OpenAPI specification, explorable in the browser. Use it to inspect every endpoint, field and response shape before you write code.

Open the interactive API docs

Downloads

Need an API key?

Keys are issued per partner after review. Request one from the developer team:

Request API Key dev.build@decensat.org