# AMETEK

> AMETEK, Inc. is a global manufacturer of electronic instruments and electromechanical devices
> with annual sales over $6 billion, operating through two segments — the Electronic Instruments
> Group (EIG) and the Electromechanical Group (EMG). It is a portfolio of roughly 40 operating
> brands, and its developer surface lives inside those brands, not on the corporate site.

Generated by API Evangelist from this repository's artifacts on 2026-09-02.
AMETEK does not publish an llms.txt of its own; /llms.txt returns 404 on docs.cranksoftware.com
and a soft-404 on www.ametek.com.

## What AMETEK actually publishes for developers

There is no AMETEK-wide developer portal, no api.ametek.com, no OpenAPI, no MCP server and no
agent card. What exists is two real, public, brand-level surfaces:

1. **AMETEK Powervar iSite PRO REST API** — a documented HTTP API embedded in the iSite PRO
   network management card fitted to Powervar UPS systems. Three read-only operations, JSON,
   Basic auth or an `x-auth-token` session token, URI-path versioning at `v1`. The host is the
   customer's own adapter on their own LAN, discovered by mDNS — there is no cloud endpoint.
   AMETEK Powervar publishes it as a PDF definition (A55-00202 REV B, 2023-03-10), not as a spec.
2. **Crank Storyboard APIs** — Crank Software (AMETEK-owned) publishes 313 versioned API
   reference pages at docs.cranksoftware.com covering nine families: Lua API, Lua DOM module, Lua
   types, Lua canvas, JavaScript API, JavaScript canvas, the Engine public C API, Storyboard IO
   and the Storyboard IO wrapper. These are in-process embedded-GUI bindings compiled into an
   application — a real API reference, but not callable over a network.

## AMETEK Powervar iSite PRO REST API

- Spec (transcribed by API Evangelist from the published PDF): openapi/ametek-powervar-isite-pro-openapi.yml
- Source definition: https://www.powervar.com/-/media/ametekpowervar/pdf/products/connectivity-solutions/isite-pro/user-manuals/a55-00202-rev-b-isite-pro-rest-api-definition.pdf
- Product page: https://www.powervar.com/products/connectivity-solutions/isite-pro-net-adapter
- Base URL: `http://{device_host}:{port}/api/v1` (templated — the device is the host)

Operations:

- `GET /UpsStatus` (getUpsStatus) — live electrical and battery state of the attached UPS:
  battery status, charge and minutes remaining, input/output voltage and frequency, load percent,
  battery temperature and replacement date, cumulative time-on-battery counters.
- `GET /UpsAlarms` (getUpsAlarms) — array of currently active alarms, each with an RFC 3339
  timestamp, a name drawn from a fixed 38-value catalogue, a severity (3 fault, 2 warning,
  1 informational) and a description. An empty array means healthy.
- `GET /whoAreYou` (getWhoAreYou) — adapter identity: model, serial, manufacturer, firmware,
  hostname, every Ethernet interface with its addressing, and the embedded HTTP server's state.

There is no write surface. Nothing in this API changes device state.

## Crank Storyboard

- Documentation: https://docs.cranksoftware.com/
- API reference index: https://docs.cranksoftware.com/docs/9.0/category/storyboard-apis
- Storyboard IO: https://docs.cranksoftware.com/docs/9.0/storyboard/api/storyboard-io-api/
- Engine public API: https://docs.cranksoftware.com/docs/9.0/storyboard/api/storyboard-engine-public-api/
- Lua API: https://docs.cranksoftware.com/docs/9.0/storyboard/api/storyboard-lua-api/
- JavaScript API: https://docs.cranksoftware.com/docs/9.0/storyboard/api/storyboard-javascript-api/
- Current documented version: 9.0.2

## Repository artifacts

- Authentication profile: authentication/ametek-authentication.yml
- Conventions, versioning, reversibility: conventions/ametek-conventions.yml
- Lifecycle and deprecation policy: lifecycle/ametek-lifecycle.yml
- Standards conformance: conformance/ametek-conformance.yml
- Data model: data-model/ametek-data-model.yml
- Error catalogue (recorded absence): errors/ametek-problem-types.yml
- Candidate MCP tools (derived; AMETEK ships no server): mcp/ametek-mcp.yml
- Tool crosswalk: mcp/ametek-tool-crosswalk.yml
- Agent skill: skills/ametek-monitor-ups-health.md
- Packages (recorded absence): packages/ametek-packages.yml
- Plans (no developer plans published): plans/ametek-plans-pricing.yml
- Rate limits (none published): rate-limits/ametek-rate-limits.yml
- Domain security probe: security/ametek-domain-security.yml
- /.well-known probe (all miss): well-known/ametek-well-known.yml

## What does not exist

- No OpenAPI, AsyncAPI, GraphQL SDL or .proto published by AMETEK.
- No published SOAP contract. www.ametek.com does run two classic ASP.NET SOAP services —
  /GlobalSearch.asmx and /AmetekServices.asmx, both named in https://www.ametek.com/robots.txt —
  but robots.txt disallows them, so this pipeline did not fetch their ?wsdl. They are internal
  site services (site search), not a documented developer surface, and no WSDL is saved.
- No MCP server, hosted or stdio, for any AMETEK brand.
- No A2A agent card on any AMETEK host.
- No /.well-known/ document on www.ametek.com, www.powervar.com or docs.cranksoftware.com.
- No first-party SDK in npm, PyPI or any other public registry.
- No API pricing, plans, rate limits, error catalogue, status page or SLA.
- No dated changelog for either API surface.

## Corporate

- Website: https://www.ametek.com
- Privacy: https://www.ametek.com/privacy
- Terms of use: https://www.ametek.com/terms-of-use
- Contact: https://www.ametek.com/contact-us
- Newsroom: https://www.ametek.com/newsroom