Rasczak agent service

Ten free, source-linked decision methods, three optional decision packs, REST, static pages, a stateless MCP endpoint, and an offline Agent Skill. Requests use reviewed fixed content and make no model calls. Payments are disabled by default; deployment owners must verify live settlement before enabling them.

Run locally

npm ci --include=dev
npm run check
npm run deploy:dry
npm run dev

Use Node 22 or the pinned local Node dependency. The SQLite tests use Node's experimental built-in driver; hosted receipts use Cloudflare D1.

Related MCP server: agentstorefront-mcp

Interface

• /api/v1/catalog lists supported methods and packs.

• /api/v1/methods/{id} returns a free method; unknown IDs return 404.

• /api/v1/sample returns a complete free vendor-evaluation pack.

• /api/v1/packs/{id} offers an optional assembled pack. Disabled payments return 503; enabled payments require verified, recorded settlement.

• /mcp exposes catalog, method, sample_pack, and pack_offer through Streamable HTTP. None of these tools pays or authorizes spending.

• /full returns 410.

• skill/rasczak-knowledge-commons contains the offline skill and its ten references.

Connect clients to the origin configured by the deployment owner. Service URLs and repository links are configuration, not embedded account identifiers.

For MCP Registry HTTP ownership verification, optionally set MCP_REGISTRY_PUBLIC_KEY to a base64 Ed25519 public key at build time. The public verification record is generated at /.well-known/mcp-registry-auth. Keep the matching private key exclusively in your secret store; the server never needs it.

Build and publish

scripts/build.mjs generates the static release from the curated catalog. scripts/package-release.mjs creates a separate source package using an explicit allowlist. Both run the privacy validator before writing output. Unknown release files stop packaging.

Set RELEASE_PRIVACY_POLICY to a private JSON policy file containing forbiddenStrings for local names, account identifiers, original filenames, and internal project names. Keep this policy outside the release. allowedPublicUrls can exempt exact approved public endpoints from identifier matching. Pattern checks alone cannot recognize every private identifier. Review Git history and author metadata separately before pushing.

Publish only the generated package from a fresh, separate checkout. Use neutral author metadata. Do not copy source archives, session records, browser profiles, credentials, debug logs, source maps, or original working folders into it. Generic paths such as data/input.json describe the distributable structure only. Public primary-source citations are retained so method claims remain verifiable.

Deployment

1. Authenticate the hosting CLI to the intended account. Supply configuration through the process environment and the hosting secret store. Never include credential values in source, logs, commands, or documentation.

2. Set PUBLIC_ORIGIN to the verified HTTPS origin at build time and in the deployment configuration. Optionally set PUBLIC_REPOSITORY to the approved public repository. Rebuild and run npm run deploy:check.

3. Keep PAYMENTS_ENABLED=false and MAINNET_SETTLEMENT_APPROVED=false. Deploy only the allowlisted assets and Worker. Verify the homepage, health, catalog, sample, unknown IDs, Origin rejection, disabled payments, and an actual MCP client connection.

4. If receipts are needed, create a D1 database, bind it as RECEIPTS, and apply migrations/0001_receipts.sql. Use your own database identifier. Back up receipts before schema changes.

5. Use Base Sepolia and its exact USDC asset for payment trials. Configure X402_PAY_TO from a controlled receiving address. A receiving-wallet private key is never needed by this server.

6. Store facilitator credentials as hosting secrets. Verify real settlement, identical retries, replay rejection, ambiguous-settlement reconciliation, and result recovery. An explicitly authorized bounded mainnet trial must pass before production payments are enabled.

7. Use the verified namespace and URL for registry listings. Confirm listings and actual independent usage separately. No listing or customer count is implied by these source files.

Payment behavior and limits

The service uses x402 v2 exact EIP-3009 on Base or Base Sepolia with a 120-second authorization window. It supports 65-byte EOA signatures. Local signature tests are cryptographic; settlement tests use fixtures.

Receipts bind network, asset, payer, nonce, proof hash, resource, and transaction. The result is stored before settlement. The same recorded proof retrieves the same result without another charge. Changed resources are rejected. Uncertain settlement is quarantined and never automatically retried.

If settlement succeeds but receipt commit fails, reconcile the receipt with facilitator and chain evidence before recovering the stored result. Never clear a reservation to force another payment. No public receipt-edit endpoint or automated refund action exists.

See EVALUATION.md for the measurement protocol. Tests, visits, and owner payments do not establish customer demand.