AISHub API

Name: AISHub API API
Brand: AISHub API
Availability: InStock

★ Only Publicly Available SpecData EnrichmentData TransformationapiKey2 EndpointsREST

For Agents

Look up live AIS vessel positions and the network of receiving stations contributing data, with results filtered by MMSI, IMO, area, or station id.

Quickstart

Get started with AISHub API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"look up vessel position by MMSI"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with AISHub API API.

Retrieve live AIS vessel positions filtered by MMSI, IMO, MMSI list, or geographic bounding box

List the global network of AIS receiving stations and their last-seen status

Choose between JSON, XML, and CSV response formats per request

Resolve a vessel's most recent position fix and reported speed and course

GET STARTED

Start building with AISHub API API

Explore with Jentic

View OpenAPI Spec

Use for: Look up the latest position of vessel with MMSI 366000000, List all AIS receiving stations contributing to AISHub, Retrieve vessel positions inside a bounding box, Check whether an AIS station is currently online

Not supported: Does not provide weather, port operations, voyage history, or commercial maritime tracking — use for AIS position and station lookups only.

Jentic publishes the only available OpenAPI specification for AISHub API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for AISHub API, keeping it validated and agent-ready. AISHub provides global AIS (Automatic Identification System) data sourced from a community of receiving stations, exposing vessel position retrieval and station metadata. The API is rate-limited to one request per minute and uses an API username passed as a query parameter, so it suits low-frequency monitoring rather than streaming use cases.

Use Cases

Patterns agents use AISHub API API for, with concrete tasks.

★ Vessel tracking dashboard

Power a low-cost vessel tracking display by polling AISHub once per minute for vessels of interest. The API returns position, speed, course, and timestamp. Best used for occasional refresh — for high-frequency tracking, a paid commercial AIS feed is required.

Call GET /ws.php with username, format=json, and mmsi=366000000 and parse the latest LAT/LON from the response

Station network monitoring

Audit which AISHub receiving stations are online and which have stopped reporting. The /stations.php endpoint lists each station with metadata including its last data timestamp, useful for community-run station operators.

Call GET /stations.php with username and format=json, then surface stations whose last-seen timestamp is older than 24 hours

AI agent integration via Jentic

Let an agent answer maritime questions like 'where is vessel X right now' by calling AISHub through Jentic. The agent searches Jentic for vessel-position retrieval, loads the AISHub schema, and Jentic injects the username credential at execution.

Search Jentic for 'look up the position of a ship by MMSI', load the AISHub /ws.php operation, and return the latest LAT/LON for the requested MMSI

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for aishub api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/ws.php

Retrieve AIS vessel data

GET

/stations.php

Retrieve AIS station information

GET

/ws.php

Retrieve AIS vessel data

GET

/stations.php

Retrieve AIS station information

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The AISHub username (passed as a query parameter) is stored encrypted in the Jentic vault and never exposed to the agent prompt. Jentic appends it at execution time.

Intent-based discovery

Agents search by intent (e.g., 'find a ship by MMSI') and Jentic returns the AISHub /ws.php operation with the parameter schema so the agent calls it without reading docs.

Time to first call

Direct AISHub integration: a few hours to wire the username, format, and parsing. Through Jentic: under 15 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

AISHub API (aishub_api)

Same AISHub service published under the aishub_api vendor entry.

Both entries expose identical endpoints; pick whichever matches your existing index.

Complementary

OpenAI API

Use OpenAI to summarise vessel movement narratives from raw AIS data.

Pair OpenAI with AISHub when an agent needs to convert position fixes into natural-language reports.

Complementary

Anthropic Messages API

Generate agent responses that explain AISHub query results.

Use Claude to interpret AIS data fields like NAVSTAT codes and turn them into plain-language status updates.

FAQs

Specific to using AISHub API API through Jentic.

Why is there no official OpenAPI spec for AISHub API?

AISHub does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AISHub API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the AISHub API use?

AISHub uses an API username passed as the 'username' query parameter on each request. Jentic stores the username in its encrypted vault and appends it at execution time, so the agent never embeds it in code.

What are the rate limits for the AISHub API?

AISHub limits free accounts to one request per minute. Treat the API as a polling source for occasional updates, not a real-time stream. If you need higher frequency you'll need a commercial AIS provider.

Can I look up a vessel by MMSI through Jentic?

Yes. Use the Jentic search query 'look up vessel position by MMSI'. Jentic returns the GET /ws.php operation; supply the mmsi and format parameters and Jentic injects your AISHub username automatically.

What response formats does AISHub support?

Both endpoints accept a 'format' query parameter and can return JSON, XML, or CSV. Most agent flows pick JSON for parsing, but CSV is useful for bulk position dumps into a spreadsheet.