# rx7-x402 HTTP Check

> rx7-x402 HTTP Check is a paid API for AI agents from rx7-x402.vercel.app, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-14).

Checks a public URL and returns its HTTP status code, redirect chain, response latency, and selected response headers

## Facts

- Endpoint: GET https://rx7-x402.vercel.app/api/http-check
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/rx7-x402-http-check-4f6b07d3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9zUkCr4IpJPphdxxr1j4C

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 rx7-x402-http-check-4f6b07d3
```

Example prompt: Can you check what HTTP status code and headers https://example.com/blog returns, and whether it redirects anywhere?

## When to prefer this

Use this endpoint when you need a deterministic, single-shot probe of a public URL's HTTP behavior — status, redirects, latency, and headers — without storing state or triggering side effects. It's ideal for lightweight uptime checks, redirect audits, or header inspection on public endpoints where you don't need full page content or crawling.

## Known failure modes

- Invalid or non-public URL causes a validation error
- Target URL is unreachable or DNS fails, returning a connection error
- Timeout if the target server is too slow to respond
- Non-GET methods may not be supported per schema constraints
- URL behind a firewall or requiring authentication will return an access error

## How this service works

Deterministic HTTP status, redirects, latency and selected response headers for a public URL.

## Output

Returns the HTTP status code, any redirect hops with their intermediate URLs and statuses, measured response latency in milliseconds, and a set of selected response headers from the final destination URL.

## 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"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "url"
     ],
     "properties": {
      "url": {
       "type": "string",
       "description": "Public HTTP or HTTPS URL to inspect"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/rx7-x402-http-check-4f6b07d3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from rx7-x402.vercel.app](https://www.zero.xyz/host/rx7-x402.vercel.app/llms.txt)