Custom Agents. Not finding the agent you need? Have one built for your business, and it is not finished until it passes the cases you wrote.

Everything that is watched is answering.

Both of the checks below that actually try something succeeded just now. The rest of the page says plainly what is only configured and what nothing watches at all.

Current checks

  • Storefront

    Answering

    Observed

    The server rendered this page, from the same deployment every other public page is served from.

    Scope
    The public pages of this site: the applications for sale, the Tools catalogue, Custom Agents, and everything under Company.
    Source
    This page, rendered by the server that serves those pages.
    Checked
  • Tools Catalogue

    Answering

    Observed

    The catalogue endpoint answered this request. That is the catalogue responding, not a hosted agent running.

    Scope
    Whether the hosted Tools platform's public catalogue endpoint answers this storefront. Not whether an agent runs.
    Source
    A request made by this server while rendering this page.
    Checked
  • Tool Execution

    Not Measured

    No Telemetry

    Nothing measures this. No Tool is published for sale yet, so there is also nothing running to measure.

    Scope
    Whether a hosted agent completes work for a paying workspace, and how often it fails.
    Source
    No monitoring vendor is connected to this application or to the Tools platform.
    Checked
  • Accounts and Sign-In

    Configured

    Configuration Only

    A configuration reading. It says this deployment holds what it needs to sign somebody in, not that a sign-in succeeded.

    Scope
    Whether this deployment holds a database connection and a session secret. Storefront accounts only — the Tools platform runs a separate identity realm with its own sign-in.
    Source
    Configuration read by this deployment while rendering.
    Checked
  • Acquisition Inquiry and Email

    Configured

    Configuration Only

    A configuration reading. Delivery to an inbox is between the mail provider and the recipient, and is not measured here.

    Scope
    Whether this deployment can send the mail an acquisition inquiry, a contact message or an account email depends on.
    Source
    Configuration read by this deployment while rendering.
    Checked
  • Payments

    Configured

    Configuration Only

    A configuration reading. It names no provider state, no settlement, and no transaction.

    Scope
    Whether a payment provider is configured for this deployment. Acquiring an application begins as an inquiry and never passes through checkout.
    Source
    Configuration read by this deployment while rendering.
    Checked

What the three readings mean.

Observed
Something was asked and answered at the time shown.
Configuration Only
This deployment holds what it needs to reach the service. It was not asked.
No Telemetry
Nothing watches this, so the row makes no claim about it.

What this page cannot tell you.

There is no uptime figure and no incident history, because nothing retains an observation over time. Every reading above was taken while this page rendered and will not exist a second from now. A percentage printed against that would be a number rather than a measurement.

This page is served by the deployment it reports on, which is the one thing it cannot be objective about: if that deployment is down you are not reading this at all. Treat the storefront row as a positive signal when you can see it, never as a negative one when you cannot.

A problem inside a product integration does not mean the storefront is down. The applications for sale, their prices and the way to ask about one are static pages that depend on none of the services below them.

What is weak, and what is verified