Menu
Sign In Try APIDome
Platform

Six workspaces. One operating system.

APIDome arranges its modules into six workspaces, starting with Voyage, the guided journeys that take each change through the others. Underneath, APIDome OS™ runs every action the same governed way.
APIDome OS™
Voyage
Guided Journeys

Guided journeys that take each change, such as a new API, step by step through every module involved.

Atelier
Design & Build

Design and mock APIs, see them as diagrams, and publish them as MCP servers for AI agents.

Assay
Quality & Governance

Test every API, follow its quality and enforce policy before changes reach consumers.

Galleria
Catalog & Commerce

Catalog every API, let consumers subscribe, and price, bill and settle what they use.

Conduit
Run & Connect

Run live traffic and quotas, route platform events and connect your backend systems.

Nucleus
Platform & AI

AI agents and models, identity and access, and the OS every action runs through.

Inside the platform

See APIDome at work.

From the first line of a specification to an AI agent calling your API, in a few steps.
Specifications

One contract for every API

Each API has one specification as its source of truth, with versions and revisions you can compare and merge.

Payments API · Specification
Payments APIv1v2
r1r2r3
Compare r2 ↔ r3
- amount: integer
+ amount: number
+ currency: string
✓ Merged into r3
Design Studio

Write the design

Author and edit API specifications in one studio, and save each change as a new revision.

Design Studio · payments.yaml
1openapi: 3.0.3
2info:
3 title: Payments API
4 version: 2.0.0
5paths:
6 /payments:
7 post:
8 summary: Create a payment
9 responses: { '201': Created }
✓ Saved as revision r3
Built-in templates

Start from a template

Built-in templates combine a base, an industry profile and your own customisation into a specification ready to edit.

Template Factory
Base templateStandard resources, errors and paging
Industry profileThe conventions of your industry
Your customisationThis API's own resources and fields
↓
Payments API · specificationReady in Design Studio
Diagram Studio

See it as a diagram

Every design becomes a diagram, drawn from the specification so it never drifts from it.

Diagram Studio · Payments API
Drawn from revision r3
Mock Studio

Mock it before you build it

Mock responses let consumers start work before the API is built.

Mock Studio · Payments API
POST /payments
{ "amount": 20, "currency": "EUR" }
Send ➜
201 Created
{ "id": "pay_1042", "status": "pending" }
Mock response · no backend needed
MCP Studio

Ready for AI agents

Turn suitable APIs into MCP servers that AI agents can call, then test and deploy them.

MCP Studio
Payments API✓ Ready for agents
➜
MCP serverpayments
create_paymentget_payment
Pay invoice 1042, €20
create_payment → 201 ✓
Done: the payment has been created.
Your own AI

Bring your own AI

Use APIDome Intelligence, or connect your organisation's own OpenAI-compatible model. It is checked before it is used, and works under the same rules.

APIDome Intelligence · Model
APIDome IntelligenceReady to use
Your own modelOpenAI-compatible
Conformance evaluation passed ✓
Your policies applyNo silent fallbackUsage shown for your tenant
Payments API · Specification
Payments APIv1v2
r1r2r3
Compare r2 ↔ r3
- amount: integer
+ amount: number
+ currency: string
✓ Merged into r3
Design Studio · payments.yaml
1openapi: 3.0.3
2info:
3 title: Payments API
4 version: 2.0.0
5paths:
6 /payments:
7 post:
8 summary: Create a payment
9 responses: { '201': Created }
✓ Saved as revision r3
Template Factory
Base templateStandard resources, errors and paging
Industry profileThe conventions of your industry
Your customisationThis API's own resources and fields
↓
Payments API · specificationReady in Design Studio
Diagram Studio · Payments API
Drawn from revision r3
Mock Studio · Payments API
POST /payments
{ "amount": 20, "currency": "EUR" }
Send ➜
201 Created
{ "id": "pay_1042", "status": "pending" }
Mock response · no backend needed
MCP Studio
Payments API✓ Ready for agents
➜
MCP serverpayments
create_paymentget_payment
Pay invoice 1042, €20
create_payment → 201 ✓
Done: the payment has been created.
APIDome Intelligence · Model
APIDome IntelligenceReady to use
Your own modelOpenAI-compatible
Conformance evaluation passed ✓
Your policies applyNo silent fallbackUsage shown for your tenant

