Skip to main content
Give this page to the team that runs your firewall, proxy or TLS inspection before the first machine is enrolled. Quint’s cloud never opens a connection to an enrolled machine: the endpoint makes every connection itself, outbound. The hosts the endpoint connects to are the same on every operating system. The sections on proxies and local ports describe a Mac. For the same detail on Windows and Linux, ask your Quint contact.

What the endpoint connects to

Every connection in this list is TCP 443.
  • api.quintai.dev: the endpoint registers, checks in about once a minute, and fetches its policy.
  • ingest.quintai.dev: the endpoint uploads what it records.
  • quint-prod-payloads.s3.us-east-1.amazonaws.com: object storage on Amazon S3. The endpoint uploads the body of an event over 200 KiB straight to it. Where it cannot, only the first 4 KiB of the body is uploaded.
  • api.anthropic.com: about once a minute the endpoint opens a connection here to check that its local proxy is in the path. It sends no credentials and no data from the machine. Where this host is blocked, that check fails.
Allow these by host name. The addresses behind them change, so a rule written for IP addresses stops matching. DNS. The endpoint uses the machine’s own resolver. If that resolver returns an error or takes more than three seconds, the endpoint asks public resolvers for Quint’s hosts and the Amazon S3 host instead: 1.1.1.1, 8.8.8.8, 9.9.9.9 and 208.67.222.222, on UDP 53. Where outside DNS is blocked, the endpoint depends on the machine’s resolver, and on addresses it resolved in the last 30 days.

To install

Both are TCP 443.
  • quint-releases-public.s3.amazonaws.com: Quint’s public download site, where the installers are. Your MDM or configuration tool can carry the installer instead, and then the machine needs no access to this host to install. Keep it reachable if you use Agent rollout, which downloads new versions from it.
  • get.quintai.dev: the install script for Linux.

Proxies and TLS inspection

  • Explicit proxies. Quint works on a network whose only way out is an explicit proxy. The proxy’s address is a Quint setting that your MDM delivers alongside the Quint profiles; ask your Quint contact for it before you roll out. Without that setting the background service connects to Quint directly: for its own traffic to Quint, it does not pick up a system proxy, a PAC file or proxy environment variables. Where it cannot connect directly, the machine does not report, and agents’ requests to their model provider can fail too, because the background service makes those connections.
  • TLS inspection. Either exempt api.quintai.dev, ingest.quintai.dev and the Amazon S3 host from inspection, or, before you inspect them, ask your Quint contact for the Quint setting that carries your inspection certificate authority, and deliver it with your MDM. Installing the authority in the Mac’s trust store is not enough: the endpoint does not use that store for its own connections. Without one of the two, the endpoint refuses a re-signed certificate, because it accepts only the certificate authorities built into it. For api.quintai.dev or ingest.quintai.dev that stops the endpoint from reporting. For the Amazon S3 upload it cuts those bodies to their first 4 KiB.
  • Rules that match on the calling program see Quint. A request from an agent to its model provider passes through Quint’s local proxy, and Quint’s background service makes the outbound connection. A firewall rule or per-app allowlist written for the agent’s own program does not match that connection. On a Mac the program to allow is /usr/local/bin/quint.

Local ports

The endpoint listens on these ports, on the loopback address 127.0.0.1 only. Nothing on your network can reach them. If another service already uses port 9090, see Platform support before you install.

When the endpoint cannot reach Quint

  • The agent keeps working. The agent’s own traffic does not depend on Quint’s cloud.
  • Events wait on the machine. The endpoint keeps unsent events on disk, up to 2 GiB in each of two queues, and sends them when the connection returns. When a queue is full, its oldest events go first. An event more than seven days old is dropped, not sent.
  • Large bodies do not wait in full. While Quint cannot be reached, an event whose body is over 200 KiB keeps only the first 4 KiB of it.
  • The dashboard shows the gap. A machine that has stopped reporting moves under Silent in Data Sources. See Verify a machine.

Containers and Kubernetes

A Quint sidecar needs the Quint API and Quint’s ingest address, the cluster DNS service and, with record delivery, the admission webhook’s Service address. See Network policies.

The dashboard

People use the dashboard in a browser at https://cloud.quintai.dev, and partners at https://admin.quintai.dev. Sign-in can send a 6-digit code by email; see Sign in.

If this fails

Next

Last modified on November 13, 2026