API · /magnetic-api

Magnetic Field & Force API

healthy 3,152 Subscribers

Magnetic fields and forces as an API, computed locally and deterministically. The wire endpoint computes the magnetic field around a long straight current-carrying wire, B = μ0·I/(2π·r) — the field at a distance r from a wire carrying a current I — and solves for whichever of the current, the distance or the field you leave out, reporting the field in tesla, millitesla, microtesla and gauss. The solenoid endpoint gives the uniform field inside a long solenoid, B = μ0·n·I (n turns per metre, given directly or as a total number of turns over a length), or the field at the centre of a circular loop, B = μ0·N·I/(2R). The force endpoint computes the magnetic force on a moving charge, F = q·v·B·sin(θ) (the Lorentz force), or on a current-carrying wire in a field, F = B·I·L·sin(θ), with the force per metre. The vacuum permeability μ0 = 4π×10⁻⁷ is built in, with an optional relative permeability for a magnetic core. Everything is computed locally and deterministically, so it is instant and private. Ideal for electromagnetism-education tools, electromagnet, motor and inductor design, magnetic-sensor and physics-simulation apps. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is magnetostatics; for Coulomb electrostatics use a Coulomb API and for Ohm's-law circuits use an Ohm's-law API.

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

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

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

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

API health

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

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 2,000 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • Straight-wire B-field at a given distance
  • Single current/distance per call
  • Community support
Sign in to subscribe

Starter

€9.00 /month

  • 40,000 calls / month
  • 5 requests / second
  • Hard cap (429 above quota, no overage)
  • Solenoid & coil field (Ampere's law)
  • Lorentz force on moving charges
  • SI + Gauss/Oersted unit outputs
  • Email support
Sign in to subscribe

Pro

€24.00 /month

  • 250,000 calls / month
  • 15 requests / second
  • Hard cap (429 above quota, no overage)
  • Batch field/force computation
  • Force-on-current-carrying-conductor solver
  • Flux density & magnetic energy density
  • Higher concurrency for design sweeps
Sign in to subscribe

Mega

€75.00 /month

  • 1,509,000 calls / month
  • 40 requests / second
  • Hard cap (429 above quota, no overage)
  • High-volume parametric coil-design sweeps
  • Full EM suite: field, Lorentz, conductor force, flux
  • Priority low-latency compute
  • Priority engineering support
Sign in to subscribe

Built by

Related APIs

Other APIs with overlapping tags.

Inductance API

Inductor-design electromagnetics as an API, computed locally and deterministically. The solenoid endpoint computes the inductance of a straight coil with the long-solenoid formula L = μ₀·μr·N²·A/l, from the number of turns, the coil length, the cross-sectional area (or diameter) and the relative permeability of the core — a ferromagnetic core multiplies the inductance. The toroid endpoint computes the inductance of a doughnut-shaped coil of rectangular cross-section, L = μ₀·μr·N²·h·ln(b/a)/(2π), from the turns, the axial height and the inner and outer radii; the toroidal shape confines the magnetic flux so there is little stray field. The energy endpoint computes the magnetic energy stored in an inductor, E = ½·L·I², and the flux linkage Φ = L·I, from the inductance and current — the energy released when the current is interrupted causes the inductive kick. Lengths are in metres, area in square metres, inductance in henries (millihenries and microhenries also returned) and current in amps, with μ₀ = 4π×10⁻⁷ H/m. Everything is computed locally and deterministically, so it is instant and private. Ideal for electronics, RF, power-supply, filter and motor-design app developers, coil-winding and inductor-sizing tools, and electromagnetics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is inductance from geometry; for the resonant frequency and reactance use a resonance API and for full AC impedance an impedance API.

api.oanor.com/inductance-api

Center of Mass API

Centre-of-mass and barycentre mechanics as an API, computed locally and deterministically. The point-masses endpoint computes the centre of mass of a system of point masses in one, two or three dimensions, applying x_com = Σ(m_i·x_i)/Σm_i to each axis from a list of masses and their x (and optional y and z) coordinates — masses of 1, 2 and 3 at positions 0, 1 and 2 give a centre of mass at 1.333, and four equal masses at the corners of a square sit at its centre. The two-body endpoint computes the barycentre of two masses separated by a distance, r1 = d·m2/(m1+m2) from the first body, which always lies closer to the heavier one — for the Earth-Moon system the barycentre is about 4 670 km from Earth’s centre, still inside the planet. Lists may be passed as comma-separated values (masses=1,2,3&x=0,1,2) or as JSON arrays in a POST body, and units are consistent and unit-agnostic. Everything is computed locally and deterministically, so it is instant and private. Ideal for physics, engineering-statics, astronomy, robotics, game-physics and mechanics-education app developers, balance-point and barycentre tools, and simulation software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 2 endpoints. This is the centre of mass; for the rotational moment of inertia use a moment-of-inertia API.

api.oanor.com/centerofmass-api

Vehicle Braking API

Vehicle-braking physics as an API, computed locally and deterministically. The stopping-distance endpoint computes the total distance to stop a vehicle as the sum of the reaction distance the vehicle travels during the driver's reaction time, v·t, and the braking distance v²/(2·μ·g) — which grows with the square of speed, so doubling the speed quadruples the braking distance — from the speed, the tyre-road friction coefficient, the reaction time and the road grade, along with the deceleration and the time to stop. The braking-force endpoint computes the braking force F = m·a and the deceleration of a vehicle, either from a stop-in-a-given-distance (a = v²/2d) or from the friction coefficient (a = μ·g), with the kinetic energy that must be dissipated as heat. The skid-speed endpoint reconstructs the speed at the start of a skid from the skid-mark length, v = √(2·μ·g·d), a lower-bound estimate used in accident reconstruction. Speed is in km/h by default (also m/s or mph), mass in kg and distances in m; dry asphalt has μ ≈ 0.7, wet ≈ 0.4 and ice ≈ 0.1. Everything is computed locally and deterministically, so it is instant and private. Ideal for automotive, driving-safety, fleet, telematics and accident-reconstruction app developers, stopping-distance and forensic tools, and physics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is vehicle braking; for general kinematics use a kinematics API and for an object on a slope an inclined-plane API.

api.oanor.com/brake-api

Circular Motion API

Uniform circular-motion physics as an API, computed locally and deterministically. The centripetal-force endpoint computes the centripetal acceleration a = v²/r = ω²·r — always pointing toward the centre — and the centripetal force F = m·a that holds a body on its circular path, from the mass, the radius and either the linear or the angular velocity, and reports the equivalent g-force. The angular endpoint converts between every way of describing rotation — angular velocity (rad/s), revolutions per minute, frequency, period and, given a radius, the linear (tangential) velocity — using ω = 2π·f = 2π/T = v/r. The centrifuge endpoint computes the relative centrifugal force (RCF, in g) of a centrifuge rotor from its speed in rpm and radius, RCF = ω²·r / g, or inverts it to give the rpm needed to reach a target RCF. Masses are in kg, radii in m (mm for the centrifuge), velocities in m/s, angular velocities in rad/s and forces in N. Everything is computed locally and deterministically, so it is instant and private. Ideal for physics-education, mechanical, automotive, lab-centrifuge and amusement-ride app developers, rotational-motion and g-force tools, and STEM teaching. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is uniform circular motion; for gravitational orbits use a gravitation API, for a vehicle on a banked curve a banked-curve API and for pendulum oscillation a pendulum API.

api.oanor.com/centripetal-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

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