Skip to main content
Every Fanvue docs page is served as plain text, alongside both OpenAPI documents and a skill file that summarises the API’s conventions. Point any tool that reads URLs at the file that suits it: an editor’s context or rules file, a client generator, or a request tool. There’s nothing to install and no sign-in.

​
Files

​
Choosing a file

  • llms.txt suits a tool that fetches pages on demand. It is small, and each entry links to the page it summarises.
  • llms-full.txt suits a tool that takes one large context. It carries every page, so no follow-up fetch is needed.
  • openapi.json and openapi-v1.json suit client generators and API tools. Import either into a generator, Postman or Insomnia to scaffold a typed client. Use openapi-v1.json for new work, and openapi.json only for the operations that exist on the unversioned API alone, such as the App Store and account health endpoints. Moving to v1 lists the differences, and the v1 API conventions cover auth, pagination and errors.
  • skill.md suits a rules file or system context. It states the base URL, the version header, pagination shapes, rate limits and scopes. It then gives the call order for jobs such as replying to fans and publishing a post, and points to both specs for request and response shapes.

​
Per-page text

Each page header offers Copy page and View as Markdown, so a single page can be pasted or fetched as Markdown without the full file.

​
Keeping current

The files are regenerated from the same source as the rendered pages, so a fetch returns the current content. The examples send X-Fanvue-API-Version: 2025-06-26. Confirm the latest value in the changelog before you ship generated code.