# MOBS

> METAR and SPECI for 27 stations, pushed over WebSocket or read over HTTP.

> ## Agent Instructions
> The WebSocket at wss://mobs.ws/v1/ws/metar is the product. The HTTP API is a fallback for backfill only.
> Follow /agents.md for connect, auth, fields, heartbeat, reconnect, and dedupe. Never log MOBS_TOKEN or a URL that includes ?token=.

- [METAR API](https://docs.mobs.ws/index.md): WebSocket push and HTTP for METAR and SPECI on 27 stations.
- [Quickstart](https://docs.mobs.ws/quickstart.md): Three steps to a report: get an API key, connect, read a record.
- [Authentication](https://docs.mobs.ws/authentication.md): API access uses an API key, issued on request. There are no accounts, plans or sign-up.
- [Use MOBS from an AI agent](https://docs.mobs.ws/agents.md): Connect to the WebSocket first. Use HTTP only to backfill the latest report per airport.
- [WebSocket API](https://docs.mobs.ws/websocket.md): Push of new METAR and SPECI reports on /v1/ws/metar.
- [HTTP API](https://docs.mobs.ws/rest.md): The /v1/metar endpoints: latest report per airport, resync after a reconnect, and latency.
- [Errors](https://docs.mobs.ws/errors.md): Socket close codes and HTTP status codes.
- [Rate limits](https://docs.mobs.ws/rate-limits.md): Limits per API key and server-wide.
- [Stations](https://docs.mobs.ws/stations.md): METAR and SPECI for 27 stations.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.