Define
Agree on the catalog boundary, customer-controlled checkpoints, and a decision the pilot should improve. Do not send catalog artifacts with an inquiry.
CUSTOMER-LOCALVERSIONED FINDINGSCHECKPOINT DIFFS
Audit the catalog.
See what changed.
Review x402 payment requirements across your catalog and compare findings between snapshots. For catalog operators, agent gateways, and release teams: a customer-local CLI, versioned findings, and no catalog uploads or remote dependency before each payment.
Proposed $299 / 30 days · one organization · up to four checkpoints and 10,000 total items. No automatic renewal. Inquiry only; professional review and written terms are required before private delivery. Need a single artifact check? One-off audits start at $0.01.
9x402scan operations listed
2paid audit products
Localprivate catalog execution
Basemainnet-native settlement
01 / THE SYSTEM
Establish a baseline.
Review the changes.
Analyze caller-supplied challenge and discovery snapshots before they reach buyers. Keep simple payment allowlists local. Use catalog findings to inform listing, integration, and release decisions—not as a remote dependency for every signature.
Baseline
After the delivery gates clear, run the checksum-pinned private CLI on local snapshots.
Compare
Review added, removed, changed, newly blocked, and resolved records across checkpoints.
Decide
Evaluate useful findings against predeclared criteria. Synthetic examples are not proof of customer accuracy.
02 / HARD BOUNDARIES
Your catalog stays on your side.
The proposed private CLI analyzes local files without network access, signing, or uploads.
01Customer-local CLI✓
02Caller-supplied snapshots✓
03No target crawling✓
04No artifact uploads✓
05Versioned finding codes✓
06Deterministic digests✓
07Four checkpoints maximum✓
08No automatic renewal✓
03 / CHOOSE THE SCOPE
Catalog review first.
One-off checks when useful.
Start with the catalog pilot for repeated snapshot reviews. The existing paid API is a smaller, optional path for evaluating one supplied artifact or checking a release.
Primary offer · design partner
Catalog seller-health pilot
Review supplied x402 catalog snapshots and compare versioned findings between checkpoints. A private CLI runs on your side; artifacts stay in your environment.
$299 / 30 days · up to 10,000 total items · no automatic renewal · Explore →One-off checks · paid beta
Independent x402 audits
Inspect one supplied challenge or OpenAPI document when evaluating an artifact or preparing a release. Keep simple allowlist checks local and outside a remote payment dependency.
$0.01 challenge audit · $0.02 discovery audit · Explore →Supporting tools and separate inquiries: client integration, team controls, and enterprise deployments.
04 / SEE THE DECISION
A small mismatch can redirect real money.
This deterministic synthetic example expects one recipient and a $0.10 ceiling. The supplied challenge asks for $0.25 at a different address. The report flags both mismatches without contacting the target merchant. It demonstrates report shape, not general accuracy. Review the evaluation boundary.
- 01 Supply a decoded x402 v2 challenge or payment-required header.
- 02 Add the network, asset, payee, scheme, and maximum you expect.
- 03 Receive a scored JSON report with precise blocking findings.
CHALLENGE-AUDIT / REPORT V1BLOCK
CONFORMANCE SCORE30/ 100
Higher means fewer findings. 100 − (2 × 35) = 30. Gate on passed and severity, not score alone.
CRITICAL
PAYEE_POLICY_MISMATCH
Pay-to differs from the caller's expected policy.
CRITICAL
AMOUNT_POLICY_EXCEEDED
250,000 atomic USDC exceeds the 100,000 maximum.
USDCBASE
SETTLED
IDEMPOTENT
HASH-CHAINED
05 / REVENUE INTEGRITY
Money lands in the wallet. Evidence lands in the ledger.
For the separate paid API, revenue settles directly to the configured Base wallet. Andromalius records a privacy-minimized, transaction-bound accounting trail—without storing payer identity or customer audit inputs.
- 01 Duplicate transaction retries never inflate totals.
- 02 Edited or partial records fail verification.
- 03 Revenue summaries open the ledger read-only.
- 04 Operators reconcile against Base and facilitator records.
06 / CURRENT STATUS
Founding beta live.
Hard limits stay visible.
COMPLETE Source, package, tests, audits, and revenue ledger
COMPLETE Hosted container qualification
COMPLETE Domain, public website, DNS, and managed TLS
COMPLETE Dedicated merchant API and Base USDC payment gate
COMPLETE Canary, backups, telemetry, and accounting alerts
COMPLETE x402scan registration and bounded paid beta
LIMITED Public sole-proprietor identity and owner-approved US-business beta policies
PENDING New York assumed-name classification and counsel review before expanding the beta
07 / STRAIGHT ANSWERS
What the system does—and what it does not.
Who is the catalog pilot for?
US-business catalog and index operators, agent gateways, and release owners who need to review advertised payment requirements across snapshots. It complements reachability and historical seller checks; it does not replace them.
Does this add a remote check to every payment?
No. The catalog pilot runs on customer-controlled snapshots outside the payment-critical path. Keep simple payee and amount allowlists local. The public API remains available for optional one-off artifact audits.
Can I buy or download the pilot immediately?
No. This is a proposed, manually scoped $299 / 30 days engagement, not self-serve checkout. Professional review, a written customer-specific order, reconciled payment, and an approved private delivery channel are required before delivery. There is no automatic renewal or SLA.
Does Andromalius hold customer funds?
No. The buyer uses a locally controlled, explicitly allowlisted wallet. The team service receives policy and sanitized usage data—not private keys or payment authorizations.
Can an agent pay any URL?
No. The client exposes a closed registry of services pinned by policy. Origin, route, network, token, payee, price, timeout, and response shape must all match.
Where does merchant revenue go?
Independent-audit revenue settles as native USDC directly to the configured Base wallet. A transaction-idempotent, hash-chained ledger provides a separate application accounting trail.
Is the public service live?
Yes. The paid founding beta is live with $0.01 challenge audits and $0.02 discovery audits settled in native Base USDC. It is deliberately single-node and bounded by hard cumulative call and revenue ceilings, so it is not presented as highly available or million-call qualified.
ANDROMALIUS / CUSTOMER-LOCAL CATALOG AUDITS
Make the next catalog review useful.
Review the $299 / 30 days pilot scope and evaluation evidence before discussing an order. No catalog uploads, automatic renewal, or SLA. Professional review, written terms, reconciled payment, and separately approved private delivery remain required. The separate paid API remains available to United States business users under its bounded founding-beta policies.
Explore the catalog pilot →