# 100BTC Oracle - API Endpoint Reachability Checker

> 100BTC Oracle - API Endpoint Reachability Checker is a paid API for AI agents from vps-fc89c157-1.taila28d02.ts.net:10000, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-02).

Checks whether a given URL endpoint is reachable, active, and suitable to call by testing it live and returning reliability metrics

## Facts

- Endpoint: POST https://vps-fc89c157-1.taila28d02.ts.net:10000/api/oracle?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/100btc-oracle-api-endpoint-reachability-checker-e970207d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4JtDcu05boNlcmSo_0j9T

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 100btc-oracle-api-endpoint-reachability-checker-e970207d -d '<json body>'
```

Example prompt: Before I pay to call it, can you check whether https://vps-fc89c157-1.taila28d02.ts.net:10000/api/someservice is actually reachable right now using a GET request — and tell me its latency and whether you'd recommend using it?

## When to prefer this

Use this endpoint when you need a live, real-time probe of whether a specific URL is responding before committing resources or payments to calling it. Particularly valuable before invoking x402 pay-per-call APIs where a failed call still costs money. Prefer this over passive uptime monitors when you need an on-demand decision ('USE' vs 'AVOID') with latency data at the moment of routing.

## Known failure modes

- Target URL is unreachable or times out — returns reachable: false with error context
- Invalid or malformed target_url input — likely 4xx validation error
- Target returns unexpected non-standard status code — still reported but may lower reliability score
- Network-level errors from the oracle server itself — service unavailability

## How this service works

Thirty x402 v2 pay-per-call APIs by 100BTC. Listing data is generated from each live HTTP 402 challenge and runtime Bazaar schema.

## Output

Returns a JSON object with a 'decision' field (e.g. 'USE' or 'AVOID'), a 'reliability_score' (0-100), 'metrics' containing reachability boolean, HTTP status code, latency in milliseconds, and check timestamp, plus a human-readable 'reasons' array explaining the assessment.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "method": {
   "enum": [
    "GET",
    "POST",
    "HEAD"
   ],
   "type": "string"
  },
  "target_url": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "metrics": {
   "reachable": true,
   "checked_at": 1790528000,
   "latency_ms": 245.5,
   "status_code": 402
  },
  "reasons": [
   "Endpoint active, responded with status 402",
   "Fast response time: 245ms"
  ],
  "decision": "USE",
  "reliability_score": 90
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/100btc-oracle-api-endpoint-reachability-checker-e970207d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from vps-fc89c157-1.taila28d02.ts.net:10000](https://www.zero.xyz/host/vps-fc89c157-1.taila28d02.ts.net%3A10000/llms.txt)