Subscription MarketTerminal guide
plain shell

Terminal setup for Subscription Market

Use this for direct local testing before adding an integration-specific page.

1. Install + request access

Log first-run and submit access demand.

PACT_EMAIL="${PACT_EMAIL:?set PACT_EMAIL}" PACT_REQUESTER="${PACT_REQUESTER:?set PACT_REQUESTER}" PACT_ORGANIZATION="${PACT_ORGANIZATION:?set PACT_ORGANIZATION}" PACT_PROJECT="${PACT_PROJECT:?set PACT_PROJECT}" npx --yes --package https://pact.sh/packages/npm/subscription-market/pact-subscription-market-0.1.2.tgz pact-subscription-market install --api-url https://pact.sh --email "$PACT_EMAIL" --access-account "${PACT_ACCESS_ACCOUNT:-$PACT_EMAIL}" --requester "$PACT_REQUESTER" --organization "$PACT_ORGANIZATION" --project "$PACT_PROJECT" --agent "Terminal" --use-case "Request production access to Subscription Market from a terminal" --where-seen "Terminal build guide" --source terminal
2. Resubmit access

Use this only if you need to send another request.

PACT_EMAIL="${PACT_EMAIL:?set PACT_EMAIL}" PACT_REQUESTER="${PACT_REQUESTER:?set PACT_REQUESTER}" PACT_ORGANIZATION="${PACT_ORGANIZATION:?set PACT_ORGANIZATION}" PACT_PROJECT="${PACT_PROJECT:?set PACT_PROJECT}" npx --yes --package https://pact.sh/packages/npm/subscription-market/pact-subscription-market-0.1.2.tgz pact-subscription-market request-access --api-url https://pact.sh --email "$PACT_EMAIL" --access-account "${PACT_ACCESS_ACCOUNT:-$PACT_EMAIL}" --requester "$PACT_REQUESTER" --organization "$PACT_ORGANIZATION" --project "$PACT_PROJECT" --agent "Terminal" --use-case "Request production access to Subscription Market from a terminal" --where-seen "Terminal build guide" --source terminal
Steps
  1. Run install with email and use case to verify both loggers.
  2. Use request-access directly only when you need to resubmit demand for the same install id.
  3. Check Vercel function logs or the configured webhook sink in production.
Logs
  1. events receive package_first_run.
  2. requests receive email, access account, requester, organization, project, agent, use case, where-seen, package, runtime, install id, and request context.
  3. Repeated requests reuse the install id but only create one first-run event.
Endpoints

The package talks to two API routes.

POST/api/events

Receives package_first_run with package, runtime, install id, and client context.

POST/api/requests

Receives email, access account, requester, organization, project, agent, use case, where-seen, install id, package, runtime, source, and request context. Install sends this automatically when those fields are present.

GET/subscription-market/agent

Agent-readable contract for the service page and integration flow.

Access

Request access