Open a route to your own system

Your data.
Your platform.
Your intelligence.

Choose where observations go and how they are used. Connect selected equipment to your own receiving system through an agreed and tested integration.

FIELD INTELLIGENCE / CONCEPT VIEW
Selected field equipment
Your receiving server
Your platform & AI
ZHICLOUD AGENT

A better question

What changed in the field,
and what should we review?

Observations → Evidence → Operator review

ENVIRONMENTAL MONITORING × APPLIED AI

A route designed around you

Two paths.
You choose the destination.

Explore direct-to-customer integration or optional ZhiCloud analysis. Hardware, firmware and receiving-system requirements define the delivered route.

INTEGRATION ARCHITECTURECONCEPT VIEW
01 / SENSEField equipmentMeasurements & agreed images
02 / DELIVERYour receiving serverProject-specific interface
03 / ANALYSEYour platform & AIYour storage and analysis

Agree image or telemetry delivery, authentication, retry behaviour and acceptance tests. Direct delivery for the current pest gateway requires project development.

AGREED FIELDS / VERSIONED INTERFACE / PILOT ACCEPTANCE
INTEGRATION ARCHITECTURECONCEPT VIEW
01 / CONNECTSelected devicesAgreed data connection
02 / INTERPRETZhiCloud AgentNumerical analysis & reports
03 / REVIEWYour operationsReviewed results & agreed delivery

Select an appropriate cloud, desktop or local workspace. Report exports or a custom result-delivery interface are scoped separately.

AGREED FIELDS / VERSIONED INTERFACE / PILOT ACCEPTANCE

Current pest-gateway baseline: HTTP upload to the manufacturer server. Direct customer delivery requires adaptation and testing; a standard public pull API is not currently available for this gateway service.

Match the protocol to the equipment

An interface is a configuration decision.

Integration routes and what needs confirmation
RouteUseStatus & checks
HTTP / HTTPS POSTAgreed image or telemetry deliveryDirect customer delivery is project development. Confirm endpoint, payload, TLS, authentication, retry and offline storage.
MQTTTelemetry or an agreed result messageVerify device/gateway implementation, broker, topics, TLS and credentials. Image transfer requires a separate design.
RS485 / ModbusLocal sensor or logger integrationUse the selected instrument's register map and serial settings. RS485 alone does not establish Modbus support.
LoRaWANSmall telemetry payloadsConfirm radio hardware, regional plan, network server and decoder. This is not the proposed transport for routine JPEG images.
ONVIF / RTSPCompatible camera stream integrationCamera-specific verification required. A documented camera must support the requested interface; not every imaging device does.
Pull API / result exportServer-to-server access or analysis deliveryAvailability depends on the selected service. The current pest gateway has no standard public pull API; agree a separate interface scope.

A listed route describes an integration option, not universal support across the catalogue. Approved firmware, field mappings and acceptance results define the delivered configuration.

A reusable integration starts with a clear contract

Define once. Verify each device.

Data & security agreement

Agree device ID, timestamp and timezone, units, image location or upload body, battery and signal fields where available. Define authentication or request signing, retention, retries, duplicate handling and recovery.

Compatibility & commercial scope

An agreed one-time integration fee covers the specified development scope. Compatible devices can reuse a protocol and firmware contract after field mapping checks. New schemas, hardware or functions may require additional work.

From requirement to an accepted pilot

Test the full route before a rollout.

  1. 01

    Requirements

    Country, devices, power, carrier, destination system and data requirements.

  2. 02

    Sample exchange

    Agree example files, field schema and security settings through a private project channel.

  3. 03

    Pilot acceptance

    Test delivery, images, timestamps, gaps, retries, reconnection and customer processing.

  4. 04

    Scale review

    Confirm firmware versions, new device fields, cost and deployment lead time.

Can I buy hardware without using your cloud?

Discuss a direct-to-customer configuration for the selected equipment. For the current pest gateway this is a custom integration, not its default firmware behaviour. We confirm the complete route before quotation.

Can my own AI use the original images?

Yes, the project can be scoped to deliver original agreed images to your receiving system. Image format, capture quality, schedule and delivery are acceptance items. Manufacturer recognition services can be scoped separately.

Does a sample payload mean an API is already available?

No. A proposed schema is a design document. Production availability is confirmed by the agreed interface implementation and a successful pilot.

From possibility to a pilot

Make the connection.
Start with a pilot.

Start with your site, your equipment and the question you need to answer. Define a practical first use together.

Discuss a pilot project