Skip to main content

PreviewThis site previews the LITS standard and platform.

The open standard

An open standard, and the platform that runs it

LITS (Livestock Identification & Traceability System) is a published API contract any vendor can build against, plus a multi-tenant platform that operates a sovereign registry for each nation. A national instance — illustrated on this site as ZLITS or MLITS — is the same standard, run for one country on its own government domain.

ANY VENDOR · EQUAL TERMSOpenAPI · /v1{ }Farm appAuctionAbattoir

The record

  • The authoritative system of record for animal identity, movement permits and health events
  • Owned by the State, on a State domain
  • One national ID per animal, held by the registry rather than any vendor

The standard

  • An open, versioned API contract any vendor can build against on equal terms
  • A public conformance suite, so integrations and the contract never drift
  • Governed in the open, with a public changelog

Open as a standard, held as an implementation

The API contract, examples and conformance suite are open (Apache-2.0), so any vendor can integrate without a private agreement and no nation is locked in. Accredited integrators connect with their own per-operator keys; the reference implementation that runs a national registry is held by the operator.

Versioned and additive

Path-versioned (/v1); additive changes never break a client. Build against it and ignore the fields you don't consume.

Conformance-tested

A public conformance suite ties behaviour to the contract, so the standard and its implementations cannot drift apart.

Open governance

Changes go through a public process and changelog, so the standard stays vendor-neutral and outlives any one operator.


Build on the contract

Farm apps, abattoirs and auctions integrate against the published OpenAPI contract — equal terms, no lock-in. Accreditation, not ownership, is the gate.

The open contract and a sandbox let vendors build and test today — before any nation goes live.

Common questions

Can a competitor to FuroTrack integrate on the same terms?
Yes. The contract is open and every integrator uses its own per-operator key. FuroTrack is the reference client for the standard — it submits to the registry on equal terms with any other vendor, and is never privileged over them.
Who can issue an official certificate?
Only the competent authority. Keepers and vendors request a certificate; the authority inspects, attests and signs it. Vendors never mint sovereign documents — see how it works.
Do I need permission to build on LITS?
No. The contract is open under Apache-2.0 — build and test against it in the sandbox, then get accredited for a live per-operator key when you are ready for production.

Related