What comes back
- The tagged PDF, as on its own page, with the report's verdict carried inside it in plain words.
- The web page, from the same reading, so the two agree word for word and number for number, as on its own page.
- The report, as JSON and as plain sentences, as on its own page.
- The archival copy: the same PDF, carrying the project it was made from and the record of what was checked, so that years from now it can be rebuilt from nothing but itself and checked again.
Price
Ten cents a page, for all four. A document that cannot be built costs nothing. Count tells you the pages, and so the price, before you send it.
Documentation
POST https://api.intex.institute/v1/all
The same request as every project service: your key in the Authorization header, and the project as a form upload in project, with main when the archive holds more than one main file. The details are in the docs.
The response
A .zip, as application/zip, with the Intex-Pages, Intex-Cost-Cents and Intex-Credit-Cents headers. For a project whose main file is lecture-04.tex, it holds:
lecture-04.pdf the tagged PDF
lecture-04/index.html the web page, with its figures beside it
lecture-04.report.json the report, for software
lecture-04.report.txt the report, in plain sentences
lecture-04.archive.pdf the archival copy
An example
curl https://api.intex.institute/v1/all \
-H "Authorization: Bearer $INTEX_KEY" \
-F project=@lecture-04.zip \
-o lecture-04-all.zip
Related
- How a PDF that carries its source rebuilds from itself: rebuilt from the PDF alone, and a document that proves itself.
- Every service on its own, with its own price: the Index.