Introduction
Catentio is a multi-agent operator platform — the SaaS face of the catentio agent runtime. A single Catentio workspace gives you a fleet of named agents (hachimi, tora, sai, ren, fumi, iro…) that you can invoke from the portal, the CLI, the API, or programmatically from another product over the Forjio family bus.
This documentation covers the developer-facing surface: signing in, invoking an agent, running a project pipeline, watching runs, and integrating Catentio into your own code via the SDKs.
New to Catentio? Start with the Quickstart — you'll have an agent run completed in about five minutes.
What's here
The docs are organised by how you'll use the product over time:
- Getting started — sign in, install the CLI or SDK, invoke an agent end-to-end.
- Core concepts — workspaces, agents, runs, projects, tools, skills, memory, heartbeats.
- Authentication — Huudis SSO, the Catentio session model, and the chat-bubble session bound to your portal identity.
- Portal — per-feature tours of what you can do in the dashboard at catent.io.
- API reference — the control-plane REST API the portal runs on.
- SDKs — per-language guides for Node.js, Python, and Go.
A note on access
Integrating over HTTP? Catentio has a public API at
https://catent.io/v1/, authenticated with an API key you create in the portal. It is deliberately small — nine endpoints: list agents, list workflows, dispatch a run, read a run, start a project, read a project, and register/list/delete outbound webhooks.The rest of the API reference documents the internal control-plane protocol, which is a different surface and is not reachable with an API key. Start at API reference → Reachability so you don't confuse the two.
Sign-in is gated by an allow-list: the internal operator (HUUDIS_ALLOWED_USER_ID) plus any customer identities listed in HUUDIS_ALLOWED_USER_IDS. An identity outside the list is rejected with 403 NOT_AUTHORIZED.
Want access? Contact us.
A note on the Forjio family
Catentio is part of the Forjio family — a set of independent SaaS products that share identity (Huudis SSO), billing (Plugipay, for non-Plugipay products), and design conventions. If you've used Storlaunch, Fulkruma, Ripllo, LinkSnap, Pawpado, or Plugipay, the auth and SDK shapes here will feel familiar.
Each product owns its own bounded context. Catentio owns agents, runs, projects, skills, tools, memory, and heartbeats. It does not own customer identity (that's Huudis), payment processing (Plugipay), or product storefronts (Storlaunch) — those live in their respective Forjio products.
Reach us
- GitHub issues: hachimi-cat/catentio-saas-node
- Email: hello@catentio.com
Ready? Go to the Quickstart.