SOURCE
payments.yaml
OPENAPI 3.1
REVISION c12b770
paths:
/payments:
post:
summary:
Create payment
responses:
201: CreatedAPI 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, your storage, and a complete build history.
Founding access · €0 for 6 months · no credit card
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 + storageOwn 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 and storage. 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
PORTAL OVERVIEW
Payments API
pages
score
live
surfaces
One revision is ready
Synced source is ahead of the live portal.
Open revision →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.
Public developer portal
Fast, searchable documentation on your domain for customers and partners.
- Custom domain + TLS
- API reference and guides
- Version-aware search
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
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.
Scoped GitHub access
Installation-scoped credentials instead of personal access tokens.
Organization boundaries
Role checks and row-level controls protect tenant data.
Immutable builds
Draft, preview, live, history, and restore remain separate.
Domain and storage control
HTTPS custom domains and private object-storage delivery.
FOUNDING ACCESS
Use the product.
Then price it with us.
API Fleet is free for the first six months. No card, no surprise conversion, and no enterprise call before you have shipped a portal.
EARLY ACCESS
Founding plan
€0/ 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
EARLY ACCESS
Help decide
what ships next.
Tell us who you are, then pick up to three priorities. It takes less than a minute and goes directly to the founding team.
- Two short steps
- No newsletter
- Personal reply
- Privacy notice included