Yachay

Docs

API access

The Yachay backend exposes a REST API that the dashboard talks to. Today it’s gated to first-party use; a public, versioned, documented surface ships in v1.1.

v1 status

No public API in v1.The endpoints described below exist and are stable enough that the Yachay frontend depends on them, but we’re not advertising them as a public contract yet — we reserve the right to break shapes before the v1.1 launch. If you have an integration need that can’t wait, email hello@condorbox.aiwith your use case and we’ll see what we can lock in.

What exists today (first-party only)

Base URL: https://api.models.condorbox.ai/v1. Auth is a Firebase Auth ID token in theAuthorization: Bearer <token>header (issued by the umbrella at sign-in).

  • GET /models — model catalog
  • POST /jobs/estimate — preview the price for a (model, dataset, hyperparams) tuple
  • POST /jobs/setup-card — start a Stripe Checkout session in setup mode to save a card on file (one-time per customer)
  • POST /jobs — submit a tune; charged off-session at completion against the saved card
  • GET /jobs — list your jobs (paginated, cursor-based)
  • GET /jobs/{job_id} — single job status
  • POST /jobs/{job_id}/cancel — cancel a running job
  • GET /jobs/{job_id}/download — fresh 1-hour signed adapter URLs
  • POST /jobs/{job_id}/extend-storage — buy a retention extension
  • GET /me — account state (pause flags, notification prefs, portal URL)
  • GET /billing/summary — lifetime spend + storage-extension totals
  • GET /healthz — liveness probe (unauth)

v1.1 roadmap

  • API keys — long-lived, scoped, revocable API keys minted from the dashboard. Today auth is Firebase ID tokens (1-hour expiry, browser-only) which makes server-to-server integration painful.
  • CLI — yachay submit / yachay status / yachay download. Same surface as the dashboard but scriptable. Apache 2.0, Go binary, no daemon.
  • Webhooks — HMAC-signed POST to a URL of your choice on job state transitions (queued → running → completed / failed / cancelled).
  • OpenAPI spec — generated from the FastAPI app, hosted at api.models.condorbox.ai/openapi.json with versioning + deprecation policy.

Compatibility policy

Once v1.1 ships, the path prefix /v1/ is a SemVer-style contract: additive-only changes (new fields, new endpoints) inside v1; breaking changes ship as /v2/ with at least 6 months overlap before v1 sunsets. Internal-only endpoints — currently everything in the list above — are not subject to that policy until v1.1.

← All docs · Pricing · API status