Total link loss
API · /opticalbudget-api
Fiber Optic Link Budget API
Fiber-optic link-budget engineering maths as an API, computed locally and deterministically — the power-budget, loss and reach numbers a network or fibre engineer designs an optical link with. The power-budget endpoint gives the optical power budget = transmit power − receiver sensitivity (in dBm), the total loss the link can tolerate: a 0 dBm transmitter into a −23 dBm receiver gives a 23 dB budget, with the powers also shown in milliwatts. The loss endpoint adds up the real link loss from the fibre attenuation × length plus the connector and splice losses — single-mode fibre runs about 0.35 dB/km at 1310 nm and 0.20 dB/km at 1550 nm, each mated connector ~0.5 dB and each fusion splice ~0.1 dB — so 10 km of fibre with two connectors is 4.5 dB. The reach endpoint gives the maximum distance = (power budget − fixed losses − system margin) ÷ the fibre attenuation, reserving a margin (typically 3 dB) for ageing, bends and future repair splices so the link still works years on. Everything is computed locally and deterministically, so it is instant and private. Ideal for FTTx and data-centre link planning, network-engineering and OSP tools, fibre-survey and design utilities, and telecom calculators. Pure local computation — no key, no third-party service, instant. Loss-limited model — at high bit rates dispersion can cap distance first. 3 compute endpoints. For fibre numerical aperture and photonics use a fiber API; for RF line-of-sight a Fresnel-zone API.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 80 ms
- Server probes · 24h
- Subscribers
- 4,798
- active
- Total calls
- 76
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 5,600 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 5,600 calls/month
- 2 req/sec
- Power budget + loss + reach
- No credit card
Starter
€11.80 /month
- 57,000 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- 57,000 calls/month
- 6 req/sec
- Connector/splice loss build-up
- Email support
Pro
€37.60 /month
- 238,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- 238,000 calls/month
- 15 req/sec
- FTTx & data-centre design pipelines
- Priority support
Mega
€116.00 /month
- 1,190,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- 1,190,000 calls/month
- 40 req/sec
- Carrier / OSP scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
RF Path Loss API
RF path-loss and link-budget maths as an API, computed locally and deterministically. The fspl endpoint computes the free-space path loss, FSPL(dB) = 20·log₁₀(d_km) + 20·log₁₀(f_MHz) + 32.44, the ideal line-of-sight attenuation between two antennas, and the wavelength. The linkbudget endpoint computes the received power, Prx = Ptx + Gtx + Grx − path loss − cable losses, the EIRP, and — given a receiver sensitivity — the link margin and whether the link closes. The dbm endpoint converts RF power between dBm, watts and dBW (0 dBm = 1 mW, 30 dBm = 1 W). Everything is computed locally and deterministically, so it is instant and private. Ideal for wireless, IoT, LoRa, Wi-Fi and radio app developers, link-planning and coverage tools, and RF engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is RF link budget; for VSWR and impedance match use a VSWR API and for antenna gain use an antenna API.
api.oanor.com/pathloss-api
Optical Fiber API
Optical-fibre photonics maths as an API, computed locally and deterministically. The numerical-aperture endpoint computes a step-index fibre's numerical aperture NA = √(n1² − n2²) from the core and cladding refractive indices, the acceptance angle θa = arcsin(NA) — the half-angle of the cone of light the fibre can capture — the full acceptance cone and the relative index difference Δ = (n1 − n2)/n1. The v-number endpoint computes the normalized frequency V = 2π·a·NA/λ from the core radius, the numerical aperture (or the indices) and the wavelength, classifies the fibre as single-mode when V is below the 2.405 cutoff or multimode above it, and gives the cutoff wavelength for single-mode operation. The modes endpoint estimates the number of guided modes — about V²/2 for a step-index fibre and V²/4 for a graded-index one — and confirms single-mode operation below the cutoff. Core radius and wavelength are in metres (1310 nm = 1.31×10⁻⁶ m) and refractive indices are dimensionless. Everything is computed locally and deterministically, so it is instant and private. Ideal for telecom, photonics, datacenter, sensor and laser app developers, fibre-link and waveguide-design tools, and optics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is optical-fibre guiding; for thin lenses and mirrors use a lens API and for refraction at a surface a Snell API.
api.oanor.com/fiber-api
MAC Address API
MAC-address (EUI-48) tooling as an API, computed locally and deterministically. The parse endpoint validates a MAC address given in any common notation — colon, hyphen, Cisco dotted or a bare run of 12 hex digits — and returns it in every standard format, split into its OUI (the first three bytes, assigned to a hardware vendor) and its NIC (the last three, device-specific) parts, plus the 48-bit integer value. The analyze endpoint reads the control bits of the first octet: the least-significant bit is the I/G bit that marks a unicast or multicast address, and the next bit is the U/L bit that marks a universally (vendor-assigned) or locally administered address, and it flags the broadcast address ff:ff:ff:ff:ff:ff. The eui64 endpoint derives the modified EUI-64 interface identifier — flipping the U/L bit and inserting FF:FE in the middle — and the resulting IPv6 link-local address (fe80::/64) used by stateless address autoconfiguration. Vendor name lookup needs the IEEE OUI registry and is not included. Everything is computed locally and deterministically, so it is instant and private. Ideal for networking, IoT, device-management, monitoring and security app developers, MAC-normalisation and IPv6 tools, and networking education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is MAC-address tooling; for IPv4 subnetting use a subnet API and for DNS records a DNS API.
api.oanor.com/macaddress-api
Data Transfer API
Data-transfer and bandwidth maths as an API, computed locally and deterministically. The time endpoint computes how long a file takes to transfer at a given bandwidth, time = file bits ÷ (rate × (1 − overhead)), accepting sizes in B, KB, MB, GB, TB or the binary KiB/MiB/GiB and rates in bps, Kbps, Mbps, Gbps or bytes-per-second (MB/s), with an optional protocol-overhead allowance, and returns the time in seconds, minutes, hours and a human-readable form. The bandwidth endpoint works backwards: the bandwidth needed to move a file within a target time, in bps, Mbps, Gbps and MB/s. The convert endpoint converts a data size between decimal (1 MB = 1,000,000 bytes) and binary (MiB = 1,048,576) units, or a data rate between bit-rates and byte-rates. Everything is computed locally and deterministically, so it is instant and private. Ideal for networking, cloud, backup and streaming app developers, download-time and capacity-planning tools, and dev dashboards. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is transfer time and bandwidth; for media encoding bitrate use a bitrate API.
api.oanor.com/transfer-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Fiber Optic Link Budget API?
What's the rate limit for Fiber Optic Link Budget API?
How much does Fiber Optic Link Budget API cost?
Can I cancel my subscription anytime?
Is Fiber Optic Link Budget API GDPR-compliant?
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/opticalbudget-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/opticalbudget-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/opticalbudget-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/opticalbudget-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
·
-
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.