# Vextorium Provider Status

> Vextorium Provider Status is a paid API for AI agents from api.vextorium.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-11).

Returns live operational status, open incidents, and scheduled maintenance for major cloud services and APIs (GitHub, OpenAI, Cloudflare, Twilio, Discord, etc.)

## Facts

- Endpoint: POST https://api.vextorium.com/v1/provider-status?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vextorium-provider-status-c24f225b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pJDWcVTikU5RSrUH9TWEu

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability vextorium-provider-status-c24f225b -d '<json body>'
```

Example prompt: Check the live status of OpenAI and Cloudflare — are they fully operational, and are there any open incidents or maintenance windows affecting them right now?

## When to prefer this

Use this endpoint when you need real-time aggregated status across multiple well-known cloud APIs and developer tools without scraping individual status pages. It is ideal for automated incident triage, on-call alerting pipelines, and health dashboards covering GitHub, OpenAI, Anthropic, Cloudflare, Twilio, Discord, Vercel, npm, DigitalOcean, Coinbase, Atlassian, Netlify, and Supabase. Prefer this over building your own status-page scrapers when you need a single unified call.

## Known failure modes

- Provider status page unreachable — may return null or stale data for that provider
- Invalid provider name returns empty or error response
- Rate limiting or payment failure (x402) if USDC balance insufficient
- Truncated response if too many providers have active incidents

## How this service works

Live status of widely used cloud services and APIs (GitHub, Cloudflare, OpenAI, Anthropic, Discord, Vercel, npm, Twilio, DigitalOcean, Coinbase, Atlassian, Netlify, Supabase) from their status pages: overall state, affected components, open incidents and ongoing maintenance.

## Output

A JSON object containing for each queried provider: their overall status string (e.g. 'operational', 'minor', 'major'), a human-readable description, a link to their status page, a list of open incidents (with title, impact level, start time, current status, and latest update), a list of scheduled maintenances, and affected components. Also includes a top-level list of providers currently with issues and a boolean 'all_operational' flag.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "required": [],
     "properties": {
      "provider": {
       "type": "string",
       "description": "e.g. GitHub (omit for all)"
      }
     }
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": [
      "object",
      "null"
     ],
     "properties": {
      "source": {
       "type": [
        "string",
        "null"
       ]
      },
      "providers": {
       "type": [
        "array",
        "null"
       ],
       "items": {
        "type": [
         "null",
         "object"
        ],
        "properties": {
         "page": {
          "type": [
           "null",
           "string"
          ]
         },
         "status": {
          "type": [
           "null",
           "string"
          ]
         },
         "provider": {
          "type": [
           "null",
           "string"
          ]
         },
         "incidents": {
          "type": [
           "array",
           "null"
          ],
          "items": {
           "type": [
            "null",
            "object"
           ],
           "properties": {
            "start": {
             "type": [
              "null",
              "string"
             ]
            },
            "title": {
             "type": [
              "null",
              "string"
             ]
            },
            "impact": {
             "type": [
              "null",
              "string"
             ]
            },
            "status": {
             "type": [
              "null",
              "string"
             ]
            },
            "last_update": {
             "type": [
              "null",
              "string"
             ]
            }
           }
          }
         },
         "description": {
          "type": [
           "null",
           "string"
       
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "source": "Each provider's public status page (Atlassian Statuspage)",
  "providers": [
   {
    "page": "https://www.cloudflarestatus.com",
    "status": "minor",
    "provider": "Cloudflare",
    "incidents": [
     {
      "start": "2026-09-22T19:23:17.000Z",
      "title": "Cloudflare One Clients are incorrectly challenged on some sites",
      "impact": "minor",
      "status": "identified",
      "last_update": "The issue has been identified and a fix is being implemented."
     },
     {
      "start": "2026-08-27T18:46:19.000Z",
      "title": "Incorrect geo location for some Cloudflare WARP users",
      "impact": "minor",
      "status": "identified",
      "last_update": "We are continuing to work on a fix for this issue."
     }
    ],
    "description": "Minor Service Outage",
    "maintenances": [],
    "affected_components": [
     "Arica, Chile - (ARI)",
     "Baghdad, Iraq - (BGW)"
    ]
   },
   {
    "page": "https://status.twilio.com",
    "status": "minor",
    "provider": "Twilio",
    "incidents": [
     {
      "start": "2026-09-04T02:43:59.602-07:00",
      "title": "MMS Delivery Failures From A Subset Of Network Subscribers In Australia To Twilio Australia Phone Numbers.",
      "impact": "minor",
      "status": "investigating",
      "last_update": "Twilio customers may be experiencing MMS delivery failures from a subset of network subscribers in Australia to a subset of Twilio Australia Phone Numbers. Our team is actively investigating this issue. We will provide another update in 24 hours or as soon as more information becomes available."
     },
     {
      "start": "2026-10-02T14:48:10.661-07:00",
      "title": "SMS Delivery Delays and Failures from Twilio to Hi3G Italy",
      "impact": "minor",
      "status": "identified",
      "last_update": "Twilio customers may be experiencing SMS delivery delays and failures from Twilio to Hi3G network subscribers in Italy. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available."
     }
    ],
    "description": "Partially Degraded Service",
    "maintenances": [],
    "affected_components": [
     "MMS Long Code, North America",
     "Bulk Export"
    ]
   }
  ],
  "with_issues": [
   "Cloudflare",
   "Twilio"
  ],
  "all_operational": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vextorium-provider-status-c24f225b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.vextorium.com](https://www.zero.xyz/host/api.vextorium.com/llms.txt)