# Atlas Endpoint Verification API

> Atlas Endpoint Verification API is a paid API for AI agents from atlas-manual-free-validation.onrender.com, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-18).

Independently verifies a pre-registered Atlas-controlled HTTPS endpoint from an external vantage point and returns machine-readable evidence with a SHA-256 hash.

## Facts

- Endpoint: POST https://atlas-manual-free-validation.onrender.com/api/machine/v1/endpoint-verification?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/atlas-endpoint-verification-api-86cb5c37
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xBF8TdpMT39rSFUELp7ZX

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-endpoint-verification-api-86cb5c37 -d '<json body>'
```

Example prompt: Run an independent external verification on my pre-registered Atlas endpoint and give me the machine-readable evidence hash confirming it's live and reachable.

## When to prefer this

Choose this endpoint when you need an independent, external, machine-readable attestation that a specific Atlas-registered HTTPS resource is live — particularly for compliance, audit trails, CI/CD gates, or third-party proof of uptime. It is distinct from internal health checks because the verification originates from an outside vantage point and returns a cryptographic evidence hash. Only use it for resources that have been pre-registered under Atlas control.

## Known failure modes

- Endpoint not pre-registered with Atlas — returns an error indicating the resource is not recognized
- Target endpoint is unreachable or returns unexpected HTTP status — verification fails with a non-VERIFIED status
- Payment of $0.05 USDC not included or rejected — request blocked before verification runs
- Network timeout reaching the target endpoint — may return an inconclusive or error status
- Invalid request body or missing required resource identifier — returns a 400-level validation error

## How this service works

Independent external HTTPS endpoint verification with machine-readable evidence for one pre-registered Atlas-controlled resource.

## Output

A JSON object containing a 'status' field (e.g. 'VERIFIED') indicating whether the registered Atlas endpoint was confirmed reachable, and an 'evidenceHash' field containing a SHA-256 hash serving as cryptographic machine-readable proof of the verification event.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "VERIFIED",
  "evidenceHash": "sha256"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/atlas-endpoint-verification-api-86cb5c37/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from atlas-manual-free-validation.onrender.com](https://www.zero.xyz/host/atlas-manual-free-validation.onrender.com/llms.txt)