An eBay production keyset needs an account-deletion endpoint first

A new production keyset for eBay’s APIs is created disabled. It stays that way until the application either subscribes to marketplace account-deletion notifications or is granted an exemption, and that holds even for an application that only searches listings and stores nothing about users.

Subscribing means running a public HTTPS endpoint that does two things:

• answers a GET carrying a challenge code with a hash of the code, a verification token you chose, and the endpoint URL
• accepts POST notifications when an eBay user deletes their account

procurement is an MCP server with no other reason to accept inbound requests, so it grew a route at /ebay/notifications to satisfy this, exposed through an ingress limited to that one path.

Sold-listing prices are a separate matter. The Browse API returns current listings only, so sold prices come from a scraping actor, which needs a much longer timeout than the API calls because of its cold start.