Menu

How Napexa works

A product layer for AI agents: authorised data, resolved to exact products, with prices that say how complete they are and links that only exist when the merchant permits them.

The problem it solves

An agent asked to “find the cheapest 18V drill that fits my existing batteries” has to answer four different questions, and general web search answers none of them reliably: which product is this exactly, does it genuinely fit, what does it actually cost delivered, and may I send someone to buy it.

Napexa answers those four questions separately and says how confident it is in each. Where it does not know, it says so rather than guessing — which is the only useful behaviour when something acts on the answer without a person checking it.

Where the data comes from

1 · Ingest

Merchant feeds, APIs and — only where a merchant has opted in — their own site. Every record carries its source, when it was observed, and the rights policy attached to it.

2 · Resolve

Listings from different merchants are matched to one canonical product using barcodes and part numbers first, and text only as corroboration. A wrong merge is worse than two entries, so the thresholds are set to split rather than merge when unsure.

3 · Answer

A search returns the offers a caller is permitted to see, each priced with an explicit completeness state, and discloses what was not searched.

What happens when you search

  1. The query is read literally. A brand, a model number, a size or a budget in the text becomes a constraint. Nothing is inferred that the words do not support.
  2. Rights are applied before ranking. A source that has not permitted the use being made of it is excluded first, so it cannot influence the order of what remains.
  3. Prices are assembled, not assumed. Item price, shipping and tax are separate facts. Where shipping is unpublished the total is marked incomplete and the wording drops to “lowest known item price” — it never says “cheapest” about a number it cannot complete.
  4. Ranking is organic. Relevance, price completeness, freshness and identity confidence. Commission is structurally excluded — see how ranking works.
  5. The answer discloses its own gaps. How many merchants were searched against how many are known, which offers are stale, and what was withheld.

Buying something

Napexa does not take the payment for a catalogue product. A purchase route is prepared — the destination is checked against the merchant’s verified domain, the provider’s programme terms and the caller’s context — and then the person is shown where they are going and confirms. The merchant remains the merchant of record.

A route exists only where policy permits one. There is no universal redirect, and a merchant whose terms forbid deep links is not deep linked. Where we earn a commission it is disclosed, and it plays no part in the ranking that produced the result.

Two ways in

REST

An ordinary JSON API. Search, resolve an identifier to a product, check compatibility, find replacements, prepare a purchase route. The endpoints.

MCP

The same services as tools an agent can call directly, over a stateless server. No session state, and the credential travels with each request. Getting a key.

What it deliberately does not do

  • It is not a web-scale crawler. Crawling is off by default and per-merchant opt-in. No paywall, login or bot protection is ever bypassed.
  • It is not a checkout. For catalogue products the merchant takes the money. Napexa never holds card details.
  • It does not cover the whole market. Amazon is excluded because its terms conflict with a general third-party API, and merchants who have not authorised us are not there. What is and is not covered.
  • It does not let a model decide a fact. Prices, currencies, barcodes and part numbers are read deterministically. A language model may help interpret a request; it never decides what something costs or what it is.

What is in it today

Proof in the data

A catalogue you can inspect.

Current figures from the catalogue, not a build-time estimate.

Suppliers with productsLive
363

Merchants represented by at least one active offer.

ProductsLive
746,871

Canonical products resolved from authorised data.

OffersLive
764,026

Active offer records with source and freshness context.

Sources we may searchLive
402

Licensed or otherwise permitted sources, not suppliers with stock.

Data region

GBmerchant country

Derived from the country recorded for suppliers represented in the catalogue.

Market types represented

By supplier
1
Builders' merchants
54
DIY
64
Hardware
1
Timber
17
Tool hire
176
Trade

These are the merchants and sources this service has rights to search. It is not a complete view of the market.