Documentation

The perception layer, as an API

Call the Digital Twin Earth over MCP or plain REST. Site intelligence, live hazards, buildings, traffic, place trends and street-level vision, every figure with disclosed provenance.

The API is keyless. Every endpoint answers without a key, without a card, without a signup. A key is optional and free: it names your usage and raises the per-minute ceiling from 120 to 600 requests per minute. That is all it does.

Keys and fair use

Keyless by default. A key is optional and free: it names your usage and raises the per-minute ceiling. That is all it does.

Keys are issued for free on the developer dashboard. Rotating there issues a new key and kills the old one immediately. Pass it as the X-Api-Key header or as a ?key= query parameter.

curl "https://api.solyzer.ai/earth/usage" \
  -H "X-Api-Key: YOUR_KEY"

GET /earth/usage returns your own consumption: owner (masked), today's total and per-path breakdown, the month total and a daily series. Without a valid key it returns 401.

Every /earth response carries X-RateLimit-Limit and X-RateLimit-Remaining. When you cross the ceiling you get a 429 with Retry-After: 60; back off and the window resets.

X-RateLimit-Limit: 120
X-RateLimit-Remaining: 118

Usage is counted at the origin. Reads served by the edge cache never reach it and are free.

Usage counts origin hits only. Reads served by the edge cache are free and are never counted, so they do not touch your usage or your per-minute ceiling.

Read this before the numbers

The layer is honest by design. These five rules hold on every response; an agent that respects them will not be misled.

Two ways in

Same tools, same contract, whichever door you pick. MCP and REST are two transports over one surface.

{
  "mcpServers": {
    "solyzer-earth": {
      "url": "https://api.solyzer.ai/mcp"
    }
  }
}

curl "https://api.solyzer.ai/earth/site-intel?\
  lat=-6.2088&lon=106.8456&radius=500"

The globe on your page

The same Digital Twin Earth, live, in one tag. Embedding on your own site takes a free publishable key, and a keyless frame renders only on solyzer.ai and on localhost while you build, so swap pk_earth_live_YOUR_KEY for your own. The key names your traffic and locks the frame to the domains you register. Source credit renders inside the frame and cannot be turned off.

<!-- Solyzer Digital Twin Earth -->
<div
  data-solyzer-earth
  data-lat="-6.2088"
  data-lon="106.8456"
  data-zoom="9"
  data-layers="quakes,disasters,cyclones"
  data-key="pk_earth_live_YOUR_KEY"
  data-height="520"
></div>
<script src="https://www.solyzer.ai/embed.js" async></script>

<iframe
  src="https://www.solyzer.ai/embed/earth?lat=-6.2088&lon=106.8456&zoom=9&layers=quakes%2Cdisasters%2Ccyclones&k=pk_earth_live_YOUR_KEY"
  title="Solyzer Digital Twin Earth"
  width="100%"
  height="520"
  loading="lazy"
  referrerpolicy="strict-origin-when-cross-origin"
  allow="fullscreen"
  sandbox="allow-scripts allow-same-origin allow-popups"
  style="border:1px solid #26262a;border-radius:12px;display:block"
></iframe>

The full surface

11 tools. Each MCP tool maps 1:1 to the REST path shown next to it.

The live manifest is unreachable right now, so this reference is the built-in fallback and may lag.

The authoritative, always-current list lives at https://api.solyzer.ai/earth/agent-tools.

One server, no ceremony

The MCP server speaks streamable HTTP and is stateless: every call stands alone, nothing to session, nothing to hold open. It exposes exactly the tools in the reference above; the REST paths and the earth_* tools are the same surface.

{
  "mcpServers": {
    "solyzer-earth": {
      "url": "https://api.solyzer.ai/mcp"
    }
  }
}