Live x402 API · paid deployment evidence

Choose the sharp release that survives your target deployment

Send one exact Node/Linux target. Get a cached, twice-run comparison of sharp 0.35.1–0.35.3, with a production pin only when every required check passes. The service never inspects your repository.

3 releases × 2 runs$0.01 per valid paid callPOST /v1/sharp/release-choice

Dataset readiness

Not ready: no deployable dataset is available

The service is exposing contract fixtures or unavailable evidence. It will not request payment or authorize a dependency change.

Price

$0.01

Configured request price. Payment remains disabled until the dataset is ready.

7-day freshness window

Every observation in the proof matrix must be no more than seven days old and must not be dated in the future. A stale or future timestamp closes readiness before payment.

Exact request scope: six targets

Profile: native+nft-v1. Supported target values are fixed:

Example request input

POST JSON to /v1/sharp/release-choice.

{
  "target": "node24-alpine-amd64",
  "profile": "native+nft-v1"
}

No current result, recommendation, candidate classification or evidence digest is exposed before a successful payment.

What the evidence checks

Offline npm ci with lifecycle scripts disabled, CommonJS and ESM imports, a native PNG transformation, @vercel/nft tracing, network-disabled artifact replay, and agreement across two independent runs for the exact target.

Explicit exclusions

  • Your repository, lockfile, dependency graph, application code or production workload
  • Windows, macOS, ARM, Bun, pnpm and Yarn
  • Framework-specific or cloud-provider deployment behavior
  • Performance, memory-leak and production-load guarantees
  • Global libvips builds and optional codec coverage such as HEIC or PDF
  • Package lifecycle scripts and source-build fallback; v1 tests the prebuilt path only
  • Any package version, Node release, libc, architecture or profile not listed above

Inspect before calling