Official service status for agents

Check the services your agent depends on before blaming your own code.

When a run fails, the boring question matters first: is GitHub, npm, Cloudflare, Supabase, OpenAI, Anthropic, or the deploy platform having an incident? These x402 checks read the official public status sources and return a small JSON answer an agent can use immediately.

Open catalog Base x402 discovery Solana Pay.sh gateway

What comes back

A quick answer, source details, and a receipt for the paid call.

The response includes the normalized status, official source URL, cache state, component counts, current incidents or scheduled maintenance when available, and a recommendation. Paid responses also include a signed receipt with the request id, route, price, settlement hash, and response SHA-256.

$0.001for a single service status check

$0.005for deploy-readiness or balanced stack bundles

14official status sources in the first catalog

Base + Solanadirect x402 on Base, Pay.sh gateway on Solana

Supported services

The first set covers the failures builders hit most often.

I picked services that tend to sit in the middle of a broken deploy or broken agent run: source control, package installs, hosting, edge, database/auth, and model APIs.

openai

OpenAI

Direct endpoint: /api/status/openai

anthropic

Anthropic

Direct endpoint: /api/status/anthropic

github

GitHub

Direct endpoint: /api/status/github

gitlab

GitLab

Direct endpoint: /api/status/gitlab

npm

Direct endpoint: /api/status/npm

vercel

Vercel

Direct endpoint: /api/status/vercel

netlify

Netlify

Direct endpoint: /api/status/netlify

render

Render

Direct endpoint: /api/status/render

fly

Fly.io

Direct endpoint: /api/status/fly

cloudflare

Cloudflare

Direct endpoint: /api/status/cloudflare

supabase

Supabase

Direct endpoint: /api/status/supabase

convex

Convex

Direct endpoint: /api/status/convex

clerk

Clerk

Direct endpoint: /api/status/clerk

bitbucket

Bitbucket

Direct endpoint: /api/status/bitbucket

Bundle

Use the bundle when an agent is about to retry a deploy.

The vibe-deploy-readiness bundle checks GitHub, GitLab, npm, Vercel, Cloudflare, Supabase, and OpenAI in one paid call. Use the direct CrowdPull endpoint for Base USDC, or the Pay.sh endpoint when the agent is already spending Solana USDC.

# Base USDC direct x402
curl -i -X POST "https://agentic.crowdpull.click/api/status/bundle" \
  -H "content-type: application/json" \
  -H "x-payment: $X402_PAYMENT" \
  --data '{"bundle":"vibe-deploy-readiness","includeComponents":false}'

# Solana USDC through Pay.sh
curl -i -X POST "https://pay.crowdpull.click/api/status/bundle" \
  -H "content-type: application/json" \
  --data '{"bundle":"vibe-deploy-readiness","includeComponents":false}'

Custom stacks

Pick the services in the stack, but keep it honest.

The discounted stack route is for a real app stack: source control, packages, deploy host, edge, data layer, auth, and model API. If the selection repeats a capped layer, such as several database services, it still belongs in the regular bundle route. The API returns that classification instead of pretending every group of services is a full stack.

# Balanced stack bundle on Base USDC
curl -i -X POST "https://agentic.crowdpull.click/api/status/stack" \
  -H "content-type: application/json" \
  -H "x-payment: $X402_PAYMENT" \
  --data '{"services":["github","npm","vercel","supabase","openai"],"includeComponents":false}'

# Category bundle, not stack pricing
curl -i -X POST "https://agentic.crowdpull.click/api/status/bundle" \
  -H "content-type: application/json" \
  -H "x-payment: $X402_PAYMENT" \
  --data '{"services":["supabase","convex","clerk"],"includeComponents":false}'

Catalog

Start free, pay only when the agent needs the status answer.

The catalog is public. It lists service ids, endpoints, source pages, bundle definitions, and the free suggestion route. The same paid status products are exposed through the direct Base endpoint and the Pay.sh Solana gateway so agents can use whichever rail they already have funded.

curl -s "https://agentic.crowdpull.click/api/status/catalog"

Missing coverage

Let agents tell us what they needed but could not find.

If a service is not in the first catalog, agents can submit the official homepage, status page, or machine-readable status API. Covered services return the existing endpoint instead of cluttering the queue. New suggestions go into the private review dashboard so we can add the services people are actually asking for.

curl -i -X POST "https://agentic.crowdpull.click/api/status/suggest" \
  -H "content-type: application/json" \
  --data '{"name":"Railway","homepage":"https://railway.app","statusPage":"https://status.railway.app","category":"deploy","priority":"high"}'