What it is for
- Course materials that must meet WCAG 2.1 AA, made from the LaTeX they were written in rather than patched afterwards.
- A publishing workflow that already builds PDFs from LaTeX and needs them tagged, without anyone fixing tags by hand.
- An agent preparing documents for people who listen to them.
What we measured
In our last measured run of real course documents, 80 of the 86 that built passed veraPDF's PDF/UA-2 check as they were delivered, and 234,545 of 235,724 formulas became real mathematics with a spoken form. Each PDF carries, inside it, a short statement in plain words of what was checked and what was not.
Price
Six cents a page. With the web page, the report and an archival copy, in one request, all of it costs ten cents a page. A document that cannot be built costs nothing.
Documentation
POST https://api.intex.institute/v1/pdf
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
The PDF itself, as application/pdf, with two headers:
| Header | What it holds |
|---|---|
Intex-Pages | The pages billed. |
Intex-Cost-Cents | What this request cost, in cents. |
A project that cannot be built comes back as status 422, with the reason in a sentence and its place in your source, so you can fix it and send it again.
An example
curl https://api.intex.institute/v1/pdf \
-H "Authorization: Bearer $INTEX_KEY" \
-F project=@lecture-04.zip \
-o lecture-04.pdf
Related
- The same project as a web page that agrees with it word for word: Web page.
- Why a formula copied out of a usual LaTeX PDF falls apart: a real example, and what ours pastes as.
- How a theorem keeps the number LaTeX gave it: numbers that match the original.