Agent-as-a-Service

Build agents.
The harness is done.

Embed Octo into your own product — frontend or backend. Octodus runs the agent loop, context, tools, files and usage metering under the hood, and exposes it all over a REST API. You own the experience; we run the engine.

Read the API docs Open the dashboard

Division of responsibility

Your product
  • Defines the experience — interface and business logic.
  • Sets the agent’s role and instructions.
  • Owns user data and permissions.
Octodus /v1
  • Runs the agent loop — planning and sub-agents.
  • Provides tools, files, memory and integrations.
  • Handles model orchestration, usage metering and billing.

Two ways to embed

In your frontend

Back a chat surface or widget with the API. The user talks to Octo inside your app; you keep full control of the UI and the surrounding flow.

In your backend

Call the REST API from your server, stream results, and drive Octo programmatically as part of a larger workflow — no chat surface required.

What the /v1 API gives you

One authenticated endpoint, the same engine that powers the chat.

  • Spaces — isolated workspaces, each with its own context, memory and access.
  • Tools & integrations — Google, hosting and deployment, web, and more, acting on your behalf.
  • Files in and out, plus streaming responses for long-running jobs.
  • Usage metering and billing handled per Space.

Keys & access, done safely

Authenticate with an API key issued from the dashboard.

  • Keys are scoped and managed in dash.octodus.com — never pasted into a chat.
  • Secrets are stored encrypted; the assistant never sees them in the clear.

Full API reference

Endpoints, request/response shapes and examples live in the interactive docs.

Read the API docs
Add octodus to your chat

Ship an agent this week.
The runtime is already live.

Tell us what you want to embed and we will point you at the right endpoints.

Talk integrations
EN · DE · FR·Telegram today · Slack & Discord soon