# Telemetry Station

> Managed Iridium satellite data service. Activate Iridium SBD (9602/9603) and Certus (9704) devices, receive and store their messages, and retrieve them through an API. Pricing is prepaid credits: 1 USD = 1 credit. All dates are UTC.

## Start here
- [Pricing](https://telemetrystation.com/pricing): plans, activation fee, per-message and destination fees.
- [SBD calculator](https://telemetrystation.com/calculators/sbd): estimate an Iridium SBD deployment.
- [Certus calculator](https://telemetrystation.com/calculators/certus): estimate an Iridium Certus deployment.
- [Device activation](https://telemetrystation.com/iridium-device-activation): what activation involves.
- [Data API documentation](https://telemetrystation.com/documentation): download and retrieve telemetry.
- [BEAR Module 9704](https://telemetrystation.com/products/bear-module/9704): in development; development status, preliminary datasheet, and pre-order inquiry.
- [Contact](https://telemetrystation.com/contact): custom engineering, BEAR Module, partnerships, support.
- [Terms](https://telemetrystation.com/terms) and [Privacy](https://telemetrystation.com/privacy).

## Supported devices and service limitations
- Standard self-service support is for eligible Iridium SBD 9602/9603 and Certus 9704 modems, not every Iridium device. Eligibility is confirmed during activation.
- Activation timing, connectivity, latency, and message delivery are not guaranteed. Up to five years of message retention requires an active account in good standing and is subject to the Terms.

## Guides and comparisons
- [SBD vs Certus 9704](https://telemetrystation.com/articles/iridium-sbd-vs-certus-9704): message sizes and choosing a network.
- [Ground Control comparison](https://telemetrystation.com/articles/ground-control-comparison): product scope, compatibility, and limitations.
- [MetOcean comparison](https://telemetrystation.com/articles/metocean-telematics-comparison): product scope, compatibility, and limitations.
- [Telemetry Station SDK](https://github.com/Telemetry-Station/sdk): alpha C99 host library, F169 bench checkout, generated payload codec and optional GNSS API. Software tests are separate from pending hardware qualification.

## For AI Agents
- [Agent integration guide](https://telemetrystation.com/documentation/agents): quick start, authentication, code examples, limits.
- [OpenAPI 3.1 specification](https://telemetrystation.com/openapi.json): REST API at https://telemetrystation.com/api/agent/v1.
- MCP server (Streamable HTTP): https://telemetrystation.com/mcp. Public tools need no authentication; telemetry tools need the customer's data API key as an Authorization: Bearer header supplied by your MCP client configuration.

## What an agent can and cannot do
- Can: read capabilities, estimate costs with the real pricing engine, validate inputs, prepare a pre-filled activation link, retrieve telemetry with the customer's API key, and send an inquiry the customer approved.
- Cannot: pay, enter email one-time codes, create passwords, or activate devices. Those steps are completed by the customer:
  - customer_details_and_email_otp: The customer enters their details on the Telemetry Station website and types the one-time code emailed to them. Agents never see or relay the code.
  - imei_registration: IMEIs are verified by Telemetry Station against the Iridium network during activation. Local format checks from this API are not authoritative.
  - destinations: Optional email, DirectIP, or HTTPS destinations are configured in the activation flow.
  - payment_approval: The customer reviews the final amount and pays through Stripe Checkout. Agents cannot pay or approve payment.
  - account_password: The customer creates their own account password. Agents never set or receive passwords.

## Telemetry retrieval
- GET https://telemetrystation.com/api/agent/v1/telemetry/messages?imeis=<comma-separated>&start=YYYY-MM-DD&end=YYYY-MM-DD with Authorization: Bearer <customer data API key>.
- Window is half-open [start, end) in UTC, at most 31 days. For hourly jobs, repeat the request with start = the last processed UTC day and de-duplicate by IMEI and message time.
- Never put the API key in a URL.