08 / CATALOG SELLER HEALTH

Audit the catalog.
Keep every artifact in your environment.

The catalog pilot applies Andromalius's versioned challenge and discovery checks across customer-controlled snapshots before payment requirements reach buyers. It establishes one deterministic baseline and measures added, removed, changed, newly blocked, and resolved records without crawling sellers or entering the per-payment signing path.

Request a scoped conversation →Inspect the settlement boundary →
COMMERCIAL STATUS

Catalog seller-health pilot

$299 / 30 days

One organization, up to four customer-controlled checkpoints, up to 10,000 total audited items, no more than 100 batches per checkpoint, and at most 100 items per batch. No hosted ingestion. No automatic renewal. Written pilot terms and reconciled payment are required before delivery.

MANUAL DESIGN-PARTNER PILOT · NO SELF-SERVE CHECKOUT

WHO IT IS FOR

  • A marketplace or index needs buyer-policy evidence beyond reachability, manifest drift, dead accepts, and historical settlement.
  • A team wants to compare recurring x402 catalog snapshots without adding a remote dependency to each payment decision.
  • The customer can partition its own challenge and discovery artifacts into deterministic 100-item files and retain them locally.
  • A technical owner can evaluate whether versioned findings change a real listing, policy, or integration decision.

SCOPE / TRUST BOUNDARY

Run locally. Keep catalog artifacts local.

The private CLI reads only explicitly named, bounded local JSON files and writes JSON to standard output. It has no network, wallet, payment, signing, upload, persistence, telemetry, or automatic-update capability. Andromalius does not request the customer's source snapshots or complete reports.

Included in scope

  • One checksum-pinned private CLI built from an exact CI-passing source commit and verified against a separately delivered SHA-256 attestation.
  • One baseline plus up to three recurring diffs across no more than four checkpoints and 10,000 total items.
  • Stable finding-code registry and score-policy versions, exact JSONPaths, deterministic snapshot/report identities, and aggregate severity/code counts.
  • One onboarding session, one closing findings review, and best-effort support during the 30-day term.

Not promised

  • Hosted ingestion, seller crawling, arbitrary target fetching, catalog upload, telemetry, or automatic updates.
  • Wallet connection, payment signing, buyer identity collection, credentials, payment headers, or transaction analytics.
  • Automatic renewal, self-serve checkout, an uptime or response-time SLA, or a guarantee that every catalog issue will be detected.
  • More than one organization, four checkpoints, 10,000 total items, 100 batches per checkpoint, 100 items per batch, or 250 operations per discovery document.

MANUAL COMMERCIAL PATH

Agree on the boundary before private delivery.

There is no automatic enrollment or checkout. The pilot starts with a fit review and requires an agreed written order, reconciled payment, an exact checksum-pinned artifact, and a separately approved private delivery channel.

  1. 01
    Fit and boundary review

    Confirm the catalog shape, decision to be improved, accountable technical owner, customer-side data boundary, and success criteria.

  2. 02
    Written pilot order

    Agree on the exact 30-day scope, $299 price, permitted use, confidentiality, support, refund, deletion, offboarding, and liability terms.

  3. 03
    Payment and private delivery

    Reconcile the approved invoice, then deliver the exact tarball and SHA-256 attestation through the separately approved private channel.

  4. 04
    Baseline, diffs, and decision

    Run one baseline and up to three recurring diffs, then close with an explicit renew, revise, or stop decision based on useful signal and operating cost.

Founding-beta boundary

Andromalius currently serves United States business users age 18 or older. The public service is bounded and single-node. Any customer-specific service level, retention, support, security, or refund term must be written into the applicable pilot or deployment agreement.

Email support@andromalius.io →Start with a $0.01 audit →

Contacting us does not create a subscription, deployment, payment authorization, or service-level commitment. Terms · Privacy · Acceptable use · Refunds