openstatus.dev valid
Argos Status
Operational status. Agent-readable markdown, JSON, and feeds are linked below.
For agents: Argos Status public status page offering component status, incident history, and JSON/RSS/Atom feeds; Statuspage-compatible summary endpoint for 'is it up?' che
status-pageuptime-monitoringincident-historystatuspage-compatiblerss-feed
- Authority
- 56 reach 10 · trust 10 · quality 21 · freshness 15
- Tier
- listed
- llms.txt
- https://argos.openstatus.dev/llms.txt
- Sections
- 4
- Links
- 11
- Size
- 1063 bytes
- Popularity rank
- #256404
- Registered
- 2023-06-17
- Country
- United States Hosting inference
- Hosting country
- United States Hosting inference
- Country evidence
- No published address evidence collected yet
- Categories
- DevOps and observability
- For agents
- Interface: a documented API or declared MCP endpoint an agent can call
- Inferred actions
- Read documentation Call an API Search content About these labels
- Audience
- mixed · agents can: read docs, call api, search content · en
- First seen
- 2026-10-19T10:41:02.084Z
- Last checked
- 2026-10-27T15:55:40.531Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-26T16:55:26.849Z. Cached copy · Source on openstatus.dev
# Argos Status
> Operational status. Agent-readable markdown, JSON, and feeds are linked below.
## Status
- [Overview](https://argos.openstatus.dev/.md): overall status, components, active incidents
- [Monitors](https://argos.openstatus.dev/monitors.md): per-service status
- [Events](https://argos.openstatus.dev/events.md): incident & maintenance history
## Monitors
- [API](https://argos.openstatus.dev/monitors/1401.md)
- [Screenshot diffs](https://argos.openstatus.dev/monitors/2397.md)
## Data
- [summary.json](https://argos.openstatus.dev/api/status/summary.json): machine summary, Statuspage-compatible
- [current.json](https://argos.openstatus.dev/api/status/current.json): single overall indicator — cheapest "is it up?"
- [Unresolved incidents](https://argos.openstatus.dev/api/status/incidents.json)
- [RSS](https://argos.openstatus.dev/feed/rss) · [Atom](https://argos.openstatus.dev/feed/atom) · [JSON feed](https://argos.openstatus.dev/feed/json)
## Notes
- Any page URL also serves markdown via a `.md` suffix or `Accept: text/markdown`.
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| cloudflarestatus.com | Cloudflare Status | interface DevOps and observability Infrastructure | US | 61 | ✓ | ||
| outagedeck.com | OutageDeck | interface AI and machine learning DevOps and observability +1 | US | 46 | ✓ | ✓ | |
| instatus.com | Instatus | documentation DevOps and observability | US | 63 | ✓ | ✓ | |
| incidenthub.cloud | IncidentHub | documentation DevOps and observability | US | 52 | ✓ | ||
| statusgator.com | StatusGator | interface DevOps and observability | — | 58 | ✓ | ||
| statoss.com | StatOSS | interface DevOps and observability | — | 45 | ✓ | ✓ | |
| outage.com | Outage.com - Real-Time Service Status Monitoring | informational DevOps and observability | US | 45 | ✓ | ✓ | |
| uptimepage.dev | Uptimepage | documentation DevOps and observability | CY | 45 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=openstatus.dev · GET /v1/domain/openstatus.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage openstatus.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for openstatus.dev:
1. POST https://agentwebmap.com/v1/sites/openstatus.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://openstatus.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/openstatus.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/openstatus.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.