Create projects, queue visibility runs, and read scored results from your own systems. The focadio API wraps the same tenant-scoped pipeline the dashboard uses — with run queues, idempotency, and metering built in.
Endpoints are described against the platform as it exists today. Anything roadmap-only is marked clearly.
The dashboard uses a customer-side JWT for human sessions. Enterprise customers can also issue API keys for server-to-server programmatic access. Both authenticate into the same tenant scope.
Dashboard sessions authenticate through Supabase JWT.
Authorization: Bearer <supabase_jwt>
Enterprise customers can issue API keys. Keys are hashed at rest.
Authorization: Bearer <api_key>
Nine endpoints cover the full loop: project setup, query management, run creation, run status, results, score breakdowns, and an optional callback for n8n orchestration.
/healthService health check./projectsCreate a tenant-scoped project./projects/{id}/queriesAdd target queries to a project./projects/{id}/queries/discoverDiscover candidate queries for a project./projects/{id}/runsStart a visibility run (debits credit on creation)./runs/{id}Read run status, including queue and pipeline state./runs/{id}/resultsRead visibility results after the run has processed./runs/{id}/scoresRead the per-query score breakdown for a run./callbacks/n8nOptional n8n callback for orchestrated workflows. OptionalEvery API call resolves to a tenant. Projects, runs, results, and ledger entries stay inside that scope.
Run creation enqueues background pipeline work and returns a run ID. The API never blocks on long-running engine calls.
Run creation debits credit from the tenant ledger so usage is predictable and observable.
Run creation supports idempotency keys, so retries do not produce duplicate runs or duplicate debits.
Adapter-mediated AI and SERP calls capture tokens, latency, and cost — visible per run.
Result endpoints reflect the state of the queued pipeline. Callers poll the run status or wait for completion.
Talk to us about scoping API access for your enterprise workflow. We will only describe endpoints and behavior the platform supports today.