API PORTALS, BUILT LIKE A RELEASE

Specs in.
Trusted portals out.

Sync OpenAPI from Git. Review what changed. Publish public, private, and agent-ready documentation with your domain, access controls, and a complete build history.

Build your first portal Read the docs

API First Journey Starter Program · guided onboarding · no credit card

acme/api-specsmain · synced 2 min ago

SOURCE

payments.yaml

OPENAPI 3.1
REVISION c12b770

paths:
  /payments:
    post:
      summary:
        Create payment
      responses:
        201: Created

REVIEW

Revision ready

NO BREAKING CHANGES

+ 2 operations added
~ 1 schema changed
✓ quality checks passed

READY TO PUBLISHPreview → Live

PORTAL

developer.acme.com

LIVE

Payments API Create a payment POST /v1/payments Request Responses

BUILD 128 · c12b770

Git-nativeRepository stays the source.

Revision-awareEvery sync has an identity.

Review before publishKnow exactly what changed.

Domain + accessOwn the delivery surface.

Human + agent readyOne source, every reader.

THE POSITION

API documentation
should move at API
speed.

A portal should not become a second source of truth. It should make the source safer to release and easier to understand.

Source stays source.

Connect the repository. Keep authorship where engineering already works.

Changes stay visible.

Separate synced and published revisions. Review the distance between them.

Readers stay contextual.

Give public developers, private teams, and agents the right surface from one system.

SOURCE TO LIVE

A release workflow for API documentation.

API Fleet treats documentation like the product surface it is: connected to source, reviewable, controlled, and reversible.

CONNECT

Sync the source

GHacme/api-specsmain branch

specs/**/*.yaml

payments.yaml
identity.yaml
webhooks.yaml

Install the GitHub App, choose a branch and pattern, and let every relevant specification arrive with its commit.

REVIEW

Understand the change

SYNCEDc12b770

≠

PUBLISHEDa910e42

+2 operations ~1 schema

● No breaking changes

Keep synced and published versions separate. See what moved before your users do.

SHAPE

Make it yours

AUDIENCE

Public

Private

Agent

ACCESS

Live

Preview

Gated

Set navigation, theme, access, and audience without forking the underlying API content.

RELEASE

Publish with control

Build 128 is live developer.acme.com Restore any earlier build

Ship an immutable build to your domain with controlled access. Restore an earlier release when you need to.

ONE PORTAL. ONE OPERATING SYSTEM.

One portal.
One operating system
for your API.

Content, quality, publishing, and access belong to the portal—not scattered across unrelated global tools.

Portal-scoped navigation
Synced versus published state
Build history and rollback
Public, private, and page-level access

EXPLORE THE PRODUCT →

API FLEETACME / PAYMENTS

PORTAL OVERVIEW

Payments API

LIVE

SYNCED REVISIONc12b770

2 minutes ago

→

PUBLISHED REVISIONa910e42

Build 127

Review changes

CONTENT24

pages

QUALITY94

score

BUILD128

live

AUDIENCE3

surfaces

RELEASE ATTENTION

One revision is ready

Synced source is ahead of the live portal.

Open revision →

ACCESS

Public portalLIVE

Private workspaceON

Agent endpointON

THREE READERS. ONE SOURCE.

The right portal for every audience.

Shape access and presentation for the reader without copying or drifting the source.

01 / PUBLIC

Public developer portal

Fast, searchable documentation on your domain for customers and partners.

Custom domain + TLS
API reference and guides
Version-aware search

02 / PRIVATE

Private internal portal

The same release discipline for internal APIs, protected behind team access.

Google and Microsoft sign-in
Roles and page-level gates
Preview before live

03 / AGENT

Structured machine context

Predictable API knowledge for coding agents, RAG systems, and MCP clients.

Structured source context
Revision identity
Audience-safe access

SECURITY WITHOUT THE THEATRE

Your specs describe how your systems work. We treat them accordingly.

01 / REPOSITORY

Scoped GitHub access

Installation-scoped credentials instead of personal access tokens.

02 / TENANCY

Organization boundaries

Role checks and row-level controls protect tenant data.

03 / RELEASES

Immutable builds

Draft, preview, live, history, and restore remain separate.

04 / DELIVERY

Domain and delivery control

HTTPS custom domains and controlled portal delivery.

API FIRST JOURNEY STARTER PROGRAM

Launch your first trusted
API portal—with us.

A guided six-month starter program for API-first teams. Bring your API source; we help shape the documentation, access model, and release workflow. No card and no automatic conversion.

Apply to the Starter Program View program details

STARTER PROGRAM

API First Journey

€0/ first 6 months

1 live public portal
Up to 5 private portals
100 pages each
GitHub specification sync
Custom domain + TLS

Google and Microsoft sign-in
Build history and restore
Page-level access gates
Theme and navigation control
Direct founder support

STARTER PROGRAM

Start the journey
with us.

Tell us about your API program, then pick up to three priorities. It takes less than a minute and goes directly to the team building API Fleet.

Two short steps
No newsletter
Personal reply
Privacy notice included

01 ABOUT YOU02 PRIORITIES

Tell us about your team Work email Company name Team size

Your details are used only for early access.

We use your details to evaluate and contact you about early access. Submissions are processed by Formspree. Privacy notice.