Integrations

What you can build against today, and what is on the roadmap. The two are kept separate on purpose — a roadmap item presented as a feature is a bad way to start a working relationship.

Available now

Embedded Engine SDK

In-process TypeScript and JavaScript library (@nomoredata/metadata-engine) for Node.js >= 18 and browsers. Zero dependencies, CJS and ESM modules, and complete type safety.

Explore engine capabilities

HTTP API

Versioned endpoints for analysis, cleaning, editing and device profiles. Multipart in, JSON or the processed file out. Works with any HTTP client.

Read the documentation

OpenAPI description

A machine-readable OpenAPI 3.1 schema you can generate typed clients from, or import into an API tool.

View the schema

Planned, not built

None of the following exists yet. They are listed so you can tell us which would matter to you, not so you can plan around them.

Registry Package Distribution

Directly installable native packages published on package registries (PyPI, crates.io) for teams that prefer pre-packaged wrappers over generating clients from our OpenAPI schema.

Embeddable widget

The metadata tool as a component you can place inside your own interface, keeping the browser-side processing model so your users’ files stay on their devices. Not built yet.

White-label deployment

Running the engine under your own brand and domain. Technically the engine has no native dependencies and no database, so it deploys as an ordinary Node service — but the licensing terms need to be agreed rather than assumed.

Webhooks and batch endpoints

Asynchronous processing for large volumes, with completion callbacks. The current API is synchronous and processes one file per request.

Tell us what you need

What gets built next is decided by what integrators actually ask for. If one of the above would unblock you, say so.