Precise claims. Narrow inputs. Objective refunds.

What the initial paid profile accepts

One public GitHub repository, one full lowercase 40-character commit, one explicit Agent Skill directory, and the fixed public-static profile. VouchSpec does not accept branches, tags, private repositories, credentials, uploads, customer-confidential content, or custom commands in this stage.

What the receipt means

A receipt identifies the exact source and content digest, the checks performed, the environment, the evidence labels earned, material limitations, timestamps, and signature. It is evidence about those checks—not a promise that the artifact is malware-free, universally safe, publisher-authentic, or correct in every runtime.

Artifact execution

The initial commercial profile performs static inspection. Artifact scripts are not executed. Retrieval is separated from the no-egress worker, and the signer receives only the frozen request, bounded worker result, and allowlisted worker identity.

Refund conditions

A refund is due for a duplicate charge; a settled payment where VouchSpec never starts the job because of its own failure; a job that fails before a signed receipt is produced; an unsupported request accepted because of a VouchSpec validation defect; or a delivered receipt with an invalid signature or wrong source, commit, path, or digest after one automatic rerun.

Test environment

The managed sandbox uses x402 exact payment of 1 test USDC on Base Sepolia. It exercises onchain settlement, isolated fulfillment, signing, public receipt caching, and live invalidation without creating revenue, and is excluded from customer, request, and traction metrics. Mainnet remains disabled until live environment separation, automatic onchain remedies, and actual cost accounting pass.

Credential handling

Tenant API keys and delivery capabilities are shown to the caller and stored only as keyed digests. A result requires both credentials. Delivery capabilities expire, may be rotated, and may be revoked immediately.