Make your service legible to agents.

The initial visible manifest shows provider your service and an empty service array. However, the internal default download is a different demo object containing one service. Bars compare zero initially displayed services with one default exported demo service at two hundred pixels per count. This source interface difference is important: a downloaded example is not proof a provider URL was fetched or validated. The page has made no live request until Validate URL is clicked. For one service, the source checks three top-level conditions, provider, network and a nonempty services array, plus four service fields: id, endpoint, price and currency. Bars compare three top-level checks with four service fields at one hundred pixels per count. Presence mostly uses truthiness. A numeric zero price fails while the string zero passes; nonempty invalid endpoint and currency text also pass. This is source field checking, not a formal protocol audit, price validation, payment, service invocation or authenticity guarantee. An HTTP, JSON or fetch failure makes the source render and save the demo object with one service, then show a failure message. Bars compare one failed request with one synthetic demo service at two hundred pixels per count. Reload validates that saved demo and can show Pass, even though it is not the requested provider response. Download remains available for failed-validation data too. The tests use an actual isolated local HTTP fixture with browser permission, not provider evidence. No model, agent service or payment is executed.