# Geo Ops Context

> Geo Ops Context is a paid API for AI agents from k2so.wrong.systems, paid per call via x402, $0.005/call, status down (last checked 2026-09-15).

Geocodes a place name and returns local time, UTC offset, current weather, and an ops-suitability note to help agents coordinate human-dependent work across timezones.

## Facts

- Endpoint: GET https://k2so.wrong.systems/api/services/geo-ops-context
- Price: $0.005/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/geo-ops-context-10ae97e3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_s8ytAy7KjVkGiJxA46ZAh

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 geo-ops-context-10ae97e3
```

Example prompt: What's the local time, UTC offset, and current weather in Nairobi right now, and is it operationally suitable for scheduling a task with a human worker there?

## When to prefer this

Choose this endpoint when an agent needs a combined geo-context snapshot — local time, timezone offset, current weather, and operational suitability — for a named place, especially when coordinating tasks that depend on human availability or outdoor conditions across timezones. Prefer this over separate geocoding or weather APIs when you need all three signals in a single call with an agent-friendly ops-suitability interpretation.

## Known failure modes

- Unrecognized or ambiguous place name returns an error or low-confidence geocode result
- Geocoding succeeds but weather service is unavailable, resulting in partial data
- Network timeout from upstream geocoding or weather provider
- Malformed query parameter causes 400-level error
- Location is too remote for weather data coverage

## How this service works

Geocode a place and return local time, UTC offset, current weather, and an ops-suitability note - context for an agent coordinating human-dependent work across timezones.

## Output

Returns a structured payload containing geocoded location data, local time, UTC offset, current weather conditions, and an ops-suitability assessment note indicating whether the time and conditions are appropriate for coordinating human-dependent work at that location.

## 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",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "meta": {
       "enum": [
        "0",
        "1"
       ],
       "type": "string",
       "description": "Set to 1 for free metadata JSON (no payment required)"
      },
      "place": {
       "type": "string",
       "description": "Composite input parameter"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "title": "Geo Ops Context paid response",
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "required": [
      "ok",
      "paid",
      "service",
      "provider",
      "result"
     ],
     "properties": {
      "ok": {
       "type": "boolean"
      },
      "paid": {
       "type": "boolean"
      },
      "result": {
       "type": "object",
       "required": [
        "ok",
        "service"
       ],
       "properties": {
        "ok": {
         "type": "boolean",
         "description": "Handler success"
        },
        "score": {
         "type": "number"
        },
        "service": {
         "type": "string",
         "description": "Service slug"
        },
        "summary": {
         "type": "string"
        },
        "evidence": {
         "type": "object"
        },
        "strengths": {
         "type": "array",
         "items": {
          "type": "string"
         }
        },
        "confidence": {
         "type": "string"
        },
        "generatedAt": {
         "type": "string",
         "description": "ISO-8601 timestamp"
        },
        "riskFactors": {
         "type": "array",
         "items": {
          "type": "string"
         }
        }
       }
      },
      "payment": {
       "type": "object",
       "properties": {
        "code": {
         "type": "string"
        },
        "payer": {
         "type": "string"
        },
        "detail": {
         "type": "string"
        },
        "selfPay": {
         "type
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "paid": true,
  "result": {
   "ok": true,
   "service": "geo-ops-context"
  },
  "service": "geo-ops-context",
  "provider": "K-2SO"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/geo-ops-context-10ae97e3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from k2so.wrong.systems](https://www.zero.xyz/host/k2so.wrong.systems/llms.txt)