# LION Marketplace Visibility Audit

**Status: public beta paid x402 route. Newly launched 2026-05-27. Awaiting first external buyer.**

Marketplace Visibility Audit is live as a public beta paid x402 route at `$0.05 USDC` on Base. LION's payment rail is proven by prior controlled Endpoint #1 settlements (Trend Intent MCP at `$0.01 USDC`). No external paid proof has been claimed for this endpoint.

A free first-pass audit is also available by email, no payment required, during the public beta.

## The problem

Your x402 or MCP service can be listed in directories (x402scan, MCP Registry, Glama, Smithery, Coinbase Bazaar) and still not be discoverable, callable, or payable by autonomous agents.

Common silent failures:

- stale `payTo` between `.well-known/x402.json`, your live 402 body, and your registry listing
- broken or missing `/.well-known/x402.json`
- 402 body that returns valid HTTP 402 but is not x402 v2-canonical (missing `accepts[].extra`, missing `extensions.bazaar`, wrong CAIP-2 network identifier)
- no `llms.txt`, no `agents.json`, no `OpenAPI` document
- `extensions.bazaar.discoverable = false` (or absent) so Coinbase Bazaar's catalog skips you
- inconsistent service metadata between Glama, Smithery, and your own canonical surfaces

Result: revenue looks like `$0` even when the service is technically live.

## What the audit checks

- `/.well-known/x402.json` availability and shape
- unpaid 402 body validity (x402 v2 `paymentRequirements` shape)
- `payTo` / `amount` / `asset` / `network` / `scheme` consistency across 402 body, well-known, registry listings
- x402scan listing presence and freshness
- MCP Registry listing presence and version freshness
- `/llms.txt`, OpenAPI document, `agents.json` presence
- Bazaar extension (`extensions.bazaar`) shape and `discoverable` flag
- top remediation recommendations ranked by expected discoverability lift

## Output

JSON report (see [`./visibility-audit.json`](./visibility-audit.json) for the full machine-readable descriptor) with:

- per-check pass/fail
- the specific bytes / fields that differ between surfaces
- a ranked list of remediation recommendations

## Paid endpoint (public beta)

| field | value |
|---|---|
| URL | `https://gleaming-cassata-d41682.netlify.app/api/x402/marketplace-visibility-audit-json` |
| Method | `GET` |
| Required query param | `?url=<https URL of the x402/MCP seller endpoint to audit>` |
| Price | `$0.05 USDC` (50000 atomic units) |
| Network | `eip155:8453` (Base mainnet) |
| Asset | `0x833589fcd6edb6e08f4c7c32d4f71b54bda02913` (USDC on Base) |
| payTo | `0x84c2e2ec19a4b467D89fE3F008591DEEA884d9Ac` |
| Scheme | `exact` |
| Auth | none |
| PII | none |

### Agent flow

1. `GET /api/x402/marketplace-visibility-audit-json?url=<https-url-to-audit>`
2. Receive HTTP `402` with x402 v2 payment requirements in the body and a `Payment-Required` response header.
3. Pay 50000 atomic USDC (= `$0.05`) on Base via x402 (CDP facilitator settles).
4. Retry the same `GET` (with the same `?url=` and the `Payment-Signature` header).
5. Receive HTTP `200` with the audit JSON report.

### Validation errors (before payment)

- `GET` with no `?url=` parameter → HTTP `400`, body `{"error":"invalid_audit_url","reason":"url_missing"}`
- `GET` with `?url=` that is not a valid https URL → HTTP `400`, body `{"error":"invalid_audit_url","reason":"url_unparseable"}`
- `GET` with a valid `?url=` → HTTP `402` with x402 v2 payment requirements

## Alternative: free first-pass audit by email

If you prefer to evaluate before paying, request a free first-pass audit:

Email `lionmaster.operations@gmail.com` with:

- subject: `[LION Visibility Audit Request]`
- body: the endpoint URL you want audited; your x402scan / MCP Registry listing URL if any; preferred reply channel

The output shape is the same JSON report you would get from the paid route. Limited by manual review; one-business-day turnaround.

## Honest status statement

Endpoint #2 is **public beta**. The paid route is live and the audit engine is built. **LION has not claimed any external paid proof on this endpoint.** LION's x402 payment rail is independently proven by prior controlled Endpoint #1 settlements (Trend Intent MCP) where on-chain USDC settlements have completed end-to-end. Endpoint #2 reuses the same rail.

## Sibling product

LION also runs **Endpoint #1: LION Trend Intent MCP** — a live x402-paid hardware-wallet buyer-intent JSON/CSV feed at `$0.01` USDC on Base. That endpoint is the production-proven proof product. See [`./agents.json`](./agents.json), [`./x402.json`](./x402.json), and [`./README.md`](./README.md).