Loading AI Team page
Check whether public pages, setup intake, dashboard access, billing handoff, connected-tool handoffs, Agent workflows, and notifications are available or gated.
Current public status
Status data is published from the same source used by the machine-readable status API.
JSON status endpoint: /api/status
Public marketing, Agent catalog, pricing, trust, setup, legal, and content pages.
Public browsing and lead capture pages are expected to load normally.
Public Agent listing, category pages, Agent detail pages, and Agent Open Graph images.
Visitors can browse all public Agent pages and start setup review.
Synthetic monitoring
The public status snapshot lists the pages and endpoints that should be watched so setup, catalog, health, and API access failures are visible.
Homepage availability
Confirms buyers can reach the homepage, canonical deployment, and primary navigation.
Agent catalog availability
Confirms buyers and crawlers can reach the full public Agent catalog.
Incident log
Client-visible incidents should appear here and in the status API with affected services, severity, state, timing, mitigation, and next update.
No client-visible incident notice is currently published for the listed public systems.
Incident policy
Agents need explicit incident and degradation paths because connected systems, providers, cost caps, and approvals can fail independently.
Client-impacting incidents should identify affected service, affected organizations, start time, current state, next update, and mitigation.
Agent incidents can include provider failure, credential revocation, approval-rule conflict, spend-cap breach, workflow bug, or unexpected output.
Agents should pause or degrade safely when required credentials, providers, approval paths, or cost controls fail.
Related controls
A status page is credible only when incidents route back to controls that can pause, recover, or explain Agent work.
FAQ
These answers explain what the status page covers and how Agents should behave when something fails.
It reports public incidents and service notices for the website, Agent catalog, public JSON APIs, setup intake, dashboard, billing handoff, Agent workflows, and connected-tool handoffs.
Provider failures, revoked access, cost-cap breaches, approval-rule conflicts, unsafe output, workflow bugs, delayed processing, and client-visible dashboard errors can all become incidents.
Agents should pause, throttle, escalate, or degrade safely based on the approved stop rule instead of continuing uncontrolled work.
Machine-readable Agent, industry, integration, comparison, blog, and status endpoints for AI/search consumers.
Public API consumers can read allowlisted catalog, content, and status data.
Public setup review form and server-side setup-intake validation path.
Buyers can submit setup-review requests without sending secrets through public forms.
Public contact form for sales, support, security, investor, partnership, and catalog-fit inquiries.
Visitors can submit structured inquiries with same-origin and rate-limit controls.
Authenticated client dashboard shell for Agents, setup state, approvals, exceptions, reports, billing, and settings.
Client dashboard access requires configured authentication and organization membership.
Stripe checkout, customer portal, webhook, entitlement, and invoice handoff surfaces.
Payment handoff remains guarded by setup review and production Stripe configuration.
Live Agent work, approvals, exceptions, QA, monitoring, and operator handling.
Live Agent work requires completed setup, access review, QA, and operator approval.
Representative Agent detail
Confirms Agent detail pages, setup CTAs, and Agent schema remain available.
Setup form availability
Confirms buyers can reach setup intake without sending credentials through a public form.
Pricing page availability
Confirms buyers can review service bands, setup fees, pass-through cost rules, and setup-first payment expectations.
Contact form availability
Confirms buyers, partners, investors, and support contacts can reach the public inquiry route without sending secrets.
Support route availability
Confirms clients and buyers can find escalation expectations, non-secret evidence rules, and support routing during service issues.
AI search index availability
Confirms buyers, crawlers, AI assistants, analysts, and procurement teams can find AI Team canonical discovery files and public data routes.
Dashboard login entry
Confirms dashboard login remains reachable even while access is organization-gated.
Health endpoint
Confirms deployment health and runtime liveness.
Status API
Confirms the machine-readable public status snapshot is reachable.
Agents API
Confirms AI/search consumers can read the public Agent catalog API.
OpenAPI contract
Confirms the public machine-readable API contract remains available.
Monitoring should make errors, run IDs, cost events, alert routes, and incident steps visible to operators.