Developer Docs & API

Docs that keep up with your API.

Point HelpBento at your OpenAPI spec and get a hosted, versioned API reference, with parameters, schemas and examples, living in the same box as the rest of your support.

docs.cedarloop.dev/api/users/create
API reference / Users
Create a user
POST/v1/users

Creates a new user in your workspace. They receive an email invite to set a password and join your team.

Parameters
emailstringrequired
The user’s email address.
namestringoptional
Display name. Defaults to the email handle.
roleenumoptional
One of admin, member or viewer.
OpenAPI in, reference outversioned, at stable URLsone search with your guides
Generated from the spec

Docs that can’t drift from the API.

Your OpenAPI spec is the source of truth. Every operation gets a reference page with its parameters, schemas and an example response, regenerated whenever you import a new spec, so the reference is never a version behind.

A reference page for every endpoint, from the spec
Parameters, schemas and example responses, in sync
Guides and reference share one search
Pick an endpoint to see its reference
POST/v1/users

Add a user to your workspace.

Parameters
emailstringrequired
The user’s email address.
roleenumoptional
One of admin, member or viewer.
Response · 200
{ "id": "usr_8FkQd2", "email": "[email protected]", "role": "member" }
Every operation, straight from your OpenAPI spec.
Versioned by default

Every version keeps its docs.

Ship v2 without stranding the developers on v1. Old versions stay published at stable URLs, deprecations are flagged inline with migration notes, and every release gets its own changelog.

Pin integrations, not people
Readers pick their version in the docs. Links keep working, nothing 404s when you cut a release.
A changelog per release
Draft, beta, stable and deprecated versions, each with release notes that publish to a changelog readers can follow.
API changelog
per-version release notes · /changelog
v2.4 · current
Added
POST /v1/users/invite
Bulk-invite users by email.
v2.4
Changed
POST /v1/users
role is now optional, defaults to member.
v2.4
Deprecated
GET /v1/users/all
Use GET /v1/users. Removed in v3, with a migration note inline.
v2.3
Still on v1? Your docs stay pinned at docs.cedarloop.dev/v1.
Docs as code

Manage docs like your code.

Your API reference is data, not a CMS. Import or replace a spec, cut a new version, or edit the changelog through the REST API, the MCP server, or the Claude Code plugin, so publishing fits your workflow instead of interrupting it.

Import or replace a spec via the REST API
The MCP server and Claude Code plugin manage versions and references
Every change lands as a draft you publish
Step through the flow
Stage
cedarloop/api · openapi.json
imported via the Claude Code plugin
v2.4 · Draft
Spec imported
A new openapi.json lands via the REST API, MCP server or Claude Code plugin.
Cut a new version
Clone the docs into a draft version and jot the release notes.
Published
v2.4 goes live; v2.3 and v1 keep their stable URLs.
Cloned into a draft version, release notes ready to review.
Part of the box

Dev docs, same box as support.

Reference, guides and support share one search, one theme and one AI agent.

Ship docs like you ship code.

Point HelpBento at your OpenAPI spec and your developer portal is live in minutes. HelpBento is in private beta.

Private beta · Free for 14 days · New spots weekly