What is Nivah and what does it do?

Nivah is a user-owned, multimodal commerce agent built to carry a shopper’s intent through research, decision support, exact approval, controlled payment authorization, and a verifiable result. In plain terms, it helps people buy with useful automation, while keeping spending under explicit user control.

It is designed for shoppers who want more than product-search chat. Nivah can accept text, voice, and reference images, then research products, verify sellers and execution routes, rank options against real constraints, and route only eligible actions through approval. Its promise is simple: your intent, carried through.

What Nivah does

Nivah helps with the parts of shopping that usually take time and create risk:

Researches products and sellers across merchants and independent evidence
Checks execution routes to see whether a route is capability-checked and selectable
Separates evidence from action so a useful listing can remain a Market Reference without becoming an Autonomous Offer
Ranks options by real constraints, not just by lowest price
Requests exact approval before any consequential step
Uses Prava for payment authorization
Issues a verifiable Trust Receipt that preserves merchant and authorization outcomes

That last point matters. Nivah is not trying to guess what you want and spend for you. It uses recommend-and-ask autonomy. Research can be broad. Spending stays deterministic and user-controlled.

How the workflow works

A typical Nivah flow starts with an intent, not a product name. For example, a recurring need can be captured as a Standing Intent with a budget and material-change rules. Nivah then looks for options that fit the request and checks whether a route is actually executable.

If a listing is useful but the route cannot be verified, it can appear as a Market Reference. That is context, not a checkout option. If a route is capability-checked, it may become an Autonomous Offer and move forward for approval.

Before anything is authorized, Nivah shows the exact terms that matter: variant, quantity, destination reference, shipping method, recurrence terms, and delivered total. The user must confirm the approval control before Nivah opens the separate Prava authorization experience.

This is the core control model:
evidence first, exact approval second, authorization third.

What Nivah can research and compare

Nivah is built to compare more than just price. In the product documentation, it can evaluate:

product and price
seller identity
package quantity
return policy
warranty or other relevant quality evidence
stock
freshness

It then ranks results for requirement fit and trust, not cheapest price alone.

That is important for real shopping. A cheaper option is not always the better one if the seller is unclear, the package is different, stock is uncertain, or the return policy is weak. Nivah is designed to surface those differences before a shopper approves anything.

What Nivah does not do

Nivah is explicit about its boundaries.

It does not claim every discovered merchant can be purchased automatically
It does not present a sandbox or test route as a live merchant purchase
It does not invent filler offers just to make a list look complete
It does not treat inferred preferences as spending authorization
It does not collect or store card numbers, CVVs, OTPs, passkeys, or one-time payment credentials

Today, the public product includes a clearly labeled controlled sandbox/test route for demonstrations. Real merchant automatic checkout remains disabled until a route passes the required probes.

That distinction is central to Nivah’s trust model. Useful evidence is not the same thing as executable authority.

A concrete example: recurring cartridges

One of the product’s illustrative workflows is a recurring purchase like razor cartridges. Nivah can subscribe to the outcome, not a blind SKU repeat.

If the seller changes, the package size changes, the unit price changes, stock changes, or the merchant changes, Nivah stops and refreshes the quote. The shopper can then:

approve the new terms
skip once
change the cap
switch products
pause the intent

That is what exact approval looks like in practice. The system does not assume yesterday’s approval still applies today.

Why shoppers and commerce teams use it

Nivah is useful when the cost of a wrong purchase is higher than the cost of a slower decision. That includes recurring household items, comparison-heavy categories, and purchases where seller quality matters as much as product specs.

For shoppers, the benefit is control without losing automation.

For commerce practitioners, the value is a clearer trust chain:

user intent
verified evidence
execution eligibility
exact approval
payment authorization through Prava
Trust Receipt

Nivah is currently a hackathon-stage product with a deployed web experience and a controlled sandbox/test execution path. It is best understood as a focused commerce workflow, not a claim of universal merchant coverage or full autonomy.

In one sentence

Nivah is a user-owned commerce agent that helps you research, verify, compare, approve, authorize, and document purchases with explicit control at every consequential step.