# Atlas Research x402 Endpoint Inspector

> Atlas Research x402 Endpoint Inspector is a paid API for AI agents from atlasresearch2026.pythonanywhere.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-11-18).

Inspects an x402-enabled HTTPS URL to retrieve its payment requirements, protocol version, and accepted payment methods without executing payment.

## Facts

- Endpoint: GET https://atlasresearch2026.pythonanywhere.com/api/x402-check?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/atlas-research-x402-endpoint-inspector-51e615ed
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mfmY-97587VmlsaxmCXNo

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 atlas-research-x402-endpoint-inspector-51e615ed
```

Example prompt: Can you inspect the x402 payment configuration at https://atlasresearch2026.pythonanywhere.com/api/gold and tell me what protocol version it uses and how many payment methods it accepts?

## When to prefer this

Use this endpoint when you need to programmatically inspect or validate the x402 payment configuration of any HTTPS URL before attempting payment or integration. Prefer this over manually parsing HTTP 402 responses when you need structured metadata about protocol version and accepted payment methods in a single call.

## Known failure modes

- Target URL is not x402-enabled — returns non-402 HTTP status with empty accepts_count
- Target URL is unreachable or times out — connection error returned in errors array
- Malformed or non-HTTPS URL provided — validation error before probe attempt
- Target endpoint has misconfigured x402 headers — errors array populated with protocol issues
- Missing url parameter — API returns 400 or similar input validation error

## How this service works

Atlas Research: a sourced European gold market snapshot, payable per call with 0.001 USDC on Base via x402, plus the Ring Rush game.

## Output

Returns a JSON object containing the target URL, HTTP status code (expected 402), x402 protocol version number, count of accepted payment methods, and an array of any validation errors encountered during the probe.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "description": "HTTPS URL of the x402 endpoint to inspect"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "errors": [],
  "target": "https://example.com/api/paid",
  "http_status": 402,
  "x402_version": 2,
  "accepts_count": 1
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/atlas-research-x402-endpoint-inspector-51e615ed/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from atlasresearch2026.pythonanywhere.com](https://www.zero.xyz/host/atlasresearch2026.pythonanywhere.com/llms.txt)
