# TEMP

- [Getting Started](https://docs.iotify.io/temp/getting-started.md): Getting Started with IoTIFY is simple. Just signup with us and follow the guides below
- [Beginner](https://docs.iotify.io/temp/getting-started/beginner.md): You are learning IoT and want to get started
- [Developer](https://docs.iotify.io/temp/getting-started/developer.md): If you are already familiar with IoT development, IoTIFY is an indispensable tool to have in your IoT arsenal.
- [Tester](https://docs.iotify.io/temp/getting-started/tester.md): Using IoTIFY for your IoT performance testing is simple.
- [Walkthrough](https://docs.iotify.io/temp/walkthrough.md): A simple walkthrough of the IoTIFY platform
- [Protocol Settings](https://docs.iotify.io/temp/protocol-settings.md): IoTIFY Supports multiple protocols to connect with cloud platforms. Let's discuss each of these protocols in detail.
- [CoAP](https://docs.iotify.io/temp/protocol-settings/coap.md): Constrained Application Protocol remains one of the most efficient protocol for low power devices. Let's see how CoAP is implemented with IOTIFY
- [Raw (TCP/UDP/TLS/DTLS)](https://docs.iotify.io/temp/protocol-settings/raw-tcp-udp-tls-dtls.md): Some IoT devices could even send a raw payload to the server which is simply a binary UDP/TCP payload. IoTIFY also enables you to provide such payload with ease.
- [LWM2M](https://docs.iotify.io/temp/protocol-settings/lwm2m.md): LWM2M simulator is an enterprise only feature currently limited in preview.
- [NONE](https://docs.iotify.io/temp/protocol-settings/none.md): When you don't want a simulated device to directly connect to a server, utilise the NONE protocol.
- [Under the hood](https://docs.iotify.io/temp/under-the-hood.md): How does IoTIFY simulate your job when you submit the run? What happens behind the scene? Learn more about our orchestration strategy.
- [Google Sheets API](https://docs.iotify.io/temp/google-sheets-api.md): Feed offline sensor data from Google Sheets to your IoT platform
- [Azure IoT](https://docs.iotify.io/temp/azure-iot-connector.md)
- [Losant IoT](https://docs.iotify.io/temp/losant.md)
- [Losant Connector](https://docs.iotify.io/temp/losant/losant-connector.md)
- [Parking Space Management](https://docs.iotify.io/temp/losant/untitled-7.md)
- [Waste Management](https://docs.iotify.io/temp/losant/untitled-6.md)
- [Connected Truck](https://docs.iotify.io/temp/losant/untitled-1.md)
- [Delivery Van](https://docs.iotify.io/temp/losant/delivery-van.md)
- [Google Cloud IoT Core](https://docs.iotify.io/temp/untitled-2.md)
- [IBM Cloud](https://docs.iotify.io/temp/untitled-3.md): Learn how to configure IoTIFY's network simulator to connect virtual devices to IBM Cloud via IBM's MQTT broker.
- [Simple Messaging](https://docs.iotify.io/temp/untitled-3/simple-messaging.md)
- [IBM Bluemix: Monitoring Energy Consumption](https://docs.iotify.io/temp/untitled-3/untitled-5.md)
- [Dweet.io](https://docs.iotify.io/temp/untitled-4.md)
- [JMeter and why it fails at IoT](https://docs.iotify.io/temp/jmeter-and-why-it-fails-at-iot.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.iotify.io/temp.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.