> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/anynet-sim/connectivity/eseye-connectivity-overview.md).

# Eseye connectivity overview

When you design and deploy your IoT devices, consider how data moves into your network. Consider your deployment options. Data movement depends on connectivity across the networks between the data source and its destination.

If you use [AnyNet](/anynet-sim/readme.md), connectivity can enable data flow across four network systems:

![Data path from an IoT device through Eseye points of presence to a customer network](https://2995386447-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzlTL8FVu6GaQkB5i1TRY%2Fuploads%2FLb1C2BcwKWwnzQ66xs6C%2FConnectivity_NetworkOverview.png?alt=media)

* **A — Device to ingress PoP:** Data travels between the device, mobile network, and [Eseye ingress Point of Presence (PoP)](/anynet-sim/connectivity/about-eseye-pops.md).
* **B — Between Eseye PoPs:** Data travels through Eseye's high-speed MPLS network.
* **C — Egress PoP to customer network:** Data travels over the internet from the Eseye egress PoP to the customer network.
* **D — Within the customer network:** Incoming data can be stored and used for business purposes.

{% hint style="info" %}
As each customer network is different, we can only describe the first three sections of the data journey.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eseye.com/anynet-sim/connectivity/eseye-connectivity-overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.