#abi

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

Check whether any EVM smart contract source code is verified and pull its ABI, source files and deployment details, keyless. Give it a chain id and contract address and get the verification status (full / partial / not verified), the compiler and contract name, the deployment info (deployer, transaction, block), the contract ABI (the JSON interface every integration needs), and the verified Solidity source. Live, nothing stored. The contract-verification / ABI layer for security, due-diligence, block-explorer, wallet and dapp tooling — backed by the open Sourcify registry, distinct from price, TVL and chain-registry APIs.

api.oanor.com/contractverify-api

Decode Ethereum smart-contract function and event signatures, keyless. Turn a 4-byte function selector (the first 4 bytes of any transaction calldata, e.g. 0xa9059cbb) into its human-readable function signature (transfer(address,uint256)), decode a 32-byte event topic from a log into its event signature, or search the database by name to find a selector. Many selectors have hash collisions — the API flags the original / canonical signature. Backed by the open 4byte.directory database, live. Essential for transaction decoders, block explorers, wallets, security tools and on-chain analytics — the signature-decoding layer for any EVM tooling.

api.oanor.com/ethsignatures-api