API · /logscale-api

Log Scaling & Timber API

healthy 4,210 Subscribers

Log-scaling and timber maths as an API, computed locally and deterministically — the board-foot yield and cubic volume a logger, sawyer or forester scales a round saw log with. The boardfeet endpoint runs the three classic log rules at once from the small-end diameter inside bark and the length: Doyle = ((D − 4) ÷ 4)² × L, Scribner Decimal C ≈ (0.79·D² − 2·D − 4) × L ÷ 16, and the International ¼-inch rule by exact four-foot segments with a half-inch taper allowance, rounded to the nearest 5 board feet — so a 20-inch, 16-foot log scales 256 BF by Doyle, 272 by Scribner and 320 by International, neatly showing how Doyle under-scales small logs, International is the most accurate and Scribner sits between. The volume endpoint gives the cubic content by Smalian’s formula — the average of the two end cross-section areas times length — and Huber’s formula — the mid cross-section area times length, usually the most accurate — both in cubic feet and cords (128 ft³ = 1 cord). Everything is computed locally and deterministically, so it is instant and private. Ideal for forestry, logging, sawmill, timber-cruising and land-management app developers, log-buyer and timber-valuation tools, and woodlot calculators. Pure local computation — no key, no third-party service, instant. Imperial forestry units. Live, nothing stored. 2 compute endpoints. For sawn-board board feet use a lumber API.

api.oanor.com/logscale-api
Get an API key Try in playground → Contact provider

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

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

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

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
91 ms
Server probes · 24h
Subscribers
4,210
active
Total calls
3
last 7 days
status Full status page → · 6 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 6,800 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • 6,800 calls/month
  • 2 req/sec
  • Doyle + Scribner + International + volume
  • No credit card
Sign in to subscribe

Starter

€4.50 /month

  • 51,500 calls / month
  • 6 requests / second
  • Hard cap (429 above quota, no overage)
  • 51,500 calls/month
  • 6 req/sec
  • Smalian & Huber cubic volume, cords
  • Email support
Sign in to subscribe

Pro

€12.20 /month

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

Mega

€39.00 /month

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

Built by

Related APIs

Other APIs with overlapping tags.

Firewood Calculator API

Firewood maths as an API, computed locally and deterministically. The volume endpoint turns a wood-stack's length, height and depth (in feet or metres) into its volume in cubic feet and cubic metres, full cords, face cords and steres — a full cord being 128 cubic feet (a 4×4×8 ft stack) and a face cord being an 8×4 ft stack by the piece (log) length. The convert endpoint converts a quantity between cords, face cords, steres, cubic metres and cubic feet, using the piece length for the face-cord relationship. The heat endpoint estimates the heating value of a number of cords by wood species — returning the millions of BTU and the equivalent gallons of heating oil, therms of natural gas and kilowatt-hours — from a built-in table of typical seasoned-wood values (oak, hickory, maple, ash, birch, pine and more) or a custom figure. Everything is computed locally and deterministically, so it is instant and private. Heat values are typical seasoned figures (around 20% moisture) and vary with species, dryness and stove efficiency. Ideal for firewood sellers and delivery tools, heating and homestead apps, and forestry and woodlot calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is firewood volume and energy; for general volume or unit conversion use a unit-conversion API.

api.oanor.com/firewood-api

Rotational Grazing API

Rotational-grazing maths as an API, computed locally and deterministically — the animal-unit, grazing-day and acreage numbers a rancher or homesteader moves a herd by. It all hangs on the animal unit: a 1000-pound cow eating about 26 pounds of dry matter a day. The animalunits endpoint converts a mixed herd to that common basis — a cow is 1.0 AU, a cow-calf pair 1.3, a horse 1.25, a sheep 0.2, a goat 0.17 — so ten cows and fifty sheep are 20 AU demanding 520 pounds of forage a day; pass a weight instead and it scales by weight ÷ 1000. The days endpoint works out how long a paddock lasts: grazing days = (acres × forage per acre × utilization) ÷ (animal units × 26), where the classic “take half, leave half” puts utilization near 50 %, so five acres yielding 3,000 lb at 50 % feeds 10 AU for about 29 days. The acres endpoint sizes the paddock the other way — acres = (AU × 26 × days) ÷ (forage × utilization) — so 20 AU for a 30-day move needs about 10.4 acres. Everything is computed locally and deterministically, so it is instant and private. Ideal for ranching, regenerative-agriculture, homesteading and farm-management app developers, paddock-planner and stocking-rate tools, and grazing-chart software. Pure local computation — no key, no third-party service, instant. US units; forage yield varies with season — measure it. Live, nothing stored. 3 compute endpoints.

api.oanor.com/grazing-api

Egg Incubation API

Egg-incubation maths as an API, computed locally and deterministically — the hatch timeline, conditions and brooder numbers a hatchery or backyard chicken-keeper raises a clutch by. The hatch endpoint turns the set day (day 0) into the schedule by species: it knows the incubation period — chicken 21 days, duck 28, quail 17, goose 30, turkey 28, Muscovy 35 and more — and gives the lockdown day, about three days before hatch, when you stop turning the eggs, raise the humidity and leave the lid shut; pass a custom incubation_days for anything else. The conditions endpoint gives the targets: a forced-air incubator at 99.5 °F (still-air a degree or two higher at the top of the eggs), with humidity around 45–55 % through incubation and 65–75 % at lockdown so the membrane stays soft. The brooder endpoint schedules the chicks after they hatch — 95 °F under the lamp in week one, dropping 5 °F a week until they reach room temperature around 70 °F and are feathered enough to leave it. Everything is computed locally and deterministically, so it is instant and private. Ideal for poultry, hatchery, homesteading and farm app developers, incubation-timer and brooder tools, and 4-H / education software. Pure local computation — no key, no third-party service, instant. Guidance — candle the eggs and watch the chicks. Live, nothing stored. 3 compute endpoints.

api.oanor.com/incubation-api

Vegetable Fermentation API

Vegetable lacto-fermentation maths as an API, computed locally and deterministically — the salt numbers a fermenter weighs sauerkraut, kimchi and pickles by. (Vegetables, not meat — for cure and nitrite that is a separate calculation.) Salt is the whole game: too little and the wrong microbes win, too much and the ferment stalls. The salt endpoint does the dry-salt method for shredded veg, salt = vegetable weight × percent, with about 2 % being the classic sauerkraut and kimchi target — so a kilo of cabbage takes 20 grams — and it bands the result from low-and-fast to a near salt-cure. The brine endpoint sizes a submerged ferment, salt = water weight × percent where the percent is of the water as recipes state it (1 ml water ≈ 1 g), so a litre at 5 % needs 50 grams for a standard sour pickle, 3.5 % for a milder one; it also reports the salinity as a percent of the total solution. The salinity endpoint converts the two ways the same brine is expressed — percent of water versus percent of total — so a 5 %-of-water brine reads about 4.76 % on a refractometer. Everything is computed locally and deterministically, so it is instant and private. Ideal for fermentation, homesteading, recipe and food app developers, ferment-calculator and batch tools, and culinary software. Pure local computation — no key, no third-party service, instant. Grams and ml. Live, nothing stored. 3 compute endpoints.

api.oanor.com/fermentation-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for Log Scaling & Timber API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Log Scaling & Timber API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Log Scaling & Timber 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 Log Scaling & Timber API cost?
Log Scaling & Timber API has a free tier with 100 calls / month. Paid plans start at €4.50 / 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 Log Scaling & Timber API GDPR-compliant?
All requests to Log Scaling & Timber 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/logscale-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/logscale-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/logscale-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/logscale-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.