Skip to content
floatjet

For developers and agents

FloatJet Content API

Version 1.0.0 - Last updated: September 22, 2026

The FloatJet Content API gives you the whole FloatJet catalog of reviews, comparisons and guides as plain JSON. It is read-only, free to use and needs no API key. The files are regenerated on every deploy, so they always match the site.

Quick start

Fetch every article, then any single article by its slug:

curl https://floatjet.com/api/articles.json
curl https://floatjet.com/api/articles/best-vpn-digital-nomads.json

The full machine-readable description is the OpenAPI 3.1 spec at floatjet.com/openapi.json. Every operation has a unique operationId, a description, typed parameters and response schemas, so you can load it straight into an LLM function-calling tool or an OpenAPI client.

Authentication and limits

  • No authentication. There are no API keys or accounts.
  • GET only. Responses are static files served from a CDN with Access-Control-Allow-Origin: *.
  • There is no hard rate limit. Please cache responses and avoid polling more than once an hour; content changes a few times a week at most.
  • Base URL: https://floatjet.com

Endpoints

  • GET /api/articles.json (listArticles)
    Every article with section, category, dates, reading time and canonical URL, newest update first.
  • GET /api/articles/{slug}.json (getArticle)
    One article by slug. Slugs come from listArticles.
  • GET /api/sections.json (listSections)
    The four sections (tools, gear, guides, blog) with their categories and article counts.
  • GET /api/index.json (getApiIndex)
    API name, version and links to every endpoint. Also served at /api/.
  • GET /index.md (getHomepageMarkdown)
    The homepage as Markdown, including every article grouped by section.
  • GET /llms.txt (getLlmsTxt)
    The llms.txt index of the site.

Try them: all articles, sections, one article.

Example response

GET /api/articles/best-vpn-digital-nomads.json returns:

{
  "article": {
    "slug": "best-vpn-digital-nomads",
    "section": "tools",
    "category": "vpn",
    "title": "Best VPNs for Digital Nomads & Remote Workers (2026)",
    "description": "I tested 12 VPNs across 15 countries to find the best for digital nomads. NordVPN, ExpressVPN, Surfshark compared with real speed tests and honest takes.",
    "url": "https://floatjet.com/tools/best-vpn-digital-nomads/",
    "published": "2025-09-24",
    "updated": "2026-09-24",
    "readingTimeMinutes": 15,
    "image": "https://floatjet.com/images/unsplash/photo-1526374965328-7f61d4dc18c5-1200w.webp",
    "imageAlt": "Digital security concept with encrypted data visualization",
    "featured": true,
    "apiUrl": "https://floatjet.com/api/articles/best-vpn-digital-nomads.json"
  }
}

Errors

Any unknown path under /api/ returns HTTP 404 with a JSON body instead of an HTML page. Every error has a stable code, a human-readable message and a hint telling you how to fix the request:

{
  "error": {
    "status": 404,
    "code": "not_found",
    "message": "No API resource exists at this path.",
    "hint": "List every article at https://floatjet.com/api/articles.json, then request /api/articles/{slug}.json with a slug from that list. The full API surface is described at https://floatjet.com/openapi.json.",
    "documentation": "https://floatjet.com/developers/#errors"
  }
}
  • not_found (404): the path or slug does not exist. Check the slug against /api/articles.json.

Markdown for agents

The FloatJet homepage supports Markdown content negotiation. Send Accept: text/markdown and you get Markdown with Content-Type: text/markdown; browsers keep getting HTML. The same Markdown is always available at /index.md.

curl -H "Accept: text/markdown" https://floatjet.com/

For a curated map of the site, read /llms.txt.

Using FloatJet content

You are welcome to use the API to find, summarize and link to FloatJet articles. Please link back to the article's canonical url when you quote or cite it. Article text itself stays under our terms of service.

Questions and changes

Found a bug or need a field we do not expose yet? Email [email protected] or use the contact page. Breaking changes will bump the major version in the OpenAPI spec.