API · /arch-api

Arch Geometry API

healthy 4,123 Subscribers

Circular-segment arch geometry as an API, computed locally and deterministically — the radius, arc-length and set-out numbers a mason, joiner, stonemason or CAD user lays a segmental arch out with. A segmental arch is an arc of a circle struck through the two springings and the crown: the from-span-rise endpoint takes the span and the rise (the height of the crown above the springing line) and returns the radius = (span²/4 + rise²) ÷ (2·rise), the central angle it subtends, the arc length along the curve, and the segment area of the void below it — flatter arches with a small rise have surprisingly huge radii. The from-radius-angle endpoint inverts it, returning the chord (span), the rise (sagitta), the arc length and the area from a known radius and central angle, the way a curve struck with a trammel or a router on a pivot is described. The setout-ordinates endpoint gives the practical numbers to mark a template: the rise of the arc above a straight base line at equally spaced stations across the span (y = √(R² − x²) − (R − rise)), so you can plot the heights, connect them and cut a plywood former or bend a batten without a giant compass — the ends come out zero at the springings and the middle equals the rise at the crown. Everything is computed locally and deterministically, so it is instant and private. Ideal for masonry and joinery layout tools, stair and window-head design, and CAD and woodworking calculators. Pure local computation — no key, no third-party service, instant. Segmental (up to a semicircle) arcs. 3 compute endpoints. For road curves use a horizontal- or vertical-curve API; for plain shape areas a geometry API.

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

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

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

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

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
102 ms
Server probes · 24h
Subscribers
4,123
active
Total calls
4
last 7 days
status Full status page → · 8 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 7,100 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • 7,100 calls/month
  • 2 req/sec
  • Span-rise, radius-angle, set-out
  • No credit card
Sign in to subscribe

Starter

€7.20 /month

  • 64,000 calls / month
  • 6 requests / second
  • Hard cap (429 above quota, no overage)
  • 64,000 calls/month
  • 6 req/sec
  • Template set-out ordinates
  • Email support
Sign in to subscribe

Pro

€25.20 /month

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

Mega

€78.00 /month

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

Built by

Related APIs

Other APIs with overlapping tags.

Masonry Estimating API

Masonry estimating maths as an API, computed locally and deterministically — the brick, block and mortar counts a bricklayer, builder or estimator works to. The brick endpoint computes how many bricks a wall needs from its area (or length × height in feet): bricks per square foot = 144 / ((brick length + joint) × (brick height + joint)), so a standard modular brick with a 3/8-inch mortar joint works out to the well-known 6.86 bricks per square foot — a 100 ft² wall is 686 bricks, plus a waste allowance and the mortar bags (about 7 per 1000 bricks). The block endpoint does the same for concrete masonry units: a standard 16×8-inch CMU with a 3/8-inch joint is 1.125 blocks per square foot, with roughly 2.5 mortar bags per 100 blocks. Both endpoints take custom unit face dimensions and joint thickness, add a configurable waste percentage and round up to whole units. Everything is computed locally and deterministically, so it is instant and private. Ideal for construction, masonry-contractor, building-supply and home-improvement app developers, takeoff and material-estimating tools, and trade calculators. Pure local computation — no key, no third-party service, instant. Imperial units (inches and square feet). Live, nothing stored. 2 compute endpoints. This is brick/block and mortar estimating; for poured-concrete volume use a concrete API and for drywall use a drywall API.

api.oanor.com/masonry-api

Geometric Solids API

Advanced 3D-solid geometry as an API, computed locally and deterministically — the shapes a basic geometry calculator leaves out. The cone-frustum endpoint gives the volume V = (π·h/3)·(R² + R·r + r²), the slant height √(h² + (R−r)²) and the lateral and total surface area of a truncated cone, the shape of buckets, lampshades and hoppers. The torus endpoint gives a doughnut’s volume 2π²·R·r² and surface area 4π²·R·r from its centre-to-tube and tube radii. The ellipsoid endpoint gives the exact volume (4/3)π·a·b·c and a Knud-Thomsen surface-area approximation accurate to better than 1.1 %. The platonic endpoint returns the volume and surface area of any of the five Platonic solids — tetrahedron, cube, octahedron, dodecahedron and icosahedron — from the edge length, using the exact golden-ratio coefficients (a unit icosahedron has volume 2.1817 and surface area 8.6603). Use a consistent length unit and get area and volume out. Everything is computed locally and deterministically, so it is instant and private. Ideal for engineering, CAD, 3D-modelling, architecture, manufacturing and maths-education app developers, volume-and-area and packaging tools, and simulation software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. These are the advanced solids; for sphere, cube, cylinder, cone and 2D shapes use a general geometry API.

api.oanor.com/solids-api

Bézier Curve API

Bézier-curve geometry maths as an API, computed locally and deterministically. The point endpoint evaluates a quadratic (three control points) or cubic (four) Bézier curve at a parameter t between 0 and 1 using de Casteljau's algorithm, returning the point on the curve and the tangent there — its direction vector, angle and speed (the derivative B'(t)). The length endpoint computes the arc length of the curve by fine polyline sampling, together with the straight-line chord length and the axis-aligned bounding box (min and max x and y, width and height). The split endpoint splits the curve at a parameter into two sub-curves and returns the control points of each — the standard de Casteljau subdivision used for trimming and adaptive rendering. Control points are passed as plain x/y coordinates. Everything is computed locally and deterministically, so it is instant and private. Ideal for graphics, CAD, font, animation, game-engine and vector-design app developers, path and curve tools, and computational-geometry education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is Bézier-curve geometry; for animation easing and timing functions use an easing API.

api.oanor.com/bezier-api

Triangle Solver API

Triangle-solving maths as an API, computed locally and deterministically. The solve endpoint solves any triangle from three values — three sides (SSS), two sides and the included angle (SAS), two angles and a side (ASA/AAS), or the ambiguous two-sides-and-a-non-included-angle case (SSA) — using the law of cosines and the law of sines, and returns all three sides and angles, the perimeter, the Heron area and whether the triangle is acute, right or obtuse and equilateral, isosceles or scalene; for an ambiguous SSA input it also returns the second valid triangle. The right endpoint is a dedicated right-triangle solver from any two of the two legs, the hypotenuse and an acute angle, applying Pythagoras and basic trigonometry. The points endpoint builds a triangle from three cartesian vertices, giving the side lengths, the interior angles, the shoelace area and the centroid. Angles are in degrees. Everything is computed locally and deterministically, so it is instant and private. Ideal for education, CAD, surveying, game-development and engineering app developers, geometry and trigonometry tools, and STEM teaching. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This solves triangles; for areas and volumes of general shapes use a geometry API and for polygon point-set operations a polygon API.

api.oanor.com/triangle-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

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