All AI guides
Inside Hokai8 min read

We Opened Every Source Link Hokai Cites

A source list means little unless it can be tested. Hokai publishes every guide's sources through its API: 2,900 citations to 1,032 domains on 17 November 2026, each with an address and a page title, 2,838 with a publisher and 2,695 with the date the page was read.

The short version

Hokai's guides cite 2,900 sources. We requested each of the 2,233 distinct addresses on 17 November 2026: 2,162 returned a page, 57 more refused our request and seven were gone. The public API lets anyone repeat the test. It proves a page exists, not that it supports the sentence beside it.

Not sure which one fits you? Describe your situation and Smart Match names three tools.Find my AI tools

In this guide6 sections

On 17 November 2026 we requested every source address cited across Hokai's 270 guides, 2,233 distinct ones, and counted what answered. Anyone can repeat the test from the public API in a few minutes without a key.

Disclosure: Hokai wrote this about Hokai.

How to run the same test

The guides list does not carry sources, and it stops at 100 guides: /api/guides?limit=500 returns 100 and leaves each guide's sources array out. The route that works has two steps. Page through /api/guides?limit=100&offset=0 (then 100, then 200) for the 270 slugs, and read each guide's own record at /api/guides/<slug>, where guide.sources holds the list. The API allows 120 requests a minute and answers 429 with a Retry-After header past that, so the script below waits 650 ms between guides.

const wait = (ms) => new Promise((r) => setTimeout(r, ms));
const get = async (u) => { for (;;) { const r = await fetch(u); if (r.status !== 429) return r.json(); await wait(11000); } };
const slugs = [];
for (let o = 0, g; (g = (await get(`https://hokai.io/api/guides?limit=100&offset=${o}`)).guides).length; o += 100) slugs.push(...g.map((x) => x.slug));
const urls = new Set();
for (const s of slugs) { for (const x of (await get(`https://hokai.io/api/guides/${s}`)).guide.sources) urls.add(x.url); await wait(650); }
console.log(slugs.length, "guides,", urls.size, "distinct addresses");

On 17 November 2026 that printed 270 guides and 2,233 distinct addresses, drawn from 2,900 citations. Guides are revised as sources change: the same script run again later that day printed 2,236 addresses, so run it again later and compare. If the count has slid and nothing on the site says so, that tells you something no editorial promise can.

A DOI check does this for one paper: Perrla's first test is to paste the DOI after doi.org and see whether a page opens. We ran the same question over a whole published list.

We requested each address once, following redirects, with a 20 second limit and an ordinary desktop browser agent, at most two requests at a time to any one host. Addresses that failed were retried with a Firefox agent and then a named one. The 15 that still gave no usable answer were tried once more with curl.

What came back

In our 17 November 2026 run, 2,136 addresses answered on the first sweep. The retries brought that to 2,162. The 71 that never did:

AnswerAddressesWhat it means
40357The server refused the request
404 or 4107The page is gone
4293The server asked us to slow down
5042A gateway timeout, both on budy.ai
No connection2No server answered

Key figure of 2,162 of 2,233 source addresses answering, beside the 71 that did not, sorted by the answer they gave Every distinct source address the guides cite, opened one by one on 17 November 2026. Source: the hokai.io guides API.

A 403 says the server refused the request. It does not say the page is missing, so the 57 are the largest group and the least informative. The client matters too: eight addresses on tabnine.com, lexisnexis.com, tricentis.com, courtlistener.com and ltx.studio defeated our script and answered curl with a 200.

Six of the seven gone pages, with the guide that cites each:

The two with no connection are aibridgeforge.com, which failed its TLS handshake and is cited in the sales assistant roundup, and videoflux.video, which no longer resolves and is cited in the image and video guide.

What each citation carries

Every citation has an address and a page title: 2,900 of 2,900. 2,838 name a publisher and 2,695 carry the date the page was read, 2,298 of those in October or November 2026. A guide cites at least 4 sources, the median is 10, and the longest list, 30 sources, is on the AI game makers guide. The 2,900 citations reach 1,032 domains, and 2,804 of them point away from hokai.io.

Four boxes for what a citation carries, address, page title, publisher and date read, with how many of the 2,900 citations have each, above 1,032 domains and 2,804 citations that point away from hokai.io The four fields a guide citation can carry, counted over all 2,900 citations on 17 November 2026. Source: each guide's record in the API.

The guide page itself draws less than the API holds. Open any guide, such as the verification piece in this series, and its foot shows an "Official-source trail" with each source's title and publisher. The date the page was read is in the guide's record at /api/guides/<slug>.

Source links are one of several outbound links on the site. Google's guidance says sponsored marks advertisements and paid placements and that nofollow is for links where you would rather Google not associate your site with the page or crawl it from yours. Reading the served HTML on 17 November 2026 gave this:

LinkCarriesWhere to see it
A source in a guide's trailnofollowThe foot of this page
A paid listing in a guidesponsored, labelled in the textBest AI meeting assistants
The listed product's own site and docsNo nofollowDevin
Anyone else on a record pagenofollowFireflies
Hokai's affiliate linksponsored, with a line under the buttonFireflies

