Vol. 1 — Public Beta — Integrated Micro HTTP Core
API Infrastructure — Edge Routing

Built for
the speed
of now.

Lightweight HTTP infrastructure that routes, transforms, and monitors your API traffic globally — with zero configuration overhead.

Read docs
By the numbers
<12ms
Average global latency across all edge regions
99.97%
Uptime SLA, backed by 18 redundant PoPs
2.4B+
Requests served monthly across all customers
01
Edge routing
Traffic is automatically directed to the nearest PoP, cutting round-trip latency by up to 60%.
02
Auth & rate limits
API key management, JWT validation, and per-endpoint rate limiting. No SDK required.
03
Live observability
Request logs, latency histograms, and error tracking stream in real time with zero instrumentation.
04
Webhook delivery
Guaranteed fan-out with automatic retries, dead-letter queues, and signed delivery receipts.
05
Transform layer
Modify request and response payloads in-flight using a declarative rule engine.
06
Global network
18 edge nodes across Asia, Europe, and North America. Traffic always exits near your users.
Quickstart — first request
# authenticate and send your first request
curl https://api.imhc.win/v1/route \
  -H "Authorization: Bearer $IMHC_KEY" \
  -d '{"target":"https://svc.example.com","ttl":30}'

→ {"status":"routed","latency_ms":9,"edge":"fra-01"}
"Ship your API in minutes, not days. Infrastructure should never be the bottleneck."
— IMHC Engineering Team
Documentation
Everything you need to integrate

Introduction

IMHC is a lightweight HTTP routing and transformation layer designed for teams that need global API infrastructure without the operational overhead. All requests are routed through our edge network, processed in under 12ms on average, and delivered to your upstream service.

The API is organized around REST. We use standard HTTP verbs, return JSON-encoded responses, and use standard HTTP response codes to indicate errors.

Base URL

https://api.imhc.win/v1

Authentication

All API requests must include your API key in the Authorization header using the Bearer scheme. You can generate and manage API keys from your dashboard.

Authorization: Bearer imhc_live_xxxxxxxxxxxxxxxx

Route endpoint

The core routing endpoint accepts a target URL and optional configuration parameters. IMHC selects the optimal edge node automatically.

POST /v1/route
ParameterTypeDescription
targetstringRequired. The upstream URL to route to.
ttlintegerCache TTL in seconds. Default: 0 (no cache).
regionstringForce a specific edge region. Default: auto.
retryintegerNumber of retries on 5xx. Default: 2.

Response

{
  "status": "routed",
  "latency_ms": 9,
  "edge": "fra-01",
  "request_id": "req_8xKp2mNvQa",
  "upstream_status": 200
}
Pricing
Simple, usage-based pricing
Starter
$0
/ month — no credit card required
  • 1M requests / month
  • 3 edge regions
  • Basic routing
  • Community support
  • 99.9% uptime SLA
Enterprise
Custom
/ volume discounts available
  • Unlimited requests
  • Dedicated edge nodes
  • Custom SLA
  • SSO & audit logs
  • 24/7 dedicated support
  • On-premise option
System status
All systems operational
All systems operational
Last updated: just now
ServiceRegionUptime (90d)Status
API Gateway Global 99.97%
Operational
Edge — Europe fra-01, ams-01, lon-01 100%
Operational
Edge — Asia Pacific sin-01, nrt-01, hkg-01 99.94%
Operational
Edge — North America jfk-01, lax-01, ord-01 100%
Operational
Webhook delivery Global 99.99%
Operational
Dashboard & API Global 99.95%
Operational
Recent incidents
Elevated latency — Asia Pacific (sin-01)
Resolved · Apr 3, 2026 · Duration: 14 minutes
Scheduled maintenance — Dashboard
Completed · Mar 28, 2026 · Duration: 22 minutes
Webhook delivery delay — Global
Resolved · Mar 15, 2026 · Duration: 8 minutes