# Uptake

> Uptake Technologies is a Chicago-based industrial AI and predictive-maintenance software
> company founded in 2014. Its SaaS platform ingests telematics, sensor, fluid-analysis and
> work-order data from heavy commercial fleets and industrial assets and applies machine-learning
> failure models to predict component failure before it happens. Bosch announced its acquisition
> of Uptake in March 2026.

This file was generated by API Evangelist from publicly probed surfaces. Uptake does not publish
an llms.txt of its own (https://uptake.com/llms.txt returns a bot challenge; every other reachable
host returns 404).

## Status of the machine-readable surface

- **No public OpenAPI, Swagger, GraphQL SDL, AsyncAPI, Protobuf or Postman collection.** Probed
  `/openapi.json`, `/openapi.yaml`, `/swagger.json`, `/v1/openapi.json`, `/api-docs`, `/docs`,
  `/redoc` on `api.uptake.com`, `api.common.uptake.com`, `developer.uptake.com`,
  `developers.uptake.com`, `fleet.uptake.com`, `login.uptake.com` and `start.uptake.com`.
- **No MCP server and no A2A agent card.** `/.well-known/agent-card.json` and
  `/.well-known/agent.json` miss on every host.
- **A live but closed API gateway.** `https://api.uptake.com/` and `https://api.common.uptake.com/`
  are AWS API Gateway endpoints behind Cloudflare that return HTTP 403 `ForbiddenException` to
  every anonymous request, with no `WWW-Authenticate` challenge.
- **The developer portal is gone.** `https://developer.uptake.com/` returns nginx 404. Wayback
  shows a login-gated SPA there through 2021.
- **Product documentation is customer-only.** The Uptake user guide and release notes are Google
  Sites (`sites.google.com/uptake.com/uptake-user-guide/home` and `.../uptake-release-notes/home`,
  both referenced from Uptake's own application bundle) and redirect to a Google account sign-in.

## Products

- **Uptake Fleet / Radar** — predictive maintenance alerts from existing telematics, fluids and
  historical work-order data.
- **Uptake Compass** — normalizes messy work-order data into a single source of truth.
- **Uptake Fusion** — moves operational-technology (OT) data to the cloud and contextualizes it
  against enterprise systems (SAP, IBM, Oracle).
- **Uptake Scout** — custom rules-based alerting over operator and maintenance knowledge.
- **Asset Strategy Library (ASL)** — ~800 equipment types, 58,000+ failure modes, 180,000+
  reportable conditions, acquired with Asset Performance Technologies in 2018.

## Authentication

- OpenID Connect via Uptake's Okta tenant on its own domain:
  https://start.uptake.com/.well-known/openid-configuration (HTTP 200)
- RFC 8414 authorization-server metadata:
  https://start.uptake.com/.well-known/oauth-authorization-server (HTTP 200)
- Platform API keys are not self-service. Integration partners are instructed to send their token
  to an Uptake account representative, who completes the connection.

## Live hosts

- https://uptake.com/ — marketing site (SiteGround bot challenge; 202 on every path)
- https://fleet.uptake.com/ — customer application (Vue SPA)
- https://start.uptake.com/ — Okta identity tenant
- https://login.uptake.com/ — sign-in shell
- https://api.uptake.com/ — API gateway (403 anonymous)
- https://api.common.uptake.com/ — API gateway (403 anonymous)
- https://geotab.uptake.com/ — MyGeotab Add-In for the Uptake Essentials marketplace solution
- https://github.com/uptake — 16 public open-source repositories

## Repository artifacts

- apis.yml — the API Evangelist profile
- well-known/uptake-well-known.yml — every `/.well-known/` probe with its status
- well-known/uptake-openid-configuration.json — verbatim OIDC discovery document
- well-known/uptake-oauth-authorization-server.json — verbatim RFC 8414 metadata
- authentication/uptake-authentication.yml — auth profile
- scopes/uptake-scopes.yml — identity scopes (no product-API scope vocabulary is published)
- conformance/uptake-conformance.yml — standards conformance, evidenced
- packages/uptake-packages.yml — first-party open-source packages (none is an API client)
- security/uptake-domain-security.yml — TLS/HSTS/DNSSEC/CAA/SPF/DMARC probe

## What Uptake could publish to become machine-readable

- An OpenAPI for the platform API at a stable public URL, linked from a live developer page.
- A `WWW-Authenticate` challenge on the gateway so the auth model is discoverable without a ticket.
- A public scope/permission reference.
- A public changelog (the release notes exist, but behind a Google sign-in).
- `/.well-known/security.txt` and a public vulnerability-disclosure policy.