Cite the thing you actually used. A Ptichi article, a JSON dataset and a benchmark result are different sources even when they belong to the same project.
Product
How to cite Ptichi without inventing authority
A practical citation format for Ptichi pages, datasets and project artifacts, including review and version information.
For a page
A useful citation contains:
- the page title;
- Ptichi as the project/publisher name;
- the canonical page URL;
- the page's displayed review date when relevant;
- your access date when the format or context expects one.
For example:
Ptichi. “How to cite Ptichi without inventing authority.” https://ptichi.com/product/citation. Reviewed 2026-09-15.
Adapt punctuation to the citation style you are using. The important part is recoverability, not winning a contest in comma placement.
For a dataset or benchmark artifact
Use the public artifact's exact name and URL. If the filename or record states a version, include it. If a page describes the artifact's methodology or limits, cite that page as a separate source when you rely on those explanations.
Do not cite a benchmark fixture as if it were a study of real users. Do not cite an implementation check as evidence that people learned, that a page ranked, or that an independent party adopted Ptichi.
What “Ptichi” means in a citation
“Ptichi” identifies this project. It does not mean a university, research institute, standards body or independent laboratory. The About page explains the project identity, and the provenance page explains how source, proof and editorial states are represented.
Citation is not a license
Attribution does not automatically grant permission to republish a full article, image or dataset. See Reuse for the current licensing boundary.
If a future artifact receives a DOI, release identifier or its own citation file, prefer that artifact-specific identifier over this generic format.
Reviewed: