Runtime functions and extensions - Neuro Developer Documentation

Script discovers functions from loaded assemblies. The exact catalog depends on the Neuron build and installed packages, but functions are organized into stable capability families.

Core families

Family	Examples of capability
Analytic	powers, logarithms, trigonometry, calculus helpers
Scalar and complex	conversions, rounding, complex components
Strings	split, replace, trim, parse, evaluate
Date and time	components, UTC conversion, durations
Vectors and matrices	aggregates, transpose, inverse, determinant
Runtime	type creation, reflection, variables, flow helpers
Logging	structured event creation

Module families

Assembly family	Capability
`Waher.Script.Persistence`	object SQL, indexes, persistence functions, SPARQL integration
`Waher.Script.Data.*`	external SQL, MySQL, PostgreSQL
`Waher.Script.Content`	encode, decode, and negotiate Internet content
`Waher.Script.Cryptography`	hashes, keys, signatures, encryption helpers
`Waher.Script.Xml*`	XML, XPath-like selection, XML signatures
`Waher.Script.Networking`	DNS and network operations
`Waher.Script.Graphs*`	charts, plots, 3D graphs
`Waher.Script.Statistics`	distributions and statistical functions
`Waher.Script.System`	operating-system integration
`Waher.Script.Threading`	parallel and synchronization helpers
`Waher.Content.*`	Markdown, semantic, XSL, images and document rendering
`Waher.Things.*`	sensor, actuator and concentrator objects

Neuron-specific functions

The IoT Broker package adds functions for:

XMPP messaging, presence, roster lookup, ping, and IQ requests;
contract creation, proposal, rejection, and obsoletion;
token state, history, profiling, attachments, and actions;
email messages, embedded resources, and attachments;
country/locale and configured local services;
runtime counters and administrative reporting.

Additional payment, KYC, Microsoft interoperability, SMS, OpenAI, and provider functions appear only when their packages are installed.

Discover at runtime

Use reflection helpers such as Functions, Methods, Properties, Fields, and Names where available in the current context. For shared production code, declare the package dependency instead of dynamically guessing whether a function exists.

Function availability is an API surface. Package authors should document names, arguments, return shapes, side effects, privileges, and version changes.