Bookbinding API
Bookbinding and print-production maths as an API, computed locally and deterministically — the spine-width and imposition numbers a book designer, printer or self-publisher needs to lay out a title. The spine endpoint computes the spine width from the page count and the paper's bulk: spine = page count ÷ pages-per-inch (the printer's paper spec, typically ~400–500 for book stock), or leaves × sheet caliper, plus the cover boards — so a 250-page book on 400-PPI stock has a 0.625-inch (15.9 mm) spine. The imposition endpoint works out the binding layout: for saddle-stitch it rounds the page count up to the next multiple of four (one folded sheet is four pages) and reports the blanks to pad and the sheets; for perfect-bound or section-sewn books it gathers the pages into signatures of 8, 16 or 32 and reports the signature count, the required page total and the blank pages. Everything is computed locally and deterministically, so it is instant and private. Ideal for self-publishing, print-on-demand, book-design, prepress and printing app developers, spine-and-cover and imposition tools, and graphic-design education. Pure local computation — no key, no third-party service, instant. Page count counts both sides; PPI is the paper spec. Live, nothing stored. 2 compute endpoints. For paper weight use a paper API and for DPI/resolution a resolution API.
api.oanor.com/bookbinding-api
