API

API comes after the data is worth depending on.

API is a future commercial and developer surface. Qidao AI currently uses Cloudflare only for lightweight newsletter infrastructure; formal product APIs should be validated and likely owned by Fuyera.

Current public API

Qidao AI only exposes the lightweight newsletter endpoint today. The content library remains static and crawlable.

Future Qidao data APIs

Tool, workflow, ranking, and selector data can become structured APIs after content quality and demand are validated.

Fuyera product APIs

Commercial model aggregation, developer APIs, billing, and formal platform services should live under Fuyera.

The first API is not a product platform.

The current site has one operational endpoint for newsletter signups. Tool data, selector logic, and workflow content are intentionally published as static pages first, so users and search engines can validate the value before an API is promised.

Join API updates

Roadmap guardrails

  • Public content stays static-first until search and newsletter signals justify a data API.
  • Lightweight forms, waitlists, and small recommendation logic can stay on Cloudflare Workers and D1.
  • Heavy aggregation, search, batch evaluation, crawlers, and long-running jobs belong on VPS Docker.
  • Any commercial API must have documentation, rate limits, auth, billing, and operational ownership before launch.