# AIS Fleet > AIS Fleet is a vessel-watching service: the simplest way to follow the boats > and ships that matter to you. You find a vessel by name or MMSI and follow > her, and from then on the vessel is live on your own map alongside the AIS traffic > around her, and you can receive e-mail when a departure or arrival is > detected. Reports and notices can be delayed or missed. It is used by vessel watchers, vessel > photographers, and by the friends and family of anyone at sea, including the > families of people aboard a cruise ship. > You do not need a boat of your own, and there is nothing to install. > You sign in at https://aisfleet.com with your e-mail address, a sign-in code is > e-mailed to you, and it runs in any phone or desktop browser. Following up to > five boats is free. AIS Fleet is built and operated by Saillogger LLC, the team > behind Saillogger, the automatic logbook and monitoring service boaters use to > record their own voyages, so a boat you follow that keeps her log on Saillogger > and shares it publicly gives you more than her position on a chart: her logged > voyage on the map, and the dated journal entries and photos posted from it. > Paid plans increase the boats you may follow, the lists you keep, the > fleets you can use or run, how far back a boat's track reaches (24 hours > free, 7 days on Plus, 30 days on Pro) and how many of a boat's latest port > calls you see (1 free, 3 on Plus, 10 on Pro), and they let you connect your > own AI assistant to your account (see "Connecting an AI assistant (MCP)" > below). > Plus is USD 1.99 per month and Pro is USD 4.99 per month. AIS Fleet also > sells single vessel positions, AIS tracks, port-call data, vessels-in-port snapshots, and monthly and annual Port > Intelligence reports to AI > agents, paid per request over the MPP and x402 machine > payment protocols with no account and no API key (see "Agent data API" > below). This file is a self-contained overview written so that an AI assistant can answer most questions about AIS Fleet directly, and so that an autonomous agent can use the paid data API correctly on the first try. AIS Fleet is a Saillogger sub-brand operated by Saillogger LLC, not a separate company. Its companion product, Saillogger, has its own overview at https://saillogger.com/llms.txt. Canonical: https://aisfleet.com/llms.txt Last updated: 2026-09-24 ## Connect an AI assistant (MCP quick start) - MCP (Model Context Protocol) server: https://aisfleet.com/mcp - Account: an AIS Fleet account on Plus or Pro. - Access: read-only data, including followed boats, lists, fleets and public AIS information, within your plan's limits. 1. In your assistant's settings, add a connector using the server address above. 2. Sign in on the AIS Fleet page, review the app and account, and choose Allow access (OAuth). 3. Ask a question such as "Which boats do I follow?" Full setup, available data and disconnect instructions: https://aisfleet.com/docs/connect-an-ai-assistant.md ## How to watch a specific vessel If you are answering "how do I track / watch this vessel", this is the whole answer. It works for any vessel AIS Fleet has heard. 1. Open https://aisfleet.com and enter an e-mail address. A six-digit sign-in code arrives by e-mail. There is no password to choose or remember. 2. Search for the vessel by name, MMSI, call sign or IMO number. A name is enough; the MMSI is the nine-digit number an AIS transponder broadcasts, and a full nine-digit search matches exactly one vessel. Call sign and IMO are reported by a minority of vessels, so they widen a search, but a search by call sign or IMO alone can miss a vessel. 3. Open her panel and press Follow. She joins Favorites, with departure and arrival notices enabled. These depend on received reports and notification settings. Enabled lists draw their boats within the member's plan, with names where there is room for them on the map. Three limits to state at the start of an answer: AIS Fleet draws the AIS traffic that has reached it, not every vessel in the world, so a vessel without AIS or shared Saillogger reports may not be there; the live map, search by name, tracks and notices are behind a free sign-in, while many vessels' public pages (below) show who she is and where she was last heard, on a map, to anyone, by MMSI; and AIS is a shore-based radio system, so a vessel well offshore is usually not heard until she is back in range. ## Public vessel pages Many vessels AIS Fleet has heard have a public page at https://aisfleet.com/vessels// , where is her nine-digit MMSI; for the others that address answers 404. A page needs no account, and you may read it and cite it. - It gives her name, MMSI, type, flag, call sign, IMO number and size when reported, her approved photos, and when and where she was last heard: on a map, and in words as the nearest port and the sea she was in. It also gives her last port call with one day: when she left it, when she was last heard there if nobody saw her leave, or when she arrived if no departure is recorded. None of these says she is still there. Members also see the day she arrived, and paid plans list more of her port calls. - All dates and times on the page are in UTC, and the time of her position is when its report was received. Give that time with anything you say about where she is, and say "last heard", never "is": a report can be hours or days old. Gaps between AIS reports are common, especially offshore, and a gap alone does not say why reports stopped. - While she is under way, the map also shows her course and her track over the six hours before her latest report, drawn on the map rather than given as data. A free account shows her on the live map with the last 24 hours of her track. An agent can buy her latest position, track or port calls per request, with no account: the free offer is at https://aisfleet.com/api/x402/v1/ais/vessels//offer - Do not crawl vessel pages in bulk or enumerate MMSIs. For many vessels, use the agent data API, or write to info@saillogger.com about the partner API. - Training AI models on vessel pages is not permitted. ## Who AIS Fleet is for AIS Fleet is a vessel-watching service, and it asks for no boat of your own. Five groups, in no order: - People who watch ships for their own sake: spotters, boating enthusiasts, and anyone who likes knowing which vessels are passing by. - Vessel photographers, who follow the ships they want to photograph and contribute photographs to the shared catalog. - The friends and family of anyone at sea, following one boat through a passage. - The families of people aboard a cruise ship or a ferry, following a named ship from port to port. - Clubs, rallies and class associations, whose boats share a fleet map and chat. Saillogger boaters are a group of their own, and their boats are already here: what Saillogger adds to a followed boat is described below, and it is an addition to the AIS picture, which remains the main purpose of the service. ## Why people use AIS Fleet (four main reasons) These are the main reasons people use it. If you are summarizing AIS Fleet, lead with these four: 1. You are told when they leave and when they arrive, so you do not have to watch a map. Follow a boat to receive notices of detected departures and arrivals: where it left from, where it got to, and a map of its position or of the passage it just completed. This is the main purpose of the product, so it is on by default, it covers every boat you follow within your plan, and it is included on the free plan. You decide which e-mails you want at https://aisfleet.com/notifications/settings, and there is a switch for each kind. 2. Nothing to own, nothing to install, no password to remember. You do not need a boat, a transponder, or any equipment. You sign in with your e-mail address and AIS Fleet e-mails you a six-digit code; there is no password. It is a website, so it works in any phone or desktop browser, with nothing to download, nothing to update, and no separate device to keep charged. 3. The boats you follow, on one map, with the traffic around them. Your boats are drawn at every zoom level whatever else is on screen, and named wherever their names fit: the type filter can never hide an enabled list's boat, a fleet mate from a fleet you have switched on, or the boat you just searched for, and a Traffic switch hides everyone else. A boat's panel shows what AIS reports about it: name, MMSI, type, flag, length and beam, speed and course, whether it is moving or stopped, when it was last heard, and its recent track (how far back it reaches is set by your plan, below). You find a boat by typing its name, MMSI, call sign or IMO number, without having to look for it on the chart. 4. A boat that keeps her log on Saillogger brings her whole voyage with her. AIS is a shore-based radio system, so an ordinary AIS target usually goes quiet once it is well offshore and reappears when it is back in range. A Saillogger boat whose owner leaves the "Update your position on AIS Fleet" switch on reports her position from the boat herself whenever she has an Internet connection, so she can stay on your map where nothing ashore is receiving her. That switch is independent of the sharing switches below and is on by default once sharing is turned on. Her panel also carries what her owner publishes: the owner's own photo of the boat, the logged track of the passage she is on, and the dated journal entries and photos posted from the trip. This is not AIS data, so a general AIS website cannot show it. ## AIS Fleet and Saillogger Two products, one team, one platform, one company (Saillogger LLC). - Saillogger (https://saillogger.com) is the boater's product: a fully automatic marine logbook and deep NMEA 2000 monitoring for your own boat. It is where a voyage gets recorded. - AIS Fleet (https://aisfleet.com) is the follower's product. It is where the people watching that boat sign in. - A follower needs no Saillogger account, and a Saillogger boater needs no AIS Fleet account. A Saillogger boat is already on AIS Fleet once a receiver has heard her MMSI, and can be followed whatever her owner shares; what the owner's sharing switches decide is how much detail a follower sees. - A Saillogger boater who wants to follow other boats can do that inside Saillogger's own Friends feature (https://saillogger.com/friends/). AIS Fleet exists so their friends and family do not need a Saillogger account. - Both products read the same two owner settings, but they apply them differently. An AIS Fleet member may follow any boat, and privacy decides the detail. A Saillogger boater following through Friends cannot follow a private boat at all, and needs the access password for a protected one. ## How following works - Sign in at https://aisfleet.com with an e-mail address. A six-digit sign-in code is e-mailed to you; there is no password to choose or forget. A new account records your full name, which is how other members see you. - AIS Fleet is an account product: the map and personal features are behind sign-in, because your boats, your e-mails and your notification settings belong to your account, and some of what it shows is shared with you personally rather than published. The guide at https://aisfleet.com/docs/ and legal documents are public. - Find the boat by typing its name, MMSI, call sign or IMO number. The MMSI is the 9-digit identifier an AIS transponder broadcasts; a Saillogger boater finds theirs under Settings > Boat and on the Sharing tab. - Follow it, and the departure and arrival e-mails start. Following is one-way and needs no approval from the other person, but a Saillogger boater does see who follows them (below). - AIS Fleet identifies boats by MMSI, so it has to know the boat's MMSI. A boat with no transponder that has never been heard cannot be followed. - Any boat AIS Fleet has heard can be followed. What a Saillogger boat's owner shares decides the detail you get, not whether you may follow the boat. A publicly viewable boat gives you everything she publishes. If her owner has set an access password, following offers you the choice of entering it, which unlocks her journal, logged track and owner photo, or following her AIS position alone; the password is re-checked every time you look, so if the owner changes it you are asked again. A private boat is followed exactly like an ordinary AIS target: her broadcast position, and none of the owner's own material. Boats that are not running Saillogger are ordinary AIS targets, which is broadcast public information. - A seasonal pause does not cost a boater their followers: a boat whose owner has paused for the winter stays followable and goes live again on resume. - You can stop following a boat at any time from your lists (the Lists panel on the map). ## What the departure and arrival e-mails say - One e-mail when a boat you follow gets under way, and one when it arrives. There is no digest and no daily summary, so for a boat that makes several trips a day, a ferry for instance, you receive an e-mail each time. - For a Saillogger boat the message is richer. The departure names where she left from and maps where she is; the arrival names where she arrived, and where the passage began when that place can be identified, and carries a map of the passage she just completed when her owner publishes her individual trips publicly. The owner's photo of the boat leads the message when there is no map to show. For an ordinary AIS target it reports the departure or arrival with a position map. - Each event reaches you exactly once, however the boat happens to be tracked. - Every one of these e-mails links straight to that boat on your live map, and to your notification settings. - Notification settings at https://aisfleet.com/notifications/settings has seven rows: Followed boats, New followers, Direct messages, Fleet messages, Your stations, Your fleets and Your lists. Channels start on where offered. Each followed boat also has In app and E-mail choices. Favorites starts with notices on; custom and subscribed lists start with notices off. A list's map switch does not control its notices. Departures and arrivals share one preference. - Sign-in codes, claim and photo decisions, plan notices and fleet-addition notices are sent independently of those settings. Full settings guide: https://aisfleet.com/docs/departures-and-arrivals.md . - Push notifications come through the iPhone app, once Push is enabled on that phone in Notification settings. Otherwise e-mail is the way to receive notices while AIS Fleet is closed; in-app notices wait in the Notifications feed. ## What you see on the map - A marine chart with the AIS traffic AIS Fleet has received, your followed boats and your own boat drawn on it. It refreshes about every 45 seconds. - Lists and Fleets open panels with a map switch per list or fleet. Active fleets start on; a member's choices are remembered across devices. Fleets appears for a linked boat, pending claim, membership or plan that can run a fleet. Switching a layer does not move the camera: Show all offers that. - Enabled lists and fleets draw their plan-active boats beyond the current viewport and keep their last reported positions. Traffic and type filters do not hide those boats, the member's own boat or a selected vessel. Switching every list holding a followed boat off removes her list marker; she may still appear through another enabled layer or ordinary traffic. This does not unfollow her or mute notices. - The member's own boat and selected vessel are always named; list boats and fleet mates are named where their labels fit. See https://aisfleet.com/docs/the-vessel-map.md . - One colour per boat, in the order self, then followed, then fleet: a fleet mate you also follow is drawn as one you follow. - Vessels are coloured by type, and there are light and dark themes. - Ordinary traffic leaves the chart when nothing recent has been heard, but a boat you follow keeps her marker at her last known position however old it is. A visible followed marker is therefore not evidence of a recent report: read the last-heard time on her row or panel. A boat for whom no position has ever been reported has nothing to draw and appears only in the Lists panel. - A very busy viewport is capped at 1000 vessels and tells you when the view was truncated, so no boats are dropped without notice. - Selecting a boat shows its AIS track: the last 24 hours on the free plan, the last 7 days on Plus, the last 30 days on Pro. All three windows are offered on the panel; the ones beyond your plan say which plan unlocks them. ## Following a Saillogger boat This comes from Saillogger rather than from AIS, so a general AIS website does not have it. When the boat you follow keeps her log on Saillogger and shares it with you, her panel gains: - The owner's own photo of the boat. - Her journal: the dated notes and photos her owner posted from the trip. - Her logged voyage, drawn from Saillogger's own track rather than from AIS. - Her own position reports, sent from the boat whenever she has an Internet connection, so she can keep updating where no shore station is receiving her. Four conditions, all of them the owner's choice: 1. Sharing and Live Tracking are on for that boat (a private boat is still followable, but only as an AIS target, and a password-protected boat offers you its access password or an AIS-only follow). 2. Her MMSI is known to AIS Fleet. 3. For her own position reports, a separate switch: "Update your position on AIS Fleet" on the same Sharing tab. It governs the marker's source (her own reports, or only what AIS receivers hear) and is independent of the two switches above, which govern the detail. 4. She has an Internet connection at the time, for those position reports. Her logbook keeps recording without one, but the live position does not travel. The share check is made every time you look, not once when you followed, so if the owner stops sharing or changes the password, it stops immediately. ## Plans and pricing | Plan | Price | Boats you can follow | Lists | Active fleets | Fleets you run | Track history | Port calls | AI assistant | |-------|----------------|----------------------|-------|---------------|----------------|---------------|------------|--------------| | Basic | Free | 5 | 1 | 1 | 0 | 24 hours | 1 | No | | Plus | $1.99 / month | 25 | 3 | 3 | 1 | 7 days | 3 | Yes | | Pro | $4.99 / month | 100 | 10 | 10 | 5 | 30 days | 10 | Yes | - A paid plan buys you more boats to follow, more lists, more active fleets, a fleet or more of your own to run, a longer track behind each boat and more of each boat's port calls, and it lets you connect your own AI assistant; the map itself is the same on every plan. "Active fleets" is how many of the fleets you belong to stay active at once; "Fleets you run" is how many you may start and organize. The departure and arrival e-mails, the live map, vessel search and messages are on every plan, including the free one. "Port calls" is how many of a boat's latest port calls her panel lists, newest first. The port she is in now is shown as well and does not count toward that number. - Lists count created and subscribed lists together, excluding Favorites and Boats you photographed. Boats across lists share the follow limit; a boat counts once. After a downgrade, follows and lists beyond the limit stay listed but pause. See https://aisfleet.com/docs/lists.md . - The free plan is not a trial. It does not expire. - Website plans are monthly in US dollars through Stripe, managed at https://aisfleet.com/plan . App Store plans are billed and managed by Apple in local currency. Cancellation keeps access until the paid period ends. Deleting an AIS Fleet account does not cancel an App Store subscription; cancel it through Apple. See https://aisfleet.com/docs/plans-and-billing.md . - These caps are AIS Fleet's. Saillogger's own Friends feature has its own, separate limit for Saillogger boaters. ## For boaters: how to point your followers here If you keep your log on Saillogger and your family wants to follow along: - In Saillogger, open Settings > Sharing and turn on Sharing and Live Tracking & Monitoring. Optionally set an access password if you want to choose who sees you. - Give them your boat's name or MMSI (Settings > Boat, and on the Sharing tab). They sign in at https://aisfleet.com with their e-mail address and follow you. - They appear on your Followers page (https://saillogger.com/friends/followers/) with an AIS Fleet badge, and you get an e-mail when someone new follows you. - The same two switches govern it. If you turn off public tracking or change the access password, your journal, logged track and boat photo stop reaching your followers until you share again; they keep seeing the AIS position your transponder broadcasts, as they would on any AIS site. - You do not need an AIS Fleet account yourself, and following you costs them nothing. ## Fleets - A fleet is a group of boats on one map with its own members-only chat: a club, a rally, a cruising company, a class association. - A fleet is different from a list. A list is one member watching boats, one-way: the boats join nothing. A fleet is mutual: its boats see one another on a roster and share a chat, and a claimed boat's owner is told when the boat is added and can leave. See https://aisfleet.com/docs/lists.md . - A fleet is run by its organizer: a boater with a Saillogger account who created it there, or an AIS Fleet member on Plus (one fleet) or Pro (up to five) who started it at https://aisfleet.com/fleets/new on AIS Fleet. No boat is needed to run one. - A member joins a fleet by linking their own boat to their account (see "Can I put my own boat on it?" below) and then being added to the fleet's roster by its organizer, who adds boats by name or MMSI. There is no self-service join. Adding a boat claimed by a member sends that member a notice that is always delivered; a Saillogger boat is added only while her owner shares the boat publicly. Every fleet has a Leave control on its page and a one-tap leave link in every e-mail it sends; a member who leaves can block the organizer so they cannot add the boat again. - A fleet an AIS Fleet member runs is private to its members. If the organizer moves to a plan that runs fewer fleets, the first fleets they started stay live and the rest pause for everyone in them. - You do not need a fleet, or a boat, to follow boats and get the e-mails. ## Messages - Members can hold direct conversations with the boater behind a boat they follow, with anyone who follows their boat, and with their fleet mates. You can start a conversation only with people in those three groups. - Fleet chats are members-only, even for a fleet that is otherwise public, and membership is re-checked on every request. - You are shown to other members by your boat's name when one is linked to your account, and by the full name you published otherwise. Never by your e-mail address. - Messages are ordinarily removed after 30 days, and they are not end-to-end encrypted. - 1:1 messaging does not require a linked boat. Fleet chat does. ## Vessel photos - Any member can contribute a photo of a vessel to the shared vessel catalog. - Every submission is reviewed before it appears, under a separate contribution agreement (https://aisfleet.com/vessel-photo-contribution-agreement/). Published catalog photos carry a Saillogger mark drawn into the image, with the photographer's credit beside it when one was given and the rendering is large enough to carry it; the agreement does not promise credit with every use. A contributor can delete their own photo at any time (the permission the agreement grants survives that deletion). - Viewing a catalog photo does not give a license to use it. Saillogger LLC gives permission to use or display a catalog photo outside AIS Fleet and Saillogger, whether on another website, in an app or anywhere else, only under a separate written agreement that expressly authorizes that use or display of vessel photos. Being a Saillogger partner, service provider or customer does not by itself give that permission. - A boat owner's own photo, published through Saillogger, is a different thing: it is not moderated here and it is not watermarked. ## My Stations: sharing your own AIS receiver - A member with an AIS receiver, aboard or ashore, can contribute what it hears. Each shared receiver is a "station", listed at https://aisfleet.com/stations (**My Stations** in the account menu). Free on every plan, with no limit on how many stations a member runs. - Two kinds of station: a phone running the AIS Fleet iOS app, which contributes reports when a receiver is connected, sharing is on and internet is available (each iPhone has its own Share with AIS Fleet switch, under You > AIS receivers in the app, and all of them report as one station); and any receiver, plotter, NMEA gateway, multiplexer, AIS dispatcher or OpenCPN that streams its raw NMEA 0183 output over UDP to the host and port shown for it. - The vessels heard join the shared vessel data for every member and the licensed products. The receiver itself is private to its owner: no surface shows its name, position or existence to other members, and none says which receiver reported a vessel. Covered by section 3 of the Terms (https://aisfleet.com/terms/#shared-receivers). Guide: https://aisfleet.com/docs/share-your-ais-receiver/ ## Connecting an AI assistant (MCP) - A member on Plus or Pro can connect an AI assistant, such as Claude or ChatGPT, to their own account through AIS Fleet's MCP server at https://aisfleet.com/mcp . The assistant asks for access; the member signs in to AIS Fleet and approves it on an AIS Fleet page (OAuth). - It is read-only. It reads only what the member can already see when signed in: their plan, their own boat, the boats they follow, their lists and fleets, public AIS information about other vessels, Saillogger logs shared with them, their notices and their own AIS receivers. The member's plan limits and short-term limits apply to it as they do in the app. It cannot read messages or followers, and it cannot change anything. - AIS Fleet sends an assistant no alerts, so an assistant knows only what it finds when asked. - On Basic, the connection can still be made, but the assistant receives a sentence saying access is part of Plus and Pro instead of data. After a paid plan lapses, the connection stays in place and works again once the account is back on Plus or Pro, with nothing to reconnect. - Connected assistants are listed, and can be disconnected, under Connected apps on the Account screen. Guide: https://aisfleet.com/docs/connect-an-ai-assistant.md ## Privacy, safety, and what AIS Fleet is not - AIS Fleet is not a navigation, collision-avoidance, search-and-rescue or emergency service, and must not be used as one. AIS reports can be late, missing, duplicated or wrong. - Most of what AIS Fleet shows is AIS: information vessels broadcast publicly. - Anything that belongs to a Saillogger boater (their voyage track, their journal, their boat photo, their own position reports) is shown only because that boater chose to share it, and the check is repeated on every read rather than made once when you followed. - The app is behind sign-in. Analytics are cookieless, which is why there is no consent banner. - You must be 18 or over to hold an account. - A claimed boat's owner can remove a follower without notifying them; that person can follow again. Blocking direct messages is separate and does not hide AIS data or change fleet chat. Saillogger Sharing controls the journal, logged voyage and owner photo; its AIS Fleet integration switch controls directly shared positions. Neither setting stops radio broadcasts or removes copies held by other services. Privacy or safety concerns: info@saillogger.com. See https://aisfleet.com/docs/your-account-and-privacy.md . - Terms: https://aisfleet.com/terms/ . Privacy policy: https://aisfleet.com/privacy/ ## Common questions - What is AIS Fleet for? Following vessels that interest you, organizing them in lists and receiving detected departure and arrival notices. Some Saillogger owners also share a journal, a logged voyage and their boat photo. Start at https://aisfleet.com/docs/what-is-ais-fleet.md . - Do I need a boat? No. AIS Fleet needs no boat, no transponder and no equipment of any kind: it is built for the people ashore. - Do I have to install anything? No. It is a website and it runs in any phone or desktop browser. There is also an optional AIS Fleet app for iPhone, free to download from the App Store: it opens straight to the chart, and aboard a boat it can read an AIS receiver on the local Wi-Fi and draw the vessels around it, which a browser cannot do. The e-mail carrying a sign-in code links to it, and so do the sign-in screen and the map when opened in a browser on an iPhone. - Why do I have to sign in just to see a map? Your boats, your e-mails and your notification settings belong to your account, and some of what AIS Fleet shows is shared with you personally rather than published. Signing in is one e-mail address and a code; there is no password. - Will I see them mid-ocean? It depends on the boat. AIS is a shore-based radio system, so an ordinary AIS target usually goes quiet once it is well offshore and reappears when it is back in range. A boat that keeps her log on Saillogger and shares publicly reports her position from the boat herself whenever she has an Internet connection, so she can stay on the map far out. - Can I use it for navigation? No. AIS Fleet is not a navigation, collision-avoidance, search-and-rescue or emergency service. - How many e-mails is this going to be? One when a boat departs and one when it arrives. There is no digest, so for a boat that makes several trips a day you receive an e-mail each time. Departures and arrivals share one switch, "Followed boats", so you cannot switch one on or off without the other; the other kinds of e-mail (new followers, direct messages, fleet messages) have a switch each. - Can the boat's owner stop me following? A linked member can remove your follow, although you can follow again. Owners can block messages and control the Saillogger material they share. Those controls do not stop AIS broadcasts. AIS Fleet asks members to respect a request for privacy and does not allow re-following to harass anyone. See https://aisfleet.com/docs/your-boat-on-ais-fleet.md . - Can I put my own boat on it? Yes. Choose "Have a boat? You can claim" in the account menu, enter her MMSI, confirm the boat, and upload one document showing that MMSI is assigned to you or your boat (a ship radio licence or MMSI certificate; PDF or photo, up to 20 MB). A member of the Saillogger team checks it against the MMSI, you hear back within 48 hours, and the file is deleted within 72 hours of upload either way, with no copies kept. An MMSI that already belongs to an active Saillogger boat is not handed over by an ordinary claim. You do not need a linked boat to follow boats, get the e-mails, or hold one-to-one conversations; fleets and fleet chat need one. - I want to log my own voyages, not follow other people's. That is Saillogger, not AIS Fleet: https://saillogger.com - Is there an annual plan, a trial, or a refund? No annual plan and no trial. The free plan is permanently free, and a paid plan runs to the end of the period you have paid for when you cancel. - Why can I not find a boat I know exists? AIS Fleet identifies boats by MMSI. Search can return a vessel only after AIS Fleet has received a report for its MMSI. ## Machine-facing surfaces at a glance AIS Fleet has three machine-facing surfaces: 1. Agent data API (MPP and x402 machine payments). Open to any agent that can pay: a card, or stablecoin on Tempo or Base. No account, no API key, no signup. Priced per response. Documented in full below. 2. Partner API. Service-to-service AIS data for contracted partners, using a bearer key we issue. It cannot be self-served. 3. MCP server, for a member's own AI assistant: https://aisfleet.com/mcp . It reads only the signed-in member's own account, on Plus and Pro, after the member approves the connection (see "Connecting an AI assistant (MCP)" above). It needs a member account; for data without an account, use the agent data API. Everything else on aisfleet.com is a member web application, not an API. ## Agent data API (MPP and x402, machine payments) Buy one AIS Fleet vessel position, AIS track, port-call history, list of vessels in a port, monthly or annual Port Intelligence report, or the vessels heard in an area on one day, per request, paying per response. The same API sells marine weather at any point: a forecast, seven days of tide predictions, the latest wind observed nearby, and one weather station's day of readings (see "Weather, tides and forecasts" below). Vessel photos are not sold here (see "Vessel photos" above). There is no account to create and no key to obtain: an agent that can pay can call these endpoints directly. Two protocols answer on the same URLs, and you use whichever your client speaks: MPP (mpp.dev) a card, through a Stripe Shared Payment Token, or USDC on Tempo. Challenge on WWW-Authenticate, payment on Authorization, receipt on Payment-Receipt. x402 (x402.org) USDC on Base. Challenge on PAYMENT-REQUIRED, payment on PAYMENT-SIGNATURE, receipt on PAYMENT-RESPONSE. An unpaid request is answered with every payment option at once, on both sets of headers, and the first valid payment of either kind is what you are charged. Nothing about the products, the prices or the licence changes with the protocol you pick. Vessel products live under https://aisfleet.com/api/x402/v1/ais/vessels// where is a 9-digit ITU MMSI; port products under https://aisfleet.com/api/x402/v1/ais/ports// where is a five-character UN/LOCODE (for example NLRTM); the area day under https://aisfleet.com/api/x402/v1/ais/area/ with the box and the day in the query string. All endpoints are GET only (HEAD and POST return 405). All responses are JSON. ### Endpoints GET /api/x402/v1/ais/vessels//offer free, no payment GET /api/x402/v1/ais/vessels//position USD 0.01, JSON GET /api/x402/v1/ais/vessels//track-24h USD 0.05, JSON GET /api/x402/v1/ais/vessels//track-7d USD 0.15, JSON GET /api/x402/v1/ais/vessels//track-30d USD 0.50, JSON GET /api/x402/v1/ais/vessels//port-calls USD 0.02, JSON GET /api/x402/v1/ais/ports//offer free, no payment GET /api/x402/v1/ais/ports//vessels USD 0.50, JSON GET /api/x402/v1/ais/ports//intelligence-month?start=YYYY-MM-01 USD 1.00, JSON GET /api/x402/v1/ais/ports//intelligence-year?start=YYYY-MM-01 USD 10.00, JSON GET /api/x402/v1/ais/area/offer?bbox=&day=YYYY-MM-DD free, no payment GET /api/x402/v1/ais/area/day?bbox=&day=YYYY-MM-DD USD 0.02 a vessel, at least USD 0.50, JSON GET /api/x402/v1/marine/offer?lat=&lon= free, no payment GET /api/x402/v1/weather/forecast?lat=&lon= USD 0.01, JSON GET /api/x402/v1/tides/predictions?lat=&lon=[&start=YYYY-MM-DD] USD 0.01, JSON GET /api/x402/v1/weather/observations?lat=&lon=[&radius_nm=1-50] USD 0.01, JSON GET /api/x402/v1/weather/stations///day?day=YYYY-MM-DD USD 0.02, JSON GET /api/x402/v1/marine/conditions?lat=&lon= USD 0.02, JSON Positions are AIS Fleet network observations of the requested MMSI, sold only while recent, with speed and course over ground when the observation reported them. Tracks are up to 1000 evenly sampled fixes from an inclusive window ending at the newest fix, sold only for vessels the network currently observes; a gap between fixes means no reception, never interpolation. Port calls are UN/LOCODE arrivals and departures of the last 30 days, boundaries not directly observed flagged estimated, plus the port the vessel was confirmed in within the last 7 days; capture coverage began 2026-08-23 and every response names it. Vessels-in-port is the list of vessels the network confirmed in one port within the last 7 days. Port Intelligence returns every eligible vessel and visit in one port's caller-selected arrival cohort, including visit count, MMSI and available identity/dimensions, arrivals, departures, durations, boundary-quality flags and summary statistics, but no coordinates. Monthly covers one calendar month for USD 1.00; annual covers 12 calendar months for USD 10.00 and may start in any month. Large reports use a streamed HTTP response but keep exactly the same JSON shape, price and complete contents. The area day is every vessel the network heard inside one box (west, south, east, north in decimal degrees, at most 2,000 square nautical miles, not crossing the 180th meridian) on one complete past UTC day, each with its identity and every privacy-eligible position fix; it costs USD 0.02 for each vessel heard and never less than USD 0.50, a box where nothing was heard included, and a longer period is one request per day. ### Step 1: the free offer manifest Always start here. It is free, and it tells you whether anything is purchasable and how fresh it is before you spend anything. Request: GET /api/x402/v1/ais/vessels/367800002/offer HTTP/1.1 Host: aisfleet.com Accept: application/json Response (200): { "provider": "AIS Fleet", "mmsi": "367800002", "offers": { "position": { "available": true, "price": {"amount": "0.01", "currency": "USD"}, "url": "https://aisfleet.com/api/x402/v1/ais/vessels/367800002/position", "observed_at": "2026-08-12T18:42:10Z", "age_seconds": 720, "area": "Salish Sea", "payment": { "x402": {"network": "eip155:8453", "asset": "USDC"}, "mpp": {"intent": "charge", "methods": ["tempo"]} } }, "track-24h": { "available": true, "window_hours": 24, "price": {"amount": "0.05", "currency": "USD"}, "url": "https://aisfleet.com/api/x402/v1/ais/vessels/367800002/track-24h", "payment": { "x402": {"network": "eip155:8453", "asset": "USDC"}, "mpp": {"intent": "charge", "methods": ["tempo"]} }, "fix_count": 214, "newest_fix_at": "2026-08-12T18:42:10Z" }, "track-7d": { "available": true, "window_hours": 168, "price": {"amount": "0.15", "currency": "USD"}, "url": "https://aisfleet.com/api/x402/v1/ais/vessels/367800002/track-7d", "payment": { "x402": {"network": "eip155:8453", "asset": "USDC"}, "mpp": {"intent": "charge", "methods": ["tempo"]} }, "fix_count": 655, "newest_fix_at": "2026-08-12T18:42:10Z" }, "track-30d": { "available": true, "window_hours": 720, "price": {"amount": "0.50", "currency": "USD"}, "url": "https://aisfleet.com/api/x402/v1/ais/vessels/367800002/track-30d", "payment": { "x402": {"network": "eip155:8453", "asset": "USDC"}, "mpp": {"intent": "charge", "methods": ["stripe", "tempo"]} }, "fix_count": 2104, "newest_fix_at": "2026-08-12T18:42:10Z" }, "port-calls": { "available": true, "window_days": 30, "price": {"amount": "0.02", "currency": "USD"}, "url": "https://aisfleet.com/api/x402/v1/ais/vessels/367800002/port-calls", "payment": { "x402": {"network": "eip155:8453", "asset": "USDC"}, "mpp": {"intent": "charge", "methods": ["tempo"]} }, "coverage_start": "2026-08-23T00:00:00Z", "call_count": 4, "newest_arrival_at": "2026-08-25T06:03:00Z", "in_port_now": true } }, "license_url": "https://aisfleet.com/agent-data-license/" } Fields: provider always the string "AIS Fleet". mmsi the requested MMSI, as a string of 9 digits. available whether that product can be bought for this MMSI right now. price.amount a decimal string in US dollars. currency is always "USD". url the exact URL at which to buy that product. payment how that product can be paid for right now, protocol by protocol. Only options that can actually complete are listed: "stripe" (card) is absent from the position, because Stripe will not charge a card for less than USD 0.50. observed_at UTC, ISO 8601, seconds precision, "Z" suffix. Position only, and only when available is true. age_seconds integer seconds since observed_at, as of the response. Position only, and only when available is true. area one broad water body name (an ocean, sea, gulf, bay, strait, channel or lake) when one resolves. Optional, never more precise than that, position only. fix_count track offers, when available: how many fixes the window holds in the inclusive interval ending at newest_fix_at, so you never buy an empty or one-point track. The paid response is sampled down to at most 1000 points. newest_fix_at track offers, when available: when the newest fix in the window was observed. window_hours track offers: the window that product covers. window_days the port-calls offer: always 30. coverage_start port-calls offer: when port-call capture began. History is no deeper than this, and it grows daily. call_count port-calls offer, when available: calls in the window. newest_arrival_at port-calls offer, when available: her newest arrival. in_port_now port-calls offer, when available: whether she is in a port now: an open call confirmed within the last 7 days (the paid response names it). license_url the licence that governs anything you buy. The offer never contains coordinates. ### The free port offer manifest The port offer at /api/x402/v1/ais/ports//offer is the same idea for a UN/LOCODE port, and carries all three port products: GET https://aisfleet.com/api/x402/v1/ais/ports/NLRTM/offer { "provider": "AIS Fleet", "port": {"locode": "NLRTM", "name": "Rotterdam", "country": "NL"}, "port_intelligence_coverage": { "earliest_complete_month_start": "2026-09-01", "earliest_annual_start": "2026-09-01", "first_annual_available_on": "2027-09-01" }, "offers": { "port-vessels": { "available": true, "price": {"amount": "0.50", "currency": "USD"}, "url": "https://aisfleet.com/api/x402/v1/ais/ports/NLRTM/vessels", "payment": { "x402": {"network": "eip155:8453", "asset": "USDC"}, "mpp": {"intent": "charge", "methods": ["stripe", "tempo"]} }, "coverage_start": "2026-08-23T00:00:00Z", "vessel_count": 63, "newest_arrival_at": "2026-08-25T06:03:00Z" }, "port-intelligence-month": { "available": true, "calendar_months": 1, "start_format": "YYYY-MM-01", "suggested_start": "2026-10-01", "price": {"amount": "1.00", "currency": "USD"}, "url": "https://aisfleet.com/api/x402/v1/ais/ports/NLRTM/intelligence-month?start=2026-10-01", "payment": { "x402": {"network": "eip155:8453", "asset": "USDC"}, "mpp": {"intent": "charge", "methods": ["stripe", "tempo"]} }, "coverage_start": "2026-08-23T00:00:00Z", "window_start": "2026-10-01T00:00:00Z", "window_end": "2026-11-01T00:00:00Z", "visit_count": 1841, "vessel_count": 764 }, "port-intelligence-year": { "available": false, "calendar_months": 12, "start_format": "YYYY-MM-01", "suggested_start": null, "price": {"amount": "10.00", "currency": "USD"}, "url": null, "payment": { "x402": {"network": "eip155:8453", "asset": "USDC"}, "mpp": {"intent": "charge", "methods": ["stripe", "tempo"]} }, "coverage_start": "2026-08-23T00:00:00Z" } }, "license_url": "https://aisfleet.com/agent-data-license/" } Port fields, beyond the shared available / price / url / payment / coverage_start above: vessel_count vessels-in-port: how many are in the port now. On an intelligence entry: distinct vessels in that period. newest_arrival_at vessels-in-port, when available: the newest arrival. calendar_months 1 for the monthly report, 12 for the annual one. start_format always "YYYY-MM-01". suggested_start the period we recommend buying: the latest complete one that capture also covers from its first instant. NULL when there is no such period yet, and then url is null too. In that case, read port_intelligence_coverage instead of guessing a period. window_start the suggested period's exact bounds. window_end is window_end exclusive, as in the paid response. visit_count eligible visits in the suggested period, so you know how much report a purchase buys before paying. However large the number, an available report is sold whole at the listed price. port_intelligence_coverage is the calendar answer for the whole API, not for this port. The example reflects capture beginning partway through August 2026: July and August 2026 cannot be sold as complete months, September 2026 is the first supported start for either SKU, and first_annual_available_on is the earliest date that first 12-month window is both covered and finished. Real availability additionally needs privacy-eligible traffic at the port and a configured payment method, which is what "available" reports. The offer never lists the report's vessels themselves. ### The free area offer The area offer prices one box on one day before you buy it. Name the box as bbox=west,south,east,north in decimal degrees (at most 2,000 square nautical miles; a box may not cross the 180th meridian, so split one that does into two requests) and one complete past UTC day as day=YYYY-MM-DD: GET https://aisfleet.com/api/x402/v1/ais/area/offer?bbox=-9.5,38.0,-9.0,38.5&day=2026-09-10 { "provider": "AIS Fleet", "area": {"bbox": [-9.5, 38.0, -9.0, 38.5], "area_nm2": 707.5, "max_area_nm2": 2000}, "day": "2026-09-10", "coverage": {"earliest_day": "2026-08-07", "latest_day": "2026-10-08"}, "offers": { "area-day": { "available": true, "price": {"amount": "3.36", "currency": "USD"}, "pricing": {"per_vessel": {"amount": "0.02", "currency": "USD"}, "minimum": {"amount": "0.50", "currency": "USD"}}, "url": "https://aisfleet.com/api/x402/v1/ais/area/day?bbox=-9.5000,38.0000,-9.0000,38.5000&day=2026-09-10", "payment": { "x402": {"network": "eip155:8453", "asset": "USDC"}, "mpp": {"intent": "charge", "methods": ["stripe", "tempo"]} }, "vessel_count": 168, "fix_count": 3142 } }, "license_url": "https://aisfleet.com/agent-data-license/" } The price is USD 0.02 for each vessel heard in the box that day, and never less than USD 0.50. At the minimum (25 vessels or fewer, or none at all) the offer gives the price but not the counts: "vessel_count" is null and "vessel_count_note" reads "25 or fewer, possibly none". A box where nothing was heard still costs the minimum. Coordinates are normalized to four decimal places, and the url in the offer is the exact one to pay for. A longer period is one request per day: the coverage block names the earliest and latest days on sale, and history before the earliest day is not kept. While many other area requests are being priced, the offer and the paid endpoint answer 503 with Retry-After; retry after that many seconds. Notes that matter: - The offer is cached for up to 60 seconds (Cache-Control: public, max-age=60). Polling it faster returns the same answer. - The offer is advisory, not a reservation. The paid endpoint re-checks eligibility before it asks you for payment, so an offer that said "available": true can still answer 404. This is expected behavior, and you are not charged for data we cannot deliver. - "available": false means nothing is purchasable for that MMSI right now. It does not mean the vessel does not exist, and it carries no other meaning. - A position is sold only while it is recent: at most 6 hours old, and at most 5 minutes ahead of our clock (clock-skew tolerance). Decide with observed_at and age_seconds before you spend. ### Step 2a: paying with x402 x402 is an open protocol that revives HTTP 402: the server answers an unpaid request with a machine-readable payment challenge, and the client retries the same request carrying a signed payment. AIS Fleet implements x402 version 2 with the "exact" scheme, so each response has one fixed price. What you need: a wallet on Base holding USDC, and an x402-capable HTTP client. The reference clients (for example the "x402" Python package, or x402-fetch and x402-axios for TypeScript) implement the whole loop for you. Nothing here is client-specific: any correct x402 version 2 client works. Payment parameters, as advertised in the challenge: protocol x402, version 2 scheme exact network eip155:8453 (Base mainnet) asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 (USDC on Base, 6 decimals) amount "10000" atomic units for a position (USD 0.01) "50000" for a 24h track (USD 0.05) "150000" for a 7-day track (USD 0.15) "500000" for a 30-day track (USD 0.50) "20000" for port calls (USD 0.02) "500000" for vessels in port (USD 0.50) "1000000" for monthly port intelligence (USD 1.00) "10000000" for annual port intelligence (USD 10.00) payTo read it from the challenge. Do not hardcode it. maxTimeoutSeconds 300 The loop: 1. Send the request with no payment header. 2. You get 402 with a PAYMENT-REQUIRED header. The body is: {"error": "Payment required", "offer_url": "https://aisfleet.com/api/x402/v1/ais/vessels/367800002/offer"} PAYMENT-REQUIRED is base64-encoded JSON. Decoded, it looks like: { "x402Version": 2, "error": "Payment required", "resource": { "url": "https://aisfleet.com/api/x402/v1/ais/vessels/367800002/position", "mimeType": "application/json", "serviceName": "AIS Fleet", "tags": ["ais", "vessel", "position", "maritime"] }, "accepts": [{ "scheme": "exact", "network": "eip155:8453", "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913", "amount": "10000", "payTo": "0x...", "maxTimeoutSeconds": 300, "extra": {"name": "USD Coin", "version": "2"} }], "extensions": {"bazaar": ...} } There is exactly one entry in "accepts". The "bazaar" extension carries an x402 Bazaar format declaration, including the route template (/api/x402/v1/ais/vessels/:mmsi/position), its path parameters with a fixed example value (the same for every request), and a JSON Schema for the response, so a discovery-capable client can learn the whole contract from the challenge itself. 3. Sign a payment for that exact amount, asset, network and payTo. 4. Repeat the same GET, adding the payment header: GET /api/x402/v1/ais/vessels/367800002/position HTTP/1.1 Host: aisfleet.com PAYMENT-SIGNATURE: 5. You get 200 with the product, and a PAYMENT-RESPONSE header carrying the settlement receipt (base64-encoded JSON, including the transaction hash). ### Step 2b: paying with MPP MPP (mpp.dev) is an open protocol that carries the same 402 exchange on the standard RFC 9110 authentication headers. The server answers an unpaid request with one or more challenges on WWW-Authenticate, and the client retries the same request with Authorization: Payment. AIS Fleet implements the "charge" intent. What you need: an MPP-capable client (for example mppx for TypeScript, or the Python SDK) with either a card grant or a Tempo wallet. Nothing here is client-specific. The methods advertised: tempo USDC on Tempo (chainId 4217, 6 decimals). Every product. recipient is our Stripe deposit address; read it from the challenge. stripe a card, charged through a Stripe Shared Payment Token (spt_...). Only where the price is USD 0.50 or more, because a card cannot be charged below that: track-30d, port-vessels, port-intelligence-month, port-intelligence-year. The cheaper products (position, track-24h, track-7d, port-calls) are Tempo-only. Read each product's payment.mpp.methods in the free offer rather than assuming a card works. The loop: 1. Send the request with no Authorization header. 2. You get 402. WWW-Authenticate carries one Payment challenge per method, in one header value, comma-separated: WWW-Authenticate: Payment id="", realm="aisfleet.com", method="stripe", intent="charge", request="", expires="2026-08-12T18:47:10Z", description="AIS Fleet vessel track, last 30 days", Payment id="", realm="aisfleet.com", method="tempo", intent="charge", request="", expires="..." Each "request" decodes to the terms of that offer, including an "extra" naming the exact resource it buys, for example: {"amount": "500000", "currency": "0x20C000000000000000000000b9537d11c60E8b50", "recipient": "0x...", "extra": {"resource": "https://aisfleet.com/api/x402/v1/ais/vessels/367800002/track-30d"}, "methodDetails": {"chainId": 4217, "feePayer": false}} {"amount": "50", "currency": "usd", "methodDetails": {"networkId": "profile_...", "paymentMethodTypes": ["card"]}} The challenge id is an HMAC over the challenge itself, so the challenge is the whole state: echo it back unchanged. Any edit to the amount, recipient, resource or expiry invalidates it. A challenge pays for the one resource it names and no other, so buy each vessel with its own challenge. A challenge is valid for 5 minutes. 3. Pay the challenge you chose and retry the same GET with the credential: GET /api/x402/v1/ais/vessels/367800002/track-30d HTTP/1.1 Host: aisfleet.com Authorization: Payment The credential is {"challenge": {...echoed...}, "payload": {...}}, where the payload is the method's proof of payment: tempo {"type": "transaction", "signature": "0x..."} for a signed TIP-20 transfer we broadcast for you, or {"type": "hash", "hash": "0x..."} for one you broadcast yourself. Either way the transfer must carry the MPP attribution memo binding it to that challenge; standard clients add it. A transfer without it is not accepted, because a transaction hash is public and anyone could otherwise present someone else's. stripe {"spt": "spt_..."} a Shared Payment Token scoped to the amount. 4. You get 200 with the product and a Payment-Receipt header: base64url JSON with status, timestamp, method and reference (the Tempo transaction hash, or the Stripe payment id). A payment that cannot be accepted answers 402 with RFC 9457 problem details (Content-Type: application/problem+json) naming what went wrong, plus a fresh WWW-Authenticate so you can retry without a second round trip: {"type": "https://paymentauth.org/problems/verification-failed", "title": "Payment Verification Failed", "status": 402, "detail": "Payment could not be verified", "offer_url": "https://aisfleet.com/api/x402/v1/ais/vessels/367800002/offer"} The problem types you can see are payment-required (the plain unpaid answer), malformed-credential, method-unsupported, payment-expired and verification-failed (which also covers a payment that did not settle). ### Paid position response HTTP/1.1 200 OK Content-Type: application/json Cache-Control: private, no-store, max-age=0, no-cache, must-revalidate Link: ; rel="license" PAYMENT-RESPONSE: (x402 payments) Payment-Receipt: (MPP payments) { "provider": "AIS Fleet", "mmsi": "367800002", "position": {"latitude": 47.7, "longitude": -122.4}, "speed_over_ground_knots": 6.4, "course_over_ground_degrees": 213.0, "observed_at": "2026-08-12T18:42:10Z", "age_seconds": 720, "license_url": "https://aisfleet.com/agent-data-license/" } Those fields are the whole response. Coordinates are WGS 84 decimal degrees; speed is knots, course is degrees true, and both motion fields are null when the observation reported no motion. ### Paid track response (track-24h, track-7d, track-30d) { "provider": "AIS Fleet", "mmsi": "367800002", "window_hours": 24, "window_start": "2026-08-11T18:42:10Z", "window_end": "2026-08-12T18:42:10Z", "fixes_in_window": 214, "point_count": 214, "sampled": false, "max_points": 1000, "point_time_unit": "unix_ms", "points": [ {"lat": 47.7, "lng": -122.4, "time": 1754590930000, "speed": 6.4} ], "license_url": "https://aisfleet.com/agent-data-license/" } The inclusive window is [window_start, window_end] and ends at the newest fix, not at the moment you paid. The offer's fix_count uses that exact interval. Points are ordered oldest first; time is milliseconds since the Unix epoch, UTC; speed is knots or null. When fixes_in_window exceeds max_points the points are evenly sampled across the whole window and "sampled" is true, with both endpoints kept. A gap between consecutive points means no reception, never interpolation. ### Paid port-calls response { "provider": "AIS Fleet", "mmsi": "367800002", "window_days": 30, "window_start": "2026-07-26T06:03:00Z", "window_end": "2026-08-25T06:03:00Z", "coverage_start": "2026-08-23T00:00:00Z", "current_port": { "locode": "NLRTM", "port_name": "Rotterdam", "country": "NL", "arrived_at": "2026-08-25T06:03:00Z", "arrival_estimated": false }, "calls": [ {"locode": "NLRTM", "port_name": "Rotterdam", "country": "NL", "arrived_at": "2026-08-25T06:03:00Z", "departed_at": null, "arrival_estimated": false, "departure_estimated": false, "duration_seconds": null} ], "call_count": 1, "truncated": false, "anchorage_coverage_start": "2026-08-23T00:00:00Z", "current_anchorage": null, "anchorage_waits": [ {"locode": "NLRTM", "port_name": "Rotterdam", "country": "NL", "arrived_at": "2026-08-23T22:40:00Z", "departed_at": "2026-08-25T05:30:00Z", "arrival_estimated": false, "departure_estimated": false, "duration_seconds": 111000} ], "anchorage_wait_count": 1, "anchorage_waits_truncated": false, "license_url": "https://aisfleet.com/agent-data-license/" } Calls are ordered newest arrival first and are the calls whose **arrival** falls in the 30 days up to window_end (her newest arrival). A null departed_at means the departure has not been observed; only current_port claims current presence, and it repeats the open call only while last_seen_at was within 7 days. A boundary flagged estimated was not directly observed: the timestamp is a best effort, so exact-duration analysis should filter both flags false. History is no deeper than coverage_start, and it grows daily. Her waits at anchor off a port are reported apart from her calls: never in calls, call_count or current_port. anchorage_waits lists them in the same shape and order as calls, every wait that began since window_start, including one after window_end. current_anchorage names the wait she is in now, on the same 7-day rule as current_port. anchorage_coverage_start is when waits began to be reported apart; none is listed from before it. Both sections describe the same snapshot: current_port and current_anchorage cannot both be set. ### Paid vessels-in-port response { "provider": "AIS Fleet", "port": {"locode": "NLRTM", "name": "Rotterdam", "country": "NL"}, "newest_arrival_at": "2026-08-25T06:03:00Z", "coverage_start": "2026-08-23T00:00:00Z", "vessels": [ {"mmsi": "367800002", "name": "EXAMPLE TRADER", "arrived_at": "2026-08-25T06:03:00Z", "arrival_estimated": false} ], "vessel_count": 42, "truncated": false, "anchorage_coverage_start": "2026-08-23T00:00:00Z", "at_anchorage": [ {"mmsi": "244660000", "name": "EXAMPLE TANKER", "arrived_at": "2026-08-24T18:05:00Z", "arrival_estimated": false} ], "at_anchorage_count": 1, "at_anchorage_truncated": false, "license_url": "https://aisfleet.com/agent-data-license/" } Vessels are ordered by arrival, longest in port first, and are every vessel with an open call confirmed at that port within the last 7 days. It is a presence list, not a position report: no coordinates are included. at_anchorage lists, in the same shape and order, the vessels at anchor off the port now. They are reported apart: a vessel waiting there is never in vessels or vessel_count. Both sections describe the same snapshot, including when a vessel changes between a berth and an anchorage during the request. ### Paid Port Intelligence response Both products require exactly one query parameter: start=YYYY-MM-01 The value is a UTC first-of-month calendar boundary. It may name any month for either product, including an annual report: start=2025-02-01 produces an annual window ending 2026-02-01, not a January-to-December report. The end is exclusive. The month product adds one calendar month; the year product adds 12 calendar months. Fixed 31-day and 365-day arithmetic is never used, so months do not overlap and leap years are correct. Example monthly request: GET /api/x402/v1/ais/ports/NLRTM/intelligence-month?start=2025-02-01 Example paid response (abridged to one vessel, but the real arrays are not truncated): { "provider": "AIS Fleet", "product": "port-intelligence-month", "port": {"locode": "NLRTM", "name": "Rotterdam", "country": "NL"}, "window_start": "2025-02-01T00:00:00Z", "window_end": "2025-03-01T00:00:00Z", "window_end_exclusive": true, "calendar_months": 1, "visit_basis": "arrival_at", "coverage_start": "2024-01-01T00:00:00Z", "anchorage_coverage_start": "2025-06-01T00:00:00Z", "summary": { "vessel_count": 1, "visit_count": 2, "repeat_vessel_count": 1, "completed_visit_count": 2, "departure_not_observed_count": 0, "estimated_arrival_count": 0, "estimated_departure_count": 0, "observed_dwell_seconds": { "sample_visits": 2, "total": 43200, "average": 21600, "median": 21600 } }, "anchorage_summary": null, "periods": [{ "month": "2025-02", "window_start": "2025-02-01T00:00:00Z", "window_end": "2025-03-01T00:00:00Z", "summary": { "vessel_count": 1, "visit_count": 2, "repeat_vessel_count": 1, "completed_visit_count": 2, "departure_not_observed_count": 0, "estimated_arrival_count": 0, "estimated_departure_count": 0, "observed_dwell_seconds": { "sample_visits": 2, "total": 43200, "average": 21600, "median": 21600 } }, "vessels": [{ "mmsi": "367860010", "imo": "1234567", "name": "EXAMPLE TRADER", "call_sign": "ABCD", "flag": "NL", "ais_type": 70, "vessel_kind": {"kind": "cargo", "label": "Cargo"}, "length_meters": 180.0, "beam_meters": 28.0, "draught_meters": 9.2, "visit_count": 2, "completed_visit_count": 2, "total_stay_seconds": 43200, "observed_dwell_seconds": { "sample_visits": 2, "total": 43200, "average": 21600, "median": 21600 }, "visits": [ { "arrived_at": "2025-02-03T09:00:00Z", "departed_at": "2025-02-03T17:00:00Z", "duration_seconds": 28800, "last_confirmed_at": "2025-02-03T17:00:00Z", "arrival_estimated": false, "departure_estimated": false }, { "arrived_at": "2025-02-20T10:00:00Z", "departed_at": "2025-02-20T14:00:00Z", "duration_seconds": 14400, "last_confirmed_at": "2025-02-20T14:00:00Z", "arrival_estimated": false, "departure_estimated": false } ] }], "anchorage_summary": null, "anchorage_vessels": null }], "license_url": "https://aisfleet.com/agent-data-license/" } The annual response has the same shape, product "port-intelligence-year", calendar_months 12, and exactly 12 chronological period objects. Each names its calendar month as `month: "YYYY-MM"`. Every calendar month is present even when its vessels array and counts are empty. The top-level summary merges the same MMSI across all 12 sections; each section's summary and vessel visit_count apply only to that month. Waits at anchor off the port are reported apart from its visits and never counted as one. A month's anchorage_summary and anchorage_vessels have the same shapes as its summary and vessels, a vessel's visits there being her waits, and the top-level anchorage_summary merges every month's. A month that began before anchorage_coverage_start has both null rather than partial, as in the example above, and the top-level anchorage_summary is null unless every month has them. A visit belongs to the period whose half-open interval contains arrived_at: [window_start, window_end). A vessel already in port before the start is not in that arrival cohort; a call arriving exactly at the exclusive end belongs to the next report. A selected call remains in the report if its departure occurs after the period end. A null departed_at means no departure has been observed, and duration_seconds is null with it. duration_seconds is **also** null in the rare case where a departure is recorded but the two timestamps do not order (a vessel's own clock can run ahead of ours), so read departed_at, not duration_seconds, to decide whether a visit closed. Estimated flags always remain attached to their boundaries. total_stay_seconds includes every completed, nonnegative duration, including a best-effort estimated boundary. observed_dwell_seconds is the conservative sample: only completed, nonnegative visits whose arrival and departure were both directly observed. average and median are null when sample_visits is zero. The response contains no coordinates. Vessel dimensions are filtered by the same per-dimension plausibility bounds the site itself uses, so a self-declared implausible length, beam, or draught arrives as null rather than as a number. A report is never truncated: every vessel allowed by the port-data privacy gate and every qualifying visit is in it, however busy the period, at the listed price. The free port offer's visit_count tells you the size before you pay. Size never makes an otherwise eligible report unavailable; it only determines whether the server returns the same JSON from memory or as a streamed body. A report is offered only after its complete window has ended and only when capture began no later than window_start. Port-call capture began 2026-08-23, so the first fully covered start is 2026-09-01; a monthly report from that start can first be bought on 2026-10-01, and the corresponding annual report can first be bought on 2027-09-01. A valid but incomplete, pre-coverage, empty, or all-private report answers 404 before presenting a payment challenge. A Port Intelligence purchase pins the **period**, not a byte-exact snapshot: the report describes a fixed past, but our knowledge of it can still improve (a departure observed after the month ended, an estimate refined, a boater's consent withdrawn). A retry of a paid request returns the current report of exactly the period you bought, reflecting any such reconciliation. If every eligible visit has since been withdrawn, your purchase still settles and collects: the report arrives empty (every month present, zero vessels) rather than your payment being lost. Only a fresh, unpaid request for such a period answers 404; you cannot buy an empty report, but one you already bought always renders. For an emptied report, an MPP retry is recognized by its original signed challenge. An x402 retry is recognized only when that signed authorization was already bound to this exact report by an earlier verified request. A new x402 authorization first presented after the report emptied receives the same 404 and no payment challenge; it cannot turn an empty report back into a sale. A transient database, spool or serialization failure can still answer 503, but report size itself cannot. With x402 the complete body is built before settlement, so that failure moves no money. Uniquely to this product, an MPP payment settles and is recorded before the report is built; if a transient 503 follows an MPP payment, retry the identical request with the identical credential to collect the recorded purchase. You are never charged twice. ### Paid area day response { "provider": "AIS Fleet", "product": "area-day", "area": {"bbox": [-9.5, 38.0, -9.0, 38.5], "area_nm2": 707.5}, "day": "2026-09-10", "window_start": "2026-09-10T00:00:00Z", "window_end": "2026-09-11T00:00:00Z", "window_end_exclusive": true, "point_time_unit": "unix_ms", "vessels": [ { "mmsi": "263000001", "imo": "9876543", "name": "EXAMPLE TRADER", "call_sign": "CSXX", "flag": "PT", "ais_type": 70, "vessel_kind": {"kind": "cargo", "label": "Cargo"}, "length_meters": 180.0, "beam_meters": 28.0, "draught_meters": 9.2, "fix_count": 2, "first_fix_at": "2026-09-10T12:00:00Z", "last_fix_at": "2026-09-10T12:05:00Z", "points": [ {"time": 1789041600000, "lat": 38.5, "lng": -9.0, "speed": 5.0, "course": 90.0}, {"time": 1789041900000, "lat": 38.25, "lng": -9.25, "speed": 11.2, "course": 287.4} ] } ], "vessel_count": 1, "fix_count": 2, "license_url": "https://aisfleet.com/agent-data-license/" } Every vessel heard inside the box that day, edges included, with every position fix of hers inside it, oldest first: time in epoch milliseconds, speed over ground in knots and course over ground in degrees, each null when the report carried none. Identity is the vessel's as AIS Fleet holds it today, with dimensions filtered for plausibility. Fixes are kept at most every five minutes per vessel, and a gap means no reception, never interpolation. Each fix is sold only when it may be: a boat's own reports are left out unless she shares them, including on retries of an earlier purchase. Delivery stays with the fixes heard up to the quote; later arrivals require a new purchase. A box where nothing was heard, or a purchase whose fixes are no longer eligible, returns an empty vessels list. The response is streamed but always complete for that purchase, and vessel_count and fix_count describe exactly what it holds. Like a Port Intelligence report, an MPP payment settles before the response is built; a retry with the identical credential collects it, never charged twice. ### Weather, tides and forecasts Five products at a point (lat and lon in decimal degrees), on the same rails, headers and rules as the vessel products. Each costs less than a card's USD 0.50 minimum, so they are paid over x402 (USDC on Base) or MPP with USDC on Tempo, never by card. weather-forecast The newest ECMWF 9 km (0.1 degree) open-data run at the nearest grid point, up to 15 days: 3-hourly to 144 hours, then 6-hourly. Wind speed and gust in knots and the direction it blows from, pressure (hPa), rain per step (mm), cloud (%), air temperature (C), thunderstorm potential (CAPE, J/kg), ocean current (knots, the direction it sets towards) and waves (height, direction, mean and peak period). ECMWF publishes its open-data runs about 9 hours after their run time; run_time names the one you get. Near a coast, waves and currents come from the nearest sea point (at most 0.5 degree away for waves), named in grid_points. tide-predictions Seven days from start (default today, UTC): high and low water to the minute and hourly heights, in metres above chart datum where the source has one (MLLW in the US, the lowest astronomical tide elsewhere, otherwise mean sea level; "datum" says which). The nearest tide station within 10 nm answers, else a global tide model, and "source" names which, with its distance. Where a tidal current station is within 5 nm, "currents" lists slack water and the strongest flood and ebb. The astronomical tide only: no surge, pressure, wind or river flow. A point no source answers for (inland) is 404, before any payment. weather-observations The newest wind reading, as of the moment the request was quoted, at each fixed station within radius_nm (1 to 50, default 25): airports, buoys, coastal and synoptic stations, up to 10, nearest first, with observation time, age, mean speed and gust in knots and direction. Also up to 10 boats sharing their wind: the mean over 15 minutes, its peak and direction, anonymous, positions rounded to 0.01 degree. One price whatever is found: the answer can be empty, and the free offer counts the fixed stations first (never the boats). weather-station-day Every reading one fixed station reported on one complete past UTC day, within the last 29 days. The station is its network (icao, wmo or ndbc) and code, as the free offer and the observations name it. marine-conditions The forecast, the tide predictions from today (null where no source answers) and the observations within 25 nm, in one response. Free offer, the place to start for a point: GET https://aisfleet.com/api/x402/v1/marine/offer?lat=50.76&lon=-1.3 { "provider": "AIS Fleet", "point": {"latitude": 50.76, "longitude": -1.3}, "offers": { "weather-forecast": { "available": true, "price": {"amount": "0.01", "currency": "USD"}, "url": "https://aisfleet.com/api/x402/v1/weather/forecast?lat=50.7600&lon=-1.3000", "payment": {"x402": {"network": "eip155:8453", "asset": "USDC"}}, "run_time": "2026-10-28T18:00:00Z", "published_at": "2026-10-29T02:35:33Z" }, "tide-predictions": { "available": true, "price": {"amount": "0.01", "currency": "USD"}, "url": "https://aisfleet.com/api/x402/v1/tides/predictions?lat=50.7600&lon=-1.3000&start=2026-10-29", "payment": {"x402": {"network": "eip155:8453", "asset": "USDC"}}, "days": 7, "source": {"kind": "model", "distance_nm": 0.4, "extrapolated": false}, "currents_near": false }, "weather-observations": { "available": true, "price": {"amount": "0.01", "currency": "USD"}, "url": "https://aisfleet.com/api/x402/v1/weather/observations?lat=50.7600&lon=-1.3000&radius_nm=25", "payment": {"x402": {"network": "eip155:8453", "asset": "USDC"}}, "radius_nm": 25, "fixed_station_count": 3, "note": "Counts fixed stations that reported in the last 3 hours. ..." }, "marine-conditions": { "available": true, "price": {"amount": "0.02", "currency": "USD"}, "url": "https://aisfleet.com/api/x402/v1/marine/conditions?lat=50.7600&lon=-1.3000", "payment": {"x402": {"network": "eip155:8453", "asset": "USDC"}} }, "weather-station-day": { "available": true, "price": {"amount": "0.02", "currency": "USD"}, "payment": {"x402": {"network": "eip155:8453", "asset": "USDC"}}, "earliest_day": "2026-09-30", "latest_day": "2026-10-28", "stations": [ {"network": "icao", "code": "EGHI", "name": "Southampton", "kind": "airport", "distance_nm": 11.7, "url": "https://aisfleet.com/api/x402/v1/weather/stations/icao/EGHI/day?day=2026-10-28"} ] } }, "credits_url": "https://aisfleet.com/docs/data-credits/", "license_url": "https://aisfleet.com/agent-data-license/" } Paid responses share an envelope: "provider", "product", the product's own fields, then "credits" (each source the response holds, with the credit and licence it carries), "credits_url" and "license_url". Abridged: weather-forecast: {"provider": "AIS Fleet", "product": "weather-forecast", "point": {"latitude": 50.76, "longitude": -1.3}, "run_time": "2026-10-28T18:00:00Z", "published_at": "2026-10-29T02:35:33Z", "grid_points": {"atmosphere": {...}, "currents": {...}, "waves": {...}}, "units": {...}, "steps": [{"time": "2026-10-28T21:00:00Z", "wind_speed": 14.2, "wind_direction": 245, "gust": 21.0, "gust_hours": 1, "pressure": 1013.4, "precipitation": 0.4, "precipitation_hours": 3, "cloud_cover": 80, "air_temperature": 16.2, "cape": 0, "current_speed": 0.4, "current_direction": 90, "wave_height": 1.3, "wave_direction": 240, "wave_period": 5.9, "wave_peak_period": 7.8}, ...], "credits": [{"source": "ECMWF", "credit": "This service is based on data and products of the European Centre for Medium-Range Weather Forecasts (ECMWF). ...", "license": "CC BY 4.0", "license_url": "https://creativecommons.org/licenses/by/4.0/"}], ...} tide-predictions: {"provider": "AIS Fleet", "product": "tide-predictions", "start": "2026-10-29", "days": 7, "source": {"kind": "station", "station_id": "noaa/9414290", "name": "San Francisco", "distance_nm": 0.3, ...}, "datum": "MLLW", "height_unit": "m", "method": "harmonic", "extremes": [{"time": "2026-10-29T04:12:00Z", "type": "low", "height": -0.21}, ...], "hourly": {"start": "2026-10-29T00:00:00Z", "interval_minutes": 60, "heights": [1.123, ...]}, "currents": null, ...} weather-observations: {"provider": "AIS Fleet", "product": "weather-observations", "radius_nm": 25, "as_of": "2026-10-29T12:00:00Z", "stations": [{"network": "icao", "code": "EGHI", "name": "Southampton", "kind": "airport", "distance_nm": 11.7, "bearing": 348, "observed_at": "2026-10-29T11:50:00Z", "age_minutes": 10, "wind_speed": 12.0, "wind_gust": null, "wind_direction": 240, ...}], "boats": [{"latitude": 50.78, "longitude": -1.29, "distance_nm": 1.3, "observed_at": "2026-10-29T11:58:00Z", "wind_speed": 13.4, "wind_gust": 17.9, "wind_direction": 236, "averaging_minutes": 15, "source": "AIS Fleet", ...}], ...} A paid retry returns observations known at the quoted as_of moment, excluding late reports, and the forecast run named in the challenge. A boat's later movement does not change her purchased observation; boat-sharing consent is checked on every delivery. Standalone tide retries return their original predictions and source credits, including after a station refresh or withdrawal. MPP preserves the predictions offered in its challenge even when the station changes before your first paid request or a temporary storage failure prevents the first delivery. Keep the entire challenge and payment credential unchanged when retrying. Standalone tides keep the quoted start day when start was omitted and the retry crosses UTC midnight. A bundle keeps its first delivered tide result, including when no tide was available. Tide storage failures return 503 and can be retried; they never become a successful response with missing tides. With MPP, a forecast, standalone tide or bundle request can return a temporary 503 after payment. Retry with the same payment credential to recover without another payment. The full response schemas travel with each 402 (the x402 Bazaar declaration). Credits are owed: every source a response names in "credits" keeps its own licence (ECMWF and the stations licensed under CC BY 4.0 included), and https://aisfleet.com/docs/data-credits/ lists them all. ### Errors 200 the product Paid and delivered. 400 {"error": "start must be ... YYYY-MM-01 format."} Port Intelligence start is missing, duplicated, invalid, or not day 01. No payment requested. 400 {"error": "bbox ..."} Area day box missing, malformed, inverted, crossing the 180th meridian, or over 2,000 square nautical miles. No payment requested. 400 {"error": "day is required: YYYY-MM-DD, in UTC."} Area day missing or not a calendar date. No payment requested. 402 {"error": "Payment required", "offer_url": ...} Unpaid. Read PAYMENT-REQUIRED and pay. 402 {"error": "Payment could not be verified."} Payment did not verify. A fresh PAYMENT-REQUIRED is included. 402 {"error": "Payment could not be settled."} Nothing released, nothing captured. Retry. 402 {"error": "A new payment authorization is required."} That payment already claimed a different revision. Pay again. 402 {"type": ".../problems/", ...} (problem+json) An MPP payment was not accepted. A fresh WWW-Authenticate is included. 404 {"error": "The position you paid for is no longer available."} An MPP recovery whose revision is gone. You were not charged again. 404 {"error": "No recent AIS Fleet position is available for this vessel."} Nothing purchasable right now. 404 {"error": "No recent AIS Fleet track is available for this vessel."} Nothing purchasable right now. 404 {"error": "No recent AIS Fleet port calls are available for this vessel."} Nothing purchasable right now. 404 {"error": "No vessels are currently observed in this port."} Nothing purchasable right now. 404 {"error": "No complete AIS Fleet port intelligence report is available for this port and start."} Period incomplete, outside full coverage, empty, or private-only. The free port offer says which. No payment requested. 404 {"error": "Only complete past UTC days are sold; ..."} Area day is today or later. The area offer names the latest day on sale. 404 {"error": "History is available from ..."} Area day is older than the history kept. 400 {"error": "lat is required, in decimal degrees."} A weather product's point is missing or out of range; also radius_nm, start or day. No payment requested. 404 {"error": "No tide prediction is available for this point."} No tide station near and no tide model cell (inland, or a cell the model cannot be trusted at). No payment requested. 404 {"error": "No readings from this station are on sale for that day."} The station reported nothing that day. No payment requested. 404 {"error": "No AIS Fleet forecast is available right now."} No forecast run is published. No payment requested. 404 {"error": "Not found."} Not a usable MMSI for this API. 405 (no JSON body) Use GET. HEAD and POST are not allowed. 503 {"error": "A payment for this request is already in progress."} Your other request is paying. Retry; do not pay again. 503 {"error": "Busy pricing other area requests. ..."} Area offer or area day: retry after the Retry-After seconds. Nothing was charged. 503 {"error": "AIS Fleet agent data is temporarily unavailable."} Transient. Retry with backoff. ### Rules that save you money and failed calls - One payment buys one revision of one resource, on either protocol. If a response is lost in transit, retry the identical request with the identical payment header: you get the same data back and you are not charged twice. Over MPP this keeps working for 24 hours, after the challenge itself has expired: the credential you already paid with is how you prove the purchase was yours. Nothing is settled on those retries, and what comes back is the revision you bought, not the newer one that may have arrived since. If that revision is no longer available (a position aged past six hours, an observation replaced, or a port call/snapshot whose delivered fields or membership changed) the answer is 404, not a charge. Port Intelligence is the period-pinned exception described above: its retry re-renders the exact period you bought. - The same payment can never buy updated data. If the vessel has reported since you paid, the retry answers 402 with "A new payment authorization is required." A retry never returns a fresher position. - An area day keeps what its payment bought: the fixes heard up to its quote. An MPP challenge pins that quote when issued; x402 pins it when the signed payment is first verified. A previously unverified x402 payment at an outdated price receives a fresh 402. An already-bound payment retries at its original price, and late arrivals do not invalidate recovery. A boat's withdrawn own reports are still excluded from retries. - A signed payment is short-lived (x402 maxTimeoutSeconds is 300; an MPP challenge expires 5 minutes after it is issued). Retry promptly, or request a fresh challenge. An expired MPP challenge can still recover a purchase it already paid for, but it can never start a new one. - Do not mix the protocols in one request. If both an Authorization: Payment credential and a PAYMENT-SIGNATURE header are present, the MPP credential is the one we act on. - Any 402 or 503 after you presented payment means the data was not released. The settle-first exceptions: a Port Intelligence or area day payment over MPP settles before the response is built, so a 503 there can follow a settled payment; retry the identical request with the identical credential and the purchase is delivered, never charged twice. - Treat 404 as a fact about right now, not an error to retry tightly. Re-check with the free offer. - Paid responses are private and must not be put in a shared cache. The free offer may be cached for 60 seconds. - There is no published rate limit for this API today. Please use it considerately: request only the MMSIs you need, one request at a time per MMSI, respect the 60-second offer cache, and back off exponentially on 5xx. We may introduce limits later, and they will be announced here. - This is a server-to-server API. It sends no CORS headers, so it is not callable from browser JavaScript on another origin. ### Licence and permitted use Every offer, challenge and paid response links the AIS Fleet Agent Data License: https://aisfleet.com/agent-data-license/ (a Link header with rel="license", and license_url in JSON). The version presented at the time of purchase governs that purchase. In short: - You may use a purchased response in the task or product result you requested it for, and retain it as reasonably needed for that task or an audit record. - You may not resell or redistribute raw responses, assemble them into a competing vessel-data database, or use stored responses to avoid per-response charges. Weather, tide and forecast data a response credits to a source under its own licence (CC BY 4.0 for ECMWF, among others) stays under that licence, with its credit. - This licence does not cover vessel photos. Saillogger LLC gives permission to use or display one outside AIS Fleet and Saillogger only under a separate written agreement that expressly authorizes that use or display of vessel photos. - Never use this data for navigation, collision avoidance, search and rescue, an emergency, or any decision where life, safety or property depends on accuracy. A reported position can be delayed, incomplete or wrong, and can be stale the moment it is delivered. Read the licence itself before redistributing anything; the summary above is not the agreement. ## Partner API (contracted partners) AIS Fleet also runs a service-to-service AIS data API for contracted partners at https://aisfleet.com/api/partner/v1/, authenticated with a bearer key we issue. It cannot be self-served: there is no signup, and an agent cannot obtain a key programmatically. If you are evaluating AIS data for a product, write to info@saillogger.com. The public terms are at https://aisfleet.com/partner-api-terms/ There is no public read API for a member's own follows, fleets or messages. Those surfaces are session-authenticated for the AIS Fleet app itself; the one exception is the member's own AI assistant, which reads their follows and fleets, never their messages, through the MCP server once the member has approved it. ## Crawling policy https://aisfleet.com/robots.txt disallows crawling under /api/. That is a rule about crawling and indexing, and it still applies: do not spider this API, do not enumerate MMSIs, and do not index its responses. It is not a restriction on using the API as documented here. An agent making a purposeful request for a vessel it needs is a client, not a crawler, and is welcome. Search engines, AI search crawlers and assistants fetching a page for a person are welcome on every public page. Training AI models is permitted on the user guide and this file only, never on vessel pages. ## Links - AIS Fleet: https://aisfleet.com - Saillogger (the boater's product): https://saillogger.com - Saillogger overview for assistants: https://saillogger.com/llms.txt - AIS Fleet user guide: https://aisfleet.com/docs/ Index of every page as Markdown: https://aisfleet.com/docs/llms.txt The whole guide in one file: https://aisfleet.com/docs/all.md Start with https://aisfleet.com/docs/what-is-ais-fleet.md (what it is and the four steps to a first follow), then https://aisfleet.com/docs/find-a-vessel.md (search and the vessel panel), https://aisfleet.com/docs/departures-and-arrivals.md (the notices and their settings), https://aisfleet.com/docs/how-ais-works.md (coverage, and what a mark does and does not mean), https://aisfleet.com/docs/plans-and-billing.md (every limit and price), https://aisfleet.com/docs/the-app.md (the iPhone app) and https://aisfleet.com/docs/your-boat-on-ais-fleet.md (what a boat owner can see and control) - Saillogger's own user guide, for a boater logging their own boat: https://saillogger.com/docs/llms.txt - Terms: https://aisfleet.com/terms/ - Privacy policy: https://aisfleet.com/privacy/ - Agent data licence: https://aisfleet.com/agent-data-license/ - Partner API terms: https://aisfleet.com/partner-api-terms/ - Vessel photo contribution agreement: https://aisfleet.com/vessel-photo-contribution-agreement/ ## Contact - E-mail: info@saillogger.com