[codex] Add agent marketplace authority safeguards

[Rumblingb]

What changed

• Added an agent-only requirement chooser that compares MCP registry servers, agent matches, and governed capability providers.
• Exposed registry discovery and the chooser on the read-only MCP surface.
• Made paid registry subscriptions fail closed: paid subscriptions now remain pending_payment until Stripe webhook confirmation.
• Added a paid registry checkout endpoint and Stripe webhook activation path.
• Added scoped repo authority request/lease routes and MCP tools without exposing raw provider tokens.
• Changed registry payouts to 80% publisher / 20% AgentPay.
• Fixed API-edge regressions in health checks, cheap/local model routing, and concierge dispatch recovery handling.
• Added the agent-led business opening Phase 1 plan for SMB/proprietor onboarding above Stripe and partner rails.
• Added Pickaxe MCP to the marketplace seed as pickaxe-agent-admin, with credential-connect metadata for the Pickaxe Studio API key.
• Expanded the marketplace seed to include the missing callable Rumblingb MCP servers from GitHub: email finder, content toolkit/moderation, legal counsel, SEC EDGAR, company intel, Wikipedia, agent memory, cost tracking, README generation, and Sentinel.
• Fixed the dashboard CI lockfile mismatch by syncing dashboard/package-lock.json back to next@16.1.6 / eslint-config-next@16.1.6 from dashboard/package.json.
• Updated MCP registry metadata and docs to describe the marketplace/authority tools.

Why

AgentPay should operate as the agent capability marketplace and authority control plane. Agents can browse and choose capabilities; humans are interrupted only for payment, repo selection, credential connection, regulated document submission, or policy exceptions.

The next mainstream expansion is not competing with Stripe or becoming a bank first. It is letting agents safely prepare and route business opening workflows through Stripe, bank, formation, KYB, and insurance partners.

Safety notes

• Paid MCP subscriptions do not become active from registry_subscribe; they require confirmed Stripe webhook settlement.
• Per-call billing fails closed until metering and spend limits are enforced.
• Repo authority leases are scoped authority records only. They do not store or return GitHub/GitLab tokens.
• Dispatch failures and retry-pending states now surface as recovery states instead of appearing healthy while money has already moved.
• Business opening is scoped as partner-routed, non-custodial orchestration: no legal/tax/banking/insurance execution without explicit human approval.
• Pickaxe requires human credential connection; agents get env placeholders/config, not raw Pickaxe API keys.

Validation

• npm --workspace @agentpay/api-edge test — 56 passed
• npm --workspace @agentpay/api-edge run typecheck
• npm --workspace @agentpayxyz/mcp-server run typecheck
• cd dashboard && npm ci
• cd dashboard && npm run build
• npx tsc --noEmit --skipLibCheck --allowSyntheticDefaultImports --moduleResolution node --module esnext --target es2022 scripts/seed-registry.ts
• node -e "JSON.parse(require('fs').readFileSync('server.json','utf8')); console.log('server.json ok')"
• git diff --check

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
agentpay-dashboard	Ready	Preview, Comment	May 21, 2026 6:48pm
agentpay-docs	Ready	Preview, Comment	May 21, 2026 6:48pm
agentpay-host-native-restore	Ready	Preview, Comment	May 21, 2026 6:48pm