Agent-ready OpenAPI document · curated by JenticData EnrichmentData TransformationapiKey2 EndpointsREST
Know of an official OpenAPI document? Contribute it →
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.
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. 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.
Install Jentic One Beta
Connect the AISHub API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AISHub API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Faishub.net%2Faishub" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Faishub.net%2Faishub" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with AISHub 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
Identify the contributing station for a given AIS message
Use Cases
Patterns agents use AISHub 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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
AISHub API
- Foundational (C-)50/100
100
Foundational Compliance63
Developer Experience & Jentic Compatibility55
AI-Readiness & Agent Experience94
Agent Usability15
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
55
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
69%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
15
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
15%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring AISHub by hand means appending its username as a query parameter, parsing the ws.php and stations.php responses, and writing your own retry logic. Through Jentic you install once, import AISHub from the API Directory, store the username once, and your agent calls it.
Permission scoping
AISHub takes its filters as query parameters and only reads AIS position and station data, so scope your agent by operation: limit it to the operations it needs, such as /ws.php for ship positions or /stations.php for station lookups.
Credential isolation
Your AISHub username is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'find a ship by MMSI', and Jentic returns the AISHub /ws.php operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AISHub 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 with Jentic One, the self-hosted execution layer.
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.
Can I limit what my agent is allowed to do with the AISHub API?
Yes. Because you run Jentic One yourself, your own rules decide which AISHub operations and credentials the agent may use. AISHub only reads AIS data through query parameters, so you can scope the agent by operation, granting it just /ws.php for vessel positions, just /stations.php for station lookups, or both. Your stored AISHub username is injected at execution only for the operations you allow.
GET STARTED