🇱🇻 LV

AI agent for Omniva LV

Connect Omniva LV to your AI agent through the WorkAist MCP server. LV parcel locker

In 60 seconds

The WorkAist Omniva LV connector is a production-grade Model Context Protocol (MCP) server. AI agents can read and write Omniva LV data — shipping — through one consistent interface. Open-source under AGPL-3.0, self-hosted, with reversible PII redaction at the LLM boundary.

Authentication & setup

The Omniva LV connector authenticates via API key.

API key in header

Generate an API key in the service dashboard and paste it at install time. WorkAist encrypts it at rest.

Frequently paired with Omniva LV

FAQ

Can a WorkAist AI agent really automate Omniva LV end-to-end?

Yes. The connector exposes read and write tools through Model Context Protocol. AI agents call them through plain-language instructions in a CLAUDE.md file — no glue code.

How does this differ from using the Omniva LV API directly?

The connector adds permission isolation, audit logging, cost tracking per agent, and reversible PII redaction at the LLM boundary. It also presents Omniva LV as part of a unified Knowledge Graph alongside your other tools.

What does it cost?

WorkAist is open-source under AGPL-3.0 and self-hosted, so the connector itself is free. You pay only for Omniva LV's own API costs (if any) and the LLM tokens your agent consumes.

Is my Omniva LV data sent to a third party?

No. WorkAist runs in your own infrastructure. Data flows from Omniva LV → your WorkAist instance → the LLM you choose. Sensitive fields can be tokenized before reaching the LLM.

What if Omniva LV changes its API?

The connector is versioned and published openly. When Omniva LV ships breaking changes, we bump the connector version and the marketplace UI surfaces the upgrade as a one-click apply.

Source code on GitHub · Licensed under AGPL-3.0 · Self-hosted, your data stays yours.