#module

Inspect the Move smart-contract code published in any Sui package, live from a public Sui fullnode JSON-RPC — no key. Sui contracts are published as packages of Move modules; this reads their normalized ABI: list every module in a package, read a module's exposed functions (visibility, entry flag, type parameters with their abilities, parameter and return type tags) and struct definitions, or drill straight into a single function's signature. Unlike object- and coin-readers, this exposes the callable interface itself — exactly what a Sui package lets you do — the layer Sui wallets, explorers, programmable-transaction-block builders and SDK and binding generators need before they can construct a transaction. Reads straight from the chain; live, short cache only.

api.oanor.com/suimodules-api

Inspect the Move smart-contract code published at any Aptos account, live from the official public Aptos fullnode REST API — no key. Where a resources endpoint shows an account's data, this shows its code: list the Move modules an account publishes, read any module's full ABI — its exposed functions with their visibility, entry and view flags, generic type parameters, parameter and return types, plus its struct definitions — and filter straight to the callable entry functions (state-changing transactions) and view functions (read-only queries) a dApp can invoke. The on-chain interface layer for Aptos wallets, explorers, SDK and binding generators, and security tooling that need to know exactly what a contract exposes before calling it. Reads straight from the chain; live, short cache only.

api.oanor.com/aptosmodules-api

Spur-gear geometry as an API, computed locally and deterministically for standard full-depth involute teeth. The geometry endpoint takes a module and a number of teeth (and an optional pressure angle, default 20°) and returns the complete tooth geometry: the pitch diameter (module × teeth), the base, tip (outside) and root diameters, the addendum, dedendum, whole and working depth, the circular and base pitch, the diametral pitch and the tooth thickness — all in millimetres. The module can be given directly or derived from a diametral pitch or a circular pitch. The pair endpoint meshes two gears of the same module and returns each gear's pitch and tip diameter, the centre distance (module × (z1 + z2) ÷ 2) and the gear ratio. The module endpoint converts freely between module, diametral pitch and circular pitch, or derives the module from a pitch diameter and tooth count. Everything is computed locally and deterministically, so it is instant and private. Ideal for machine-design and CAD tools, gear and gearbox calculators, maker, robotics and 3D-printing projects, and mechanical-engineering apps. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is spur-gear geometry; for bicycle gear ratios and development use a bike-gear API and for belt-and-pulley drives use a belt-drive API.

api.oanor.com/spurgear-api