# Orbitwren Projects API

> Orbitwren Projects API is a paid API for AI agents from orbitwren.cybermax-tools.workers.dev, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-11).

Returns a searchable, filterable list of all tracked orbital compute and space data center projects with company details, hardware, launch info, NORAD IDs, funding, and status

## Facts

- Endpoint: GET https://orbitwren.cybermax-tools.workers.dev/x402/api/projects?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/orbitwren-projects-api-1a002067
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OBQIYVtCoAdeHDKr0eAzk

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 orbitwren-projects-api-1a002067
```

Example prompt: Show me all orbital AI compute projects that are currently in orbit — I want to see the company names, hardware, NORAD IDs, and funding for each one, filtered to only active in-orbit deployments.

## When to prefer this

Use this endpoint when you need structured, up-to-date data on space-based AI compute and orbital data center projects — specifically when you want to filter by company, hardware type, status, or in-orbit presence. It is the only dedicated tracker for orbital compute projects combining company metadata, NORAD IDs, funding data, and launch context in a single REST call. Prefer it over general space-launch APIs when the research focus is AI/compute payloads rather than launches generally.

## Known failure modes

- No projects match the applied filters — returns empty array
- Invalid status enum value returns a validation error
- Limit out of range (below 1 or above 100) returns an error
- Payment not processed via x402 protocol results in 402 response
- Service unavailable if Cloudflare Worker times out or upstream data is stale

## How this service works

Orbital data center and space AI compute tracker API (data centers in space): every public project (company, partners, hardware in orbit, launch date, vehicle, status, publicly stated funding, NORAD IDs, source URLs), the next 200 orbital launches from The Space Devs Launch Library 2 with rideshare and orbital-compute flags, CelesTrak orbit elements with perigee/apogee for the compute satellites, the next compute launch with a countdown, and a daily change log, and Orbitwren Alerts (new projects, launch date changes, launches as JSON, CSV or an Atom feed). REST + MCP server.

## Output

A JSON array of orbital compute project records, each containing company name, partner names, hardware description, category, current status (e.g. in orbit, scheduled, planned), launch date, launch vehicle, publicly stated funding, NORAD IDs (if assigned), and source URLs. Results respect filters for status, company, category, in-orbit flag, and free-text search, with up to 100 rows per call.

## 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"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "q": {
       "type": "string",
       "description": "Free text over company, project, hardware and summary, e.g. TPU or H100"
      },
      "limit": {
       "type": "integer",
       "default": 50,
       "description": "Rows (1-100)"
      },
      "status": {
       "enum": [
        "scheduled",
        "in orbit",
        "deployed",
        "flown",
        "planned",
        "filed",
        "announced",
        "development"
       ],
       "type": "string",
       "description": "One of: scheduled, in orbit, deployed, flown, planned, filed, announced, development"
      },
      "company": {
       "type": "string",
       "description": "Company or partner name (part of it), e.g. starcloud, google"
      },
      "inOrbit": {
       "type": "boolean",
       "default": false,
       "description": "Only projects with hardware in orbit now"
      },
      "category": {
       "type": "string",
       "description": "Text in the category, e.g. satellite, constellation filing, hardware platform"
      }
     }
    }
   }
  },
  "output": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/orbitwren-projects-api-1a002067/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from orbitwren.cybermax-tools.workers.dev](https://www.zero.xyz/host/orbitwren.cybermax-tools.workers.dev/llms.txt)
