Skip to main content
The Nasiko server exposes one HTTP API — the same one the CLI, dashboard, and admin tools use. Base URL: https://free.app.nasiko.com on Nasiko Cloud Free. A paid workspace has its own subdomain, https://<workspace>.app.nasiko.com. Every path starts with /api/, for example https://free.app.nasiko.com/api/agents. Live spec (OSS only): http://localhost:8080/api/openapi.json on a local cluster, Swagger UI at /api/docs. The OpenAPI endpoints section of this site is a copy of that spec. Endpoints that the spec doesn’t cover are documented on the pages below.

Authentication

The API takes a session JWT. API keys aren’t supported. Sign in with the CLI, then print the token it stored:
To try an endpoint on this site, paste the token into the Authorization field and pick your server. From your own code, send it as Authorization: Bearer <token>. Tokens expire: nasiko auth status shows whether yours is still valid, and nasiko auth login gets a new one. See access control. Strict attribution: Cost attribution.

Conventions

Field names are snake_case. IDs are UUIDs. There is no /api/v1 prefix — evolution is additive. Always check the HTTP status first. The error body depends on where the request was rejected:

Hand-written surfaces

These are not in the generated OpenAPI file:

LLM router (/v1)

Chat Completions, Responses, Messages, Gemini, embeddings.

Coding agents

Register integrations and ingest telemetry.

Approvals (HITL)

Pending, resolve, cancel, stream, requeue.

OCI registry (/v2)

Embedded Distribution v2 for agent images.

Account and settings

Log in and out, change your password, your profile, and server settings.

Deployed agents

Containers, builds, image namespace, and agent cards.

Agent access

Share an agent with users, other agents, or everyone.

Chat

Chat sessions, messages, files, transcription, and calling an agent.

Harness sessions

Start, inspect, suspend, and remove harness sessions.

Workflows

Create, run, and stop multi-agent workflows.

Flows

List and record request lifecycles across agents.

Custom providers

Register and sync your own model providers.

TokenOps and observability

Savings, session turns and tool calls, and the estate overview.

MCP uploads

Track an uploaded MCP server while it builds.

GitHub

Connect GitHub, list repositories, and clone into a deploy.

Health and metrics

Liveness, readiness, and summary counts.
TokenOps extra routes (finops/spend-timeseries, spend-calendar, attributions, /api/usage/*) are listed in cost attribution. MCP management routes are in the generated spec and in MCP gateway. Custom providers: Providers.