Skip to content
Zentro

Build with Zentro

Developer hub

Same-origin APIs, documented routes, and API keys — integrate with Zentro without exposing private backend URLs in the browser.

Quick start

  1. 1. Read the API catalog

    Browse authenticated and public routes at /docs/api.

  2. 2. Sign in and create an API key

    Keys use the zentro_sk_ prefix and are managed in Settings.

  3. 3. Send alert ingest or call a route

    Use Bearer auth or ingest tokens as documented per route.

  4. 4. Check connector health

    Verify reasoning and robot proxies from Settings → Connectors.

Product Access

Open live Zentro products and documentation.

API request builder

Copyable curl and SDK examples — not executed in browser.

Documentation

Guides for setup, console modules, and deployment.

API reference

Catalog of public and authenticated API routes.

Integrations

Alert ingest, Slack approvals, and connector health.

GitHub

Open-source web application and migration scripts.

SDK & CLI overview

  • TypeScript / Next.js (this repo)

    Open-source web app at github.com/aicodeai50/ZENTRO — primary integration surface today.

    Available

  • TypeScript SDK

    Documented alongside the API catalog; dedicated package publishing is in progress.

    Preview

  • Python SDK

    Planned — use REST and API keys until published.

    Coming soon

  • CLI

    Planned developer CLI for keys, ingest testing, and health checks.

    Planned

Zentro AI

Standalone product at https://ai.zentro.run. Console Copilot uses same-origin /api/copilot/chat with server-side keys — not embedded on marketing pages.

Open Zentro AI ↗

Authentication

  • Browser sessions: Supabase Auth cookies on console routes.
  • Programmatic access: API keys (Authorization: Bearer zentro_sk_…).
  • Alert ingest: dedicated ingest tokens scoped per workspace.
  • Webhooks: PayPal signature verification server-side; never expose secrets in client code.

Error handling

  • 401 — missing or invalid API key / session.
  • 403 — org role or plan does not allow the action.
  • 429 — rate limit exceeded on sensitive routes.
  • 502 — upstream connector (reasoning/robot) unreachable when configured.

API request builder

Copy example requests for documented routes — run them in your terminal or server.

API request builder — generates copyable examples only. Requests are not executed from this page. Use your own terminal or server with a valid API key.

Public liveness — no authentication.

Example request (not executed)

curl -s https://zentro.run/api/health

Example response shape

{
  "ok": true,
  "service": "zentro-web",
  "uptime_s": 12345
}

Example request

// Example: authenticated API request (server or script)
const res = await fetch("https://zentro.run/api/overview/error-budget-summary", {
  headers: {
    Authorization: "Bearer zentro_sk_your_key_here",
  },
});
if (!res.ok) throw new Error(`HTTP ${res.status}`);
const data = await res.json();

Usage and billing

PayPal subscriptions and balance sync through server routes when configured. API usage is org-scoped; see /pricing and /settings/billing when signed in. No usage-based billing claims on this page beyond what your plan includes.

Pricing →Status →Changelog →

Try Zentro

Explore products →

Start a pilot

Apply for a pilot →

Build with Zentro

Developer hub →