API · /bookbinding-api

Bookbinding API

healthy 3,687 Subscribers

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
Get an API key Try in playground → Contact provider

Machine-readable spec so AI agents can integrate this API.

/api/bookbinding-api/openapi.json
/api/bookbinding-api/llms.txt

Discovery: GET /api/index.json lists every API.

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
74 ms
Server probes · 24h
Subscribers
3,687
active
Total calls
0
last 7 days
status Full status page → · 3 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 4,850 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • 4,850 calls/month
  • 2 req/sec
  • Spine width + imposition
  • No credit card
Sign in to subscribe

Starter

€5.10 /month

  • 47,500 calls / month
  • 6 requests / second
  • Hard cap (429 above quota, no overage)
  • 47,500 calls/month
  • 6 req/sec
  • PPI/caliper, saddle & signatures
  • Email support
Sign in to subscribe

Pro

€13.90 /month

  • 216,000 calls / month
  • 15 requests / second
  • Hard cap (429 above quota, no overage)
  • 216,000 calls/month
  • 15 req/sec
  • Prepress & cover pipelines
  • Priority support
Sign in to subscribe

Mega

€42.50 /month

  • 1,255,000 calls / month
  • 40 requests / second
  • Hard cap (429 above quota, no overage)
  • 1,255,000 calls/month
  • 40 req/sec
  • Platform scale
  • Dedicated SLA
Sign in to subscribe

Built by

Related APIs

Other APIs with overlapping tags.

ISBN Validator API

ISBN validation and conversion as an API, computed locally and deterministically. The validate endpoint detects whether a code is an ISBN-10 or an ISBN-13, ignores hyphens and spaces, and verifies the check digit — ISBN-10 with the mod-11 scheme whose last character may be the letter X (for 10), and ISBN-13 with the weighted 1-3-1-3 mod-10 scheme — so 0-306-40615-2 and 978-0-306-40615-7 both validate while a wrong check digit is rejected. The checkdigit endpoint computes the trailing check digit for a 9-digit ISBN-10 stem or a 12-digit ISBN-13 stem (and recomputes it for a full code). The convert endpoint converts between the two forms: an ISBN-10 becomes an ISBN-13 by prefixing 978 and recomputing the check, and a 978-prefixed ISBN-13 converts back to ISBN-10 (979-prefixed codes have no ISBN-10 equivalent). Everything is computed locally and deterministically, so it is instant and private. Ideal for publishing, library, bookstore, catalogue, e-commerce and metadata app developers, ISBN-validation and barcode tools, and inventory systems. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is ISBN-specific validation and conversion; for generic Luhn/Verhoeff check digits use a check-digit API.

api.oanor.com/isbn-api

CTAN API

The TeX and LaTeX package ecosystem — CTAN, the Comprehensive TeX Archive Network — as an API. Look up any of CTAN's ~6,900 packages for its caption and description, latest version and date, license, authors (with resolved names), aliases, topics, home and repository links, and whether it ships with MiKTeX and TeX Live; search the whole registry by name and caption; and resolve any CTAN author id to a name. Covers the TeX/LaTeX world from PGF/TikZ, Beamer and KOMA-Script to amsmath, biblatex and listings. Live from the official CTAN JSON API. Ideal for LaTeX editors and tooling, package dashboards, academic-publishing pipelines and TeX ecosystem analytics. Open data from CTAN.

api.oanor.com/ctan-api

Sailing & Hull Design API

Sailing and naval-architecture maths as an API, computed locally and deterministically — the hull-speed and design-ratio numbers a sailor, boat-shopper or yacht designer sizes a boat with. The hullspeed endpoint gives the theoretical displacement speed limit from the waterline: hull speed = 1.34 × √LWL (feet) in knots, so a 25-foot waterline tops out around 6.7 knots (7.7 mph, 12.4 km/h) — with a tunable coefficient up to about 1.5 for light, easily-driven hulls, since planing boats leave the formula behind entirely. The ratios endpoint computes the two classic performance numbers: the Sail Area/Displacement ratio, SA/D = sail area ÷ (displaced volume in ft³)^⅔ using displaced volume = displacement ÷ 64 lb/ft³ for seawater — around 16–18 is a typical cruiser and 20-plus is sporty — and the Displacement/Length ratio, DLR = (displacement in long tons) ÷ (0.01 × LWL)³, where under 200 is light and over 300 is heavy, each returned with a class label. The ballast endpoint gives the ballast ratio = ballast ÷ displacement × 100, a rough proxy for stiffness and sail-carrying power that most cruisers hit near 35–45 %. Everything is computed locally and deterministically, so it is instant and private. Ideal for sailing, boating, marine, yacht-brokerage and boat-design app developers, boat-comparison and rig-sizing tools, and naval-architecture calculators. Pure local computation — no key, no third-party service, instant. Imperial units. Live, nothing stored. 3 compute endpoints. Design-ratio estimates, not a velocity prediction program.

api.oanor.com/sailing-api

Archery & Arrow API

Archery and arrow maths as an API, computed locally and deterministically — the FOC, energy and arrow-weight numbers an archer or bowhunter tunes a setup with. The FOC endpoint finds the front-of-center balance, the share of an arrow’s weight that sits forward of the middle: FOC = ((balance point − length ÷ 2) ÷ length) × 100 measured from the throat of the nock, so a 28-inch arrow balancing at 16 inches is 7.1 % — and it bands the result, since target archers run about 7–12 % while hunters push 12–19 % for penetration and forgiveness. The energy endpoint turns arrow weight and speed into terminal performance: kinetic energy (ft-lb) = grains × fps² ÷ 450,240 and momentum (slug-fps) = grains × fps ÷ 225,218, so a 400-grain arrow at 280 fps carries about 69.7 ft-lb and 0.50 slug-fps, with a suggested game class — momentum, not KE, is the better penetration predictor for heavy arrows. The weight endpoint totals a finished arrow from its parts — shaft (grains-per-inch × length) plus point, insert, nock and fletching — and divides by draw weight for grains-per-pound, flagging the 5-GPP minimum that protects the bow. Everything is computed locally and deterministically, so it is instant and private. Ideal for archery, bowhunting, traditional-archery and outdoor-sports app developers, arrow-builder and bow-tuning tools, and pro-shop calculators. Pure local computation — no key, no third-party service, instant. Imperial archery units. Live, nothing stored. 3 compute endpoints. For sight marks or bow tuning use a different API.

api.oanor.com/archery-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for Bookbinding API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Bookbinding API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Bookbinding API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does Bookbinding API cost?
Bookbinding API has a free tier with 100 calls / month. Paid plans start at €5.10 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is Bookbinding API GDPR-compliant?
All requests to Bookbinding API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.

Pick an endpoint from the list on the left to see its details and try it.

Code snippets

Sign up to get an API key, then call any path under your slug.

curl https://api.oanor.com/bookbinding-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/bookbinding-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/bookbinding-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
    "https://api.oanor.com/bookbinding-api/SOME_PATH",
    headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())

Ratings

Sign in to rate.

No reviews yet.

Discussion

Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.

Sign in to start a thread or reply.

Sign in

New thread

/ 4000

📌 Pinned 🔒 Locked

·

· ·

/ 4000

🔒 This thread is locked — no new replies.

  • No threads yet — start the discussion.

Support

Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.

Sign in to open a support ticket.

Sign in

Open new ticket

Describe what you need help with. The provider team gets an email and replies on the ticket page.

  • No tickets yet for this API.

Subscription active — calls can start immediately.

Send your first request —

Subscription active — copy a snippet and fire off your first call.