GeoProxy

One-Line Pitch

A routing API that lets you fetch any URL as if you were physically located in the UK, US, Germany, Japan, or Australia — your location stops being a wall.

The Problem

Websites lock access by geography. A service you need is available in Germany but not where you are. An API behaves differently depending on which country the request comes from. A content platform blocks your server's IP range. Your feet are in the wrong place, and the internet has decided that matters.

GeoProxy removes that constraint.

What It Does

Send GeoProxy a URL and a target country. It routes the request through a VPN endpoint in that country and returns exactly what a user sitting there would receive. No metadata overhead unless you want it.

# Fetch github.com as if you're in the UK
curl "http://104.248.168.149:8080/api/v1/proxy?url=https://api.github.com&country=uk" \
  -H "Authorization: Bearer YOUR_KEY"

The response is raw content — HTML, JSON, images — exactly as it would arrive from that location.

Two Modes

Mode	Endpoint	Use When
Transparent proxy	`GET /api/v1/proxy`	You want the raw content, nothing else. Drop-in replacement for a direct HTTP request.
Full metadata fetch	`POST /api/v1/fetch`	You want the content plus geographic confirmation, headers, timing, and an optional verifiable timestamp receipt.

Regions

Five regions configured. UK (London) active now. US, Germany, Japan, Australia ready to bring online.

# Check which regions are healthy right now
curl http://104.248.168.149:8080/health

Who It's For

Use Case	Why GeoProxy
Developers testing geo-restricted APIs	See exactly what a user in that country sees
AI agents that need to browse the open web	Route requests through any region without managing VPN infrastructure
Services building geo-aware features	Test your own geo-detection and regional behaviour
Anyone locked out by IP range	Your location is not a valid reason to be denied access to public information

The Extras

The full metadata mode wraps every response in a Kronos temporal proof — a cryptographic timestamp proving exactly when the request was made and what came back. That capability connects to a bigger principle (Zero Darkness→), but it's the extra thing here, not the main thing.

The main thing is: you asked for a page from London, you got what London sees.

What Exists Now

Live and operational. Single region (UK). Production API with authentication, rate limiting, and a policy analysis engine that flags domains with ToS restrictions on proxy usage.

GET /api/v1/proxy — transparent proxy
POST /api/v1/fetch — full metadata + Kronos receipt
GET /health — region status
GET /api/v1/regions — available regions

Next Step to Explore

Activating the remaining four regions. US in particular unlocks a large set of geo-restricted content that currently only the UK endpoint touches. The infrastructure is already configured.

Connections

Zero Darkness→ — the Kronos principle behind the verifiable receipt feature
Fort Knox→ — another Kronos service using the same chain for financial ledger integrity

The Technical Moat

The temporal proof system is built on the same Kronos chain used across all Kronos services:

T1 = nanoseconds before request sent
T2 = nanoseconds after reply received
Kronos_hash = SHA256(H_previous || T1_bytes || T2_bytes)

The window T1→T2 is unique in all of history. We've never been at those exact nanoseconds before, for the same request, in the same chain. At nanosecond precision, even a 50ms window contains 2.5 × 10¹⁵ possible (T1, T2) pairs. That's the search space a forger faces — for each link in the chain.

The chain grows faster than any computer can search it. This is not probabilistic. It's structural.

What It Is Right Now

GeoProxy is live and running. Single region (UK). Five regions configured and ready to activate.

POST /api/v1/fetch — full metadata + Kronos receipt
GET /api/v1/proxy — transparent proxy, raw content
GET /health — region status and VPN health

It's quietly operational. Nobody knows it exists yet. The pitch has never been written in a way that leads with what makes it genuinely different.

The differentiator is the receipt, not the routing.

Any proxy routes traffic. GeoProxy is the only one that produces cryptographic proof of what was fetched, where, and when — proof that cannot be constructed after the fact.

Next Step to Explore

The interesting commercial question: who needs provable data access?

Legal teams collecting evidence. AI safety researchers proving training data provenance. Financial institutions with geographic compliance requirements. Journalists documenting what was publicly available at a specific time.

The receipt turns a commodity service (geographic routing) into a compliance and evidence tool. That's the version worth building toward.

Connections

Zero Darkness→ — the Kronos principle this is built on: security through radical visibility of failure
Electrogravitics Receipts→ — another system built around the idea that receipts are the product
Fort Knox→ — another Kronos service where every transaction produces an unbreakable ledger entry