Bearing capacity
API · /soil-api
Soil Bearing Capacity API
healthy
3,266 Subscribers
Geotechnical foundation maths as an API, computed locally and deterministically. The factors endpoint computes the Terzaghi/Vesic bearing-capacity factors Nc, Nq and Nγ from a soil friction angle — Nq = e^(π·tanφ)·tan²(45+φ/2), Nc = (Nq−1)·cotφ and Nγ = 2(Nq+1)·tanφ. The bearing-capacity endpoint computes the ultimate, net and allowable bearing capacity of a strip, square or circular footing from the cohesion, friction angle, soil unit weight, footing width and founding depth, qu = sc·c·Nc + γ·D·Nq + sγ·γ·B·Nγ, breaking it into its cohesion, surcharge and self-weight components and dividing by a factor of safety (default 3) for the allowable value. The settlement endpoint computes the immediate elastic settlement of a footing, s = q·B·(1−ν²)·I / E, from the applied pressure, the footing width, the soil elastic modulus and Poisson's ratio. Cohesion and pressures are in kilopascals, unit weight in kN/m³ and lengths in metres. Everything is computed locally and deterministically, so it is instant and private. Ideal for civil-engineering, geotechnical, foundation-design and construction app developers, footing-sizing and feasibility tools, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is foundation bearing capacity; for lateral earth pressure on walls use an earth-pressure API and for open-channel flow a Manning API.
api.oanor.com/soil-api
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 72 ms
- Server probes · 24h
- Subscribers
- 3,266
- active
- Total calls
- 76
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 2,000 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 2,000 bearing-capacity calls/month
- Terzaghi Nc/Nq/Nγ factors endpoint
- Strip and square footing geometry
- Deterministic, instant results
Starter
€9.00 /month
- 18,000 calls / month
- 5 requests / second
- Hard cap (429 above quota, no overage)
- 18,000 calls/month
- Vesic shape and depth correction factors
- Allowable bearing pressure with safety factor
- JSON output for spreadsheet pipelines
Pro
€24.00 /month
- 90,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- 90,000 calls/month
- Inclined and eccentric load factors
- Batch footing evaluation per request
- Groundwater-table correction handling
- Priority compute lane
Mega
€74.00 /month
- 431,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- 400,000 calls/month
- Full Terzaghi + Vesic factor suite
- High-throughput design-iteration workloads
- SLA-backed deterministic uptime
- Dedicated support channel
Built by
Related APIs
Other APIs with overlapping tags.
Composting API
Composting maths as an API, computed locally and deterministically — the three numbers that decide whether a pile heats up and breaks down or sits there cold and smelly. The cn-ratio endpoint blends a mix to its carbon-to-nitrogen ratio: pass each material by weight with its dry-weight %C and %N as parallel comma-separated lists and it returns the total carbon and nitrogen masses and the blended C:N, with an assessment against the ideal 25–35:1 — ten parts dry leaves (50 %C, 1 %N) with ten parts grass clippings (45 %C, 2.5 %N) comes out at a near-perfect 27:1. The moisture endpoint works out the water to add to reach a target moisture (the pile should be a wrung-out-sponge 50–60 %): from the current mass and moisture it holds the dry matter constant, so 100 kg at 30 % needs about 56 kg of water to reach 55 %, and it flags a too-wet pile that needs drying instead. The mix endpoint gives the brown:green weight ratio to hit a target C:N from two materials' %C and %N — leaves and grass at a target 30:1 want about 1.5 parts browns to 1 part greens. Everything is computed locally and deterministically, so it is instant and private. Ideal for gardening and composting apps, master-composter and allotment tools, regenerative-ag and soil-health sites, and waste-diversion calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. For material volume use a mulch API; for NPK application rates use a fertilizer API.
api.oanor.com/compost-api
Earth Pressure API
Lateral earth-pressure maths (Rankine theory) as an API, computed locally and deterministically for retaining-wall design. The active endpoint computes the active earth pressure that pushes a wall outward when the soil is allowed to yield: the coefficient Ka = (1−sinφ)/(1+sinφ) from the soil friction angle, the pressure at the base of the wall σ = Ka·γ·H, the total thrust per metre run ½·Ka·γ·H², plus the contributions of a surface surcharge and of soil cohesion (which reduces the pressure by 2c√Ka and forms a tension crack of depth 2c/(γ√Ka)). The passive endpoint computes the passive resistance Kp = (1+sinφ)/(1−sinφ) that the soil mobilises when a wall is pushed into it — the resisting pressure and thrust, with cohesion adding 2c√Kp. The atrest endpoint computes the at-rest pressure K0 = 1−sinφ (Jaky) for unyielding walls such as basements and braced excavations. Everything is computed locally and deterministically, so it is instant and private. Ideal for geotechnical and civil-engineering tools, retaining-wall, sheet-pile and basement-wall design, excavation-shoring and foundation apps, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is Rankine lateral earth pressure; for slope geometry use a slope API and for open-channel weir flow use a weir API.
api.oanor.com/earthpressure-api
Earthwork Volume API
Earthwork volume maths as an API, computed locally and deterministically — the cut/fill-quantity and soil-state numbers a civil engineer, estimator or grading contractor runs for a road, trench or site. The average-end-area endpoint gives the volume between two cross-sections = the mean of the two end areas × the distance between them, ÷ 27 for cubic yards — the everyday earthwork-quantity method you sum section by section down an alignment (a 100 ft²/150 ft² pair 100 ft apart is about 463 cy). The prismoidal endpoint gives the more accurate Simpson volume = length ÷ 6 × (A₁ + 4·A_mid + A₂) using the true middle-section area, preferred for payment quantities where the average-end-area over-estimate would matter. The soil-state endpoint converts between the three states earth passes through: loose = bank × (1 + swell %) (excavating loosens it, ~25 %, so you haul more cubic yards than you cut) and compacted = bank × (1 − shrinkage %) (placing and compacting shrinks it, ~10 %) — which is why a balanced cut-and-fill needs more bank cut than the compacted fill, with the load factor for truck sizing. Everything is computed locally and deterministically, so it is instant and private. Ideal for grading and site-work estimating, surveying and civil-design tools, and earthmoving calculators. Pure local computation — no key, no third-party service, instant. US units (ft², ft, cy). 3 compute endpoints. For tank/storage volumes use a tank API; for concrete mix a concrete API.
api.oanor.com/earthwork-api
Highway Vertical Curve API
Vertical (parabolic) road-curve geometry as an API, computed locally and deterministically — the K-value, profile-elevation and design-length numbers a highway engineer or surveyor lays a crest or sag curve out with. The geometry endpoint takes the incoming and outgoing grades and the length and returns the algebraic grade difference A = g2 − g1 (negative is a crest, positive a sag), the K value = length ÷ |A| (the headline number on every design chart), the high or low point offset −g1·L/A from the PVC, and — given the PVI station and elevation — the PVC and PVT coordinates and the turning-point station and elevation. The elevation endpoint evaluates the parabola at any station: elevation = PVC elevation + (g1/100)·x + (A/(200·L))·x², with the instantaneous grade g1 + (A/L)·x that sweeps smoothly from g1 to g2 — the smooth change of grade that makes the ride and sight line comfortable. The min-length endpoint gives the AASHTO minimum length for stopping sight distance: crest L = A·S² ÷ 2158 and sag (headlight) L = A·S² ÷ (400 + 3.5·S), with the controlling K, because a crest hides the road over the hump and a sag limits the headlight reach at night. Everything is computed locally and deterministically, so it is instant and private. Ideal for highway- and rail-design tools, surveying and civil-engineering utilities, and CAD/GIS profile work. Pure local computation — no key, no third-party service, instant. US units (ft, %, mph). 3 compute endpoints. For horizontal curves use a horizontal-curve API; for slope conversion a slope API.
api.oanor.com/verticalcurve-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Soil Bearing Capacity API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Soil Bearing Capacity API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Soil Bearing Capacity 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 Soil Bearing Capacity API cost?
Soil Bearing Capacity API has a free tier with 100 calls / month. Paid plans start at €9.00 / 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 Soil Bearing Capacity API GDPR-compliant?
All requests to Soil Bearing Capacity 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/soil-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/soil-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/soil-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/soil-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 inNew thread
📌 Pinned
🔒 Locked
·
·
·
-
Provider answer
🔒 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 inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.