Remote API documentation for workspaces

Give teams and AI agents one clean place to keep API docs current.

Apicon stores API projects, endpoints, request and response examples, workflows, and generated API references for each workspace.

Workspace test-user

Active

MCP endpoint https://apicon.test/mcp/api-docs

Stored API project Partner API 12 endpoints documented

Generated references

Swagger Scalar

source API context target selected by agent

{
  "default_target": "main",
  "targets": {
    "main": {
      "workspace_slug": "test-user",
      "project_slug": "partner-api",
      "project_name": "Partner API",
      "servers": [
        {
          "url": "https://partner.test/api/v1",
          "description": "Stored API project server"
        }
      ],
      "version": "v1",
      "default_status": "published"
    },
    "partner": {
      "workspace_slug": "partners",
      "project_slug": "partner-api",
      "project_name": "Partner API",
      "servers": [
        {
          "url": "https://partner.example.com/api/v1"
        }
      ],
      "version": "v1",
      "default_status": "published"
    }
  },
  "read_projects": [
    {
      "workspace_slug": "test-user",
      "project_slug": "partner-api"
    },
    {
      "workspace_slug": "billing-workspace",
      "project_slug": "billing"
    }
  ]
}

Recommended workflow

Let source API repos write docs and external systems read them.

Create a workspace

An admin creates the account and workspace path for the team or API owner.

Create a bearer token

Members create user-scoped tokens. Workspace membership and role decide what each request can access.

Add source API context

Source API repos use .apicon.json to define named write targets, default target, servers, version, and related read projects.

Read selected context

Agents can page through allowed project endpoints with Read API Endpoints, while external systems can use Scalar, Swagger, OpenAPI JSON, or read-only MCP resources.

What Apicon manages

A workspace API catalog built for humans and agents.

Workspace isolation

Each workspace keeps its API catalog, members, and generated references separate while user tokens follow account permissions.

Stored OpenAPI

Apicon turns saved endpoints and examples into project-specific OpenAPI documents.

Swagger and Scalar

Readers can inspect and test stored APIs with familiar reference viewers.

Remote MCP

Source API agents can create docs remotely and read selected cross-project endpoint context page by page.

Role-based access

Admins manage members, developers write docs, and workspace users can view docs. Write-capable tokens still depend on the account's active workspace roles.

Operational memory

Flows preserve how endpoints work together, not just what each route accepts.