Skip to content
Docs navigationBrowse tools →

Start with browser tools. Pro has no paid delivery today; API and Console documentation describes development capabilities, not guaranteed hosted access. Implemented interfaces and development screens do not imply public production availability, paid access or a completed payment integration. Confirm access with Birdor before connecting an application.

Docs · Platform

Developer Console

The Birdor Developer Console is the early-access control plane for your projects, environments, and supported API usage. It gives you a calm overview of what's running on Birdor — and a simple way to manage keys, logs, and plan state without heavy ceremony.

Console Structure

The Console is organized into a small set of focused sections:
  • Overview — first-run guidance plus live workspace, usage, and billing summaries.
  • Projects — optional structure for grouping usage by app or service.
  • Tasks & schedules — inspect task, schedule, and automation activity.
  • API Keys — create, rotate, and revoke keys.
  • Usage & Logs — inspect requests and errors.
  • Billing & Plans — manage your subscription.
  • Profile & workspace — view account, workspace state, and security activity.
  • Workspace Settings — naming, regions, preferences, and retention notes.

The goal is to keep the Console predictable and calm: fewer screens, fewer toggles, and a single place to answer "what is going on with our usage?".

Access

Access & Authentication

You access the Console via /console. Authentication is handled via your Birdor account, and each account is associated with one or more workspaces.
  • A workspace is where settings, projects, and billing live.
  • Within a workspace, you can create multiple projects to separate usage.
  • Shared workspace access is being rolled out carefully; not every environment should be assumed to expose the full multi-member self-serve flow yet.

Sign-in and session surfaces live under the same Console, while exact OAuth provider availability still depends on runtime configuration.

Dashboard

The Overview screen is the first screen you see after signing in. In the checked-in product, it's meant to answer a few simple questions without pretending Birdor already has a giant enterprise analytics surface:

  • Do I have the right workspace boundary selected?
  • Can I create a key and make one successful request?
  • Did that request appear in logs, usage, and billing state?
  • How much of my monthly quota have I used?
01

First-run path

The live path is narrow on purpose: confirm the workspace, create one API key, send one request, then inspect logs, usage, and billing.
02

Workspace and usage

Live cards summarize current workspace quota and billing state. Richer per-tool and per-project views are still intentionally limited.
03

Recent activity

Tasks and recent changes are visible where the current control plane records them; this should not be read as a separate enterprise event bus.

Tasks, Schedules & Automations

The Console now includes an early-access tasks page for workspace-scoped task records, schedule history, and automation activity on the current checked-in control plane.
  • Inspect current task state and recent run history.
  • Review schedule configuration and launch-surface run history.
  • See webhook-backed triggers under automations instead of a separate launch-era webhooks console.

Current run history is recorded by the checked-in control plane. It should not be read as evidence of a separate distributed worker fleet.

Projects

Projects & Environments

Projects are a way to group usage logically — per application, microservice, or customer. Each project can have multiple environments, such as:
  • development
  • staging / preview
  • production

This lets you keep keys, logs, and usage isolated per environment while still seeing an aggregated view at the workspace level.

Future iterations may add per-environment alerts, rate limits, and more fine-grained settings.

API Keys & Secrets

API keys are how your backend authenticates with Birdor APIs. In the Console, you can:
  • Create keys scoped to a specific project and environment.
  • Give keys human-readable names (e.g. "prod backend").
  • Revoke keys instantly if they're no longer needed.
  • See when a key was last used.

The currently supported self-serve path is narrower than a full secrets platform. Treat the Console as the place to manage API key lifecycle and one-time secret display, not as a generic secret vault.

Usage & Logs

The Usage & Logs section is where you inspect how your applications are talking to Birdor.
  • Filter by project, environment, tool, status code, or time range.
  • See request counts and error rates over time.
  • Drill into individual log entries for debugging.

In early versions, this focuses on simple, structured logs. Over time, it may grow into a richer log and alerting layer (still with a calm design).

Billing & Plans

The Billing section shows your current plan, usage against quota, and any available billing records for the current workspace. Plan changes that are not self-serve yet should still go through pricing intake or support instead of being inferred from this page. The philosophy is the same as elsewhere in Birdor:
  • Pricing should be transparent and boring.
  • The free tier should be genuinely useful.
  • Upgrades and cancellations should never be hidden behind email forms.

Team

Team & Access Control

Team & API is being introduced as a narrow shared-workspace layer, not a large enterprise admin surface. Early versions are intentionally simple:
  • Shared workspace access where enabled.
  • A small set of predefined roles.

As the platform grows, more fine-grained roles may be added, always with an emphasis on clarity over complexity, and only after the self-serve surface is ready.

Start

Getting Started with the Console

A typical first-time path through the Console looks like this:
  1. 01Sign in to Birdor and open the Developer Console.
  2. 02Confirm your workspace boundary on the overview screen.
  3. 03Create one API key, preferably workspace-wide with metrics.read for the first request.
  4. 04Use the API quickstart to call GET /v1/workspaces/:workspaceId/monitoring/summary.
  5. 05Watch logs, usage, and billing state update in the Console.

From there, you can add project/environment structure only when you actually need it, instead of starting with unnecessary setup.

If Birdor has enabled the hosted hash pilot for your workspace, mint a second key using tools.run and call POST /v1/workspaces/:workspaceId/tools/hash/digest. The request will show up in the same logs, usage, and billing surfaces as the control-plane quickstart above.

Failure Paths & Support

The Console should help you explain failures before you ask Birdor for help. The minimum supportable path is still: request response, request id, logs, usage, billing, then role/scope review.
01

Start here

  • Logs for request id, status, and path.
  • Billing/usage for quota or plan state.
  • API keys for scope and one-time secret history.
  • Workspace members for role and access boundaries.
02

Not self-serve yet

  • Team / Enterprise billing changes.
  • Broader hosted API enablement beyond the current pilot.
  • Provider-backed payment method collection or PDF invoices.

If you hit those edges, use pricing intake or contact contact@birdor.com with the workspace id and request id.

Intent

Design Goals

The Console is intentionally not a busy enterprise control center. It's a quiet companion for your work — a place to check on things, adjust a few dials, and then get back to building.

As Birdor grows, this page will stay up to date with new sections, screenshots, and API references — but the underlying promise remains the same: calm, developer-first infrastructure.