The paid listing is labelled with the sentence "HappyScribe is a sponsored listing in this guide", and HappyScribe has its own page. The affiliate line on the Fireflies page reads "Affiliate link: Hokai may earn a commission if you sign up. It does not change our rating."

Listing on Hokai takes a flat submission fee, according to the site's llms.txt read the same day, and a listed product's own links are the followed ones. A second guide, the music video generators roundup, has an older in-text paid link marked sponsored as well. To check any row, view the page source and search for rel=.

The strongest counter-argument

A link that answers proves a page exists. It does not prove an editor read it, or that it says what the sentence beside it says.

Our own run shows the gap. Of the first 2,225 addresses opened, 54 ended on a different host than the one cited: lmarena.ai/how-it-works now ends on arena.ai and surferseo.com/pricing on surfer.ai. Three returned a page that was a home page, not the one cited: the pricing page of alice.tech in the quiz generators guide, replit.com/agent in how to build apps without being a developer and tryskilly.app/people in Murf AI vs Skilly. A 200 on those three would have passed a naive count.

Editage's checklist puts that reading last: its step 5 is to read the original source and confirm it supports the claim it is attached to, which no script does. So this is a floor. It shows that an address answers, and leaves the harder question to the reader: whether the reading was right.

Pew Research found that 38% of webpages that existed in 2013 were gone by October 2023, and that 54% of Wikipedia pages carry at least one dead link in their references. Most of Hokai's citations carry a read date in October or November 2026 (2,298 of the 2,695 dated ones, counted from each guide's record), so the gone pages here are not a like-for-like comparison with a decade of decay, and this test does not claim to be one.

Sponsor spot open

Who this test isn't for

It tells you the address works. If you need to know that a number on a Hokai page matches the vendor's page, the listing check in this series compares one listing line by line, and the pricing checklist gives five steps for any page.

If you want to know whether a guide's pick is right for your constraints, a link test says nothing about that. Smart Match walks the directory against your budget and use and returns a shortlist with reasons, and the guides index lists every guide the test covered. The company page carries what Hokai publishes about itself.

One more limit: eight addresses on five sites, Tabnine among them, answered one client and not another, so a single run from one machine can mislabel a page. For any figure you will spend money on, open the source and read the sentence beside it. This test says the link works, and only you can say whether the page supports the claim.

Frequently asked questions

Does Hokai publish the sources behind its guides?

Yes. Every guide lists at least 4 sources at its foot under "Official-source trail", and the same list is in the guide's record at /api/guides/<slug>, with the date each page was read where one is stored. On 17 November 2026 the 270 guides held 2,900 citations to 1,032 domains.

Why do some of Hokai's source links return 403 or 429?

A 403 means the server refused the request, often one that came from a script, and a 429 means it asked the client to slow down. Neither says the page is missing. On 17 November 2026 eight addresses that failed our script answered curl with a 200, so a single run from one machine can mislabel a page.

How can I check Hokai's source links myself without an account?

Read /api/guides?limit=100&offset=0 (then 100 and 200) for the guide slugs, read /api/guides/<slug> for each guide's sources array, then request every distinct address. No key or login is needed. The API allows 120 requests a minute and answers 429 beyond that.

Are the links on Hokai guides followed by search engines?

Sources in a guide's trail carry nofollow. A paid listing in a guide carries sponsored and is labelled as a sponsored listing. On a record page, links to the listed product's own site and docs carry no nofollow and links to anyone else do. This was read from the served pages on 17 November 2026; view source and search for rel=.

Does a source link that opens prove the claim beside it is right?

No. It proves the page exists. Of the first 2,225 addresses opened, 54 ended on a different host than the one cited and three returned a home page instead of the page cited. Whether the page says what the sentence claims is a question of reading, which this test cannot answer.

Covered in this guide

  • Hokai: Singapore-run directory of AI tools, models, agents, skills and services, with a free Smart Match engine that names three picks for the job you describe.
  • CiteLens: CiteLens tracked brand citations across ChatGPT, Perplexity, Claude and Gemini; its self-serve site closed in November 2026 and it now runs only inside Solustiq's GEO agency service.
  • Devin: Devin is Cognition's autonomous AI software engineer that plans, codes, tests, and ships pull requests, with a Free plan and several paid tiers.
  • Fireflies: AI Notetaker for Meeting Transcription, Summarization & Conversation Intelligence
  • HappyScribe: AI notetaker and transcription platform that records Zoom, Meet and Teams calls and turns audio or video into text in 150+ languages.
  • Tabnine: Enterprise AI coding assistant with privacy-first architecture, agentic workflows, and flexible deployment

Sources

Still deciding?

This guide covers a handful of options. Smart Match checks every listing in the directory against how you actually work and what you can spend, then hands you the shortlist and the reason behind each pick.

Find your tools

Keep reading

Find your toolsAll AI guides