Voyage

Guided Journeys

Guided work packages that take a change step by step through every module involved, such as creating a new API or modifying an existing one.

Atelier

Design & Build

Author specifications, start from templates, mock before you build, see every design as a diagram, and publish APIs as MCP servers for AI agents.

ForgeDesign APIs in Design Studio, automate build steps in Workflow Studio, start from reusable templates in Template Factory and mock responses in Mock Studio.
Diagram StudioSee an API's design as a diagram, drawn from the specification so it never drifts from it.
MCP StudioFind the APIs ready to serve AI agents, turn them into MCP servers, test and deploy them, and see how agents use them.

Assay

Quality & Governance

Prove every API works and meets your standards: run test suites, follow quality over time, enforce policy and approve changes before they reach consumers.

Forge-QBuild test suites, run them against your environments and follow quality over time.
SentinelDefine policies and governance rules, validate APIs against them and approve changes before release.

Galleria

Catalog & Commerce

One catalog with a 360° view of every API, a marketplace where consumers subscribe, and the pricing, billing and settlement behind it.

AtlasThe catalog of every API, with a 360° view of versions, contracts, quality, runtime and consumers, API products, and an explorer to try operations.
NexusThe marketplace where consumers find APIs, register applications, subscribe to plans, get credentials and follow their usage.
CommercialTurn APIs into offerings: pricing, metered usage, charges, prepaid wallets, billing, payments and settlement, traced from each call to the invoice.

Conduit

Run & Connect

Operate live traffic and quotas, route platform events to the right place, and connect the backend systems your APIs depend on.

FluxOperate the API runtime: traffic and usage, quotas, subscription health and gateway operations.
PulseGridPlatform events and the rules that route them, with a history of every dispatch.
CoreLinkRegister the backend systems your APIs depend on and reach them through managed connectors.

Nucleus

Platform & AI

AI agents, knowledge and models; tenants, identity and access; and the operating system every action runs through.

APIDome IntelligenceAgents, the knowledge they answer from, model access and usage, evaluations, prompt templates and industry packs.
FoundationUsers, roles and access, identity providers, tenants and observability.
APIDome OSThe health of the operating system and what it ran for your organization: executions, failures, recovery and events.
APIDome OS™

The industry's first native OS for the API Ecosystem.

Not a set of loose modules: APIDome OS™ is the common foundation through which every module, journey and external provider works.

Journey Runtime

Role-aware journeys and work packages move people through a change on the same execution path.

Governed Actions

Every action runs through one control plane that applies policy and keeps state.

Policy & Access

Identity, roles and permissions decide what each person, agent and tenant can do.

Evidence & Receipts

Each execution leaves a receipt, an audit trail and its artifacts, so every result can be traced.

Module Adapters

Modules stay independent but share common contracts, so they work together without shortcuts.

Driver Runtime

External systems, gateways and AI models are reached through standard, governed drivers.

APIDome Intelligence

Intelligence belongs inside the platform, not beside it.

APIDome Intelligence gives you agents, grounded answers, model access and evaluations, all governed by APIDome OS™. Use APIDome's own model or connect yours.

Grounded answersAnswers come from your own knowledge and the context of the module you are working in.
Governed model accessModel providers sit behind the standard driver runtime, with usage tracked per tenant.
Agents that ask firstAgent steps run through the same authorized actions and MCP paths as people, and wait for your confirmation where the action needs it.
Evaluated before releaseEvaluations measure answer quality, and changes go live only when they pass.

Start building on APIDome.

Create an account and choose your first journey, or sign in to carry on where you left off.

Try APIDomeTalk to Us