Dira

Zambia's business
intelligence.

Dira turns the public registers into tools you can act on: verify a business, watch it for change, screen it against the lists, and file a record that proves you did.

See a sample record Live at dira.oapps.dev
A compliance officer holding a printed verification record
Verification record VR-…-0A7F3K
Zambeef Retailing Limited 3 of 4 passed
Registry statusActive
Tax registrationTPIN 1001747472
VAT registrationRegistered
Annual returnsNot current
dira.oapps.dev/verify/VR-…
Verify
A filed, hash-stamped record: real, licensed, current.
Watch
Alerts when returns lapse, licences expire, names change.
Screen
Sanctions and debarment, with a human on the decision.
API
The same answers inside your own systems.
Built on Zambia's own registers PACRA · ZRA · ZAMRA · Mining Cadastre · Bank of Zambia · NCC · HPCZ · ZTA · ZICTA · PIA · SEC · ZICA · Government Gazette Screened against the UN, OFAC, UK and EU sanctions lists and the World Bank and AfDB debarment lists.
19 registers and watchlists
30,000+ licences indexed
92 strike-offs caught in a month

Made for the work

Procurement and supply chain
Procurement and supply chain Three hundred suppliers on the vendor list, and Smart Invoice means one non-compliant customer can cost you your own VAT deduction.
Registered, tax-registered and VAT-valid, before the PO, not after
NCC grade checked against the grade the bid claims
Debarment and Gazette strike-offs watched across the whole list
PACRA · ZRA · NCC · World Bank and AfDB lists

From a name to a filed record

Step 1 Search A name, a TPIN or a Dira ID. If Dira's index doesn't know it, the registers are read live before anything is said.
Step 2 Issue the record Every check carries its source and read time. Immutable, hash-stamped, publicly confirmable.
Step 3 Watch Returns lapse, licences expire, names change in the Gazette. Dira tells you first.
Two colleagues reviewing a verification record together

Built for the person who signs

Provenance on every fact Each field names its register, its URL and the moment it was read, so your auditor sees the same trail you do.
Records that cannot be quietly edited Append-only history plus a SHA-256-stamped PDF. Re-verifying issues a new record; the old one stands.
Screening a human confirms Matches open a review with the score. A named person decides, never the machine.
History that compounds Every version of every record is kept, so changes become signals, not surprises.

One call, one answer

The same records over an API your systems can file: idempotent verifications, signed webhooks when a watched company changes, and a public link to confirm any PDF is genuine.

Read the API reference
curl https://dira.oapps.dev/v1/verifications \
  -H "Authorization: Bearer dira_live_…" \
  -d '{"name": "Zambeef Retailing Limited",
       "purpose": "supplier_onboarding"}'

{ "result":  { "passed": 3, "attention": 1 },
  "checks":  { "registry": { "status": "pass",
      "source": "pacra", "read_at": "…" }, … },
  "report_url": "…/verify/VR-…" }