\n \n\n"},{"@type":"HowToStep","position":2,"name":"Publish","text":"> \"Publish swagger-ui.html to Display for everyone at my company.\"\n\nYour agent publishes the file and returns the link.\n\nFor Redoc:\nnpx @redocly/cli build-docs openapi.yaml --output ./redoc-build/index.html\n\nThe Redocly build writes one self-contained HTML file. Ask your agent to publish it to Display."}]}]

A URL for every API reference you build

Where your engineers
and agents work on the API docs.

One command. Your API documentation becomes an authenticated URL that never changes, accessible to any engineer with a company email.

Try it free See CI setup ↓

Works with your agents

Cursor, Codex, Claude Code – any agent that writes a file. Switch agents anytime – your URLs, versions and comments stay put.

Used by top teams at

The command

"Publish the API docs page to Display for everyone at my company."

Your agent publishes the page and returns the link, for example https://acme.dsp.so/0kzNYG7O-api-docs.

Any @yourco.com email authenticates with one click. No GitHub account. No Vercel project.

The problem

API docs are internal. They need internal auth.

Swagger UI and Redoc turn your OpenAPI spec into a browsable explorer – method by method, parameter by parameter, with live request testing. That explorer is for internal engineers, so it shouldn't be public. Every hosting option that adds auth charges for it in money or in setup.

display.dev publishes the Swagger UI or Redoc page behind Google and Microsoft SSO in 15 seconds. €49/month for the whole company.

✗
Vercel with sign-in
Identity-provider sign-in is an Enterprise feature, and each spec needs its own project.
✗
Behind a VPN
engineers off the office network can't reach it, and mobile access breaks.
✗
S3 + CloudFront + Cognito
Longer setup with IAM policies, repeated for every new spec.
✗
Confluence embed
strips the JavaScript, so "Try it out" stops working.

display.dev vs. alternatives for API doc hosting

	display.dev	Vercel + SSO	Behind VPN	S3 + Cognito
Interactive Swagger UI / Redoc	✅	✅	✅	✅
Google Workspace SSO	✅ Included	Enterprise only	❌	Complex setup
Microsoft 365 SSO	✅ Included	Enterprise only	❌	Complex setup
Setup	Short	Longer, more steps	Longer, more steps	Longer, more steps
Mobile access (no VPN)	✅	✅	❌	✅
Monthly price	€49 flat	Pro per seat, and Enterprise for sign-in	$0 (VPN cost)	$50+/mo + time
Non-engineer access	✅	✅	❌ (VPN)	✅

Generate and publish Swagger UI

Step 1: Generate the Swagger UI build

For a self-hosted Swagger UI:

# Clone Swagger UI
git clone https://github.com/swagger-api/swagger-ui.git
cd swagger-ui
 
# Build with your spec URL
# Then ask your agent to inline the spec, CSS and JS into one HTML file

Or use the CDN-based single-file approach:

 
<!DOCTYPE html>
<html>
<head>
  <link rel="stylesheet" href="https://unpkg.com/swagger-ui-dist/swagger-ui.css">
</head>
<body>
  <div id="swagger-ui"></div>
  <script src="https://unpkg.com/swagger-ui-dist/swagger-ui-bundle.js"></script>
  <script>
    SwaggerUIBundle({
      spec: { /* your OpenAPI JSON */ },
      dom_id: '#swagger-ui',
    })
  </script>
</body>
</html>

Step 2: Publish

"Publish swagger-ui.html to Display for everyone at my company."

Your agent publishes the file and returns the link.

For Redoc:

npx @redocly/cli build-docs openapi.yaml --output ./redoc-build/index.html

The Redocly build writes one self-contained HTML file. Ask your agent to publish it to Display.

CI/CD setup – publish on every spec change

name: Publish API Docs
 
on:
  push:
    paths:
      - 'openapi.yaml'
      - 'openapi.json'
 
jobs:
  publish-docs:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
 
      - name: Build Redoc
        run: |
          npm install -g @redocly/cli
          redocly build-docs openapi.yaml --output ./api-docs/index.html

In the next step, the job calls Display's REST API with DISPLAYDEV_API_KEY from your CI secrets. It publishes the built file as the next version of the same artifact.

Every merge that touches the OpenAPI spec automatically updates the published docs using the artifact ID stored in DISPLAY_ARTIFACT_ID.

Pricing

2 months free

Free

Try it. No credit card.

€0

Included: 3 gated artifacts
Included: Unlimited public artifacts^*
Included: 50MB storage
Not included: Version history
Not included: Google + Microsoft SSO
Not included: Audit logs

display.dev branded

Get started

Solo

Individuals. Unlimited gated sharing.

€15/mo

Included: Unlimited gated artifacts
Included: Unlimited public artifacts
Included: 1GB storage
Included: 10 versions
Not included: Google + Microsoft SSO
Not included: Audit logs

Get started

ProMost popular

For teams who need SSO & audit logs.

€49/mo

Included: Unlimited gated artifacts
Included: Unlimited public artifacts
Included: 25GB storage
Included: 50 versions
Included: Google + Microsoft SSO
Included: 90 days audit logs

Get started

Enterprise

For compliance-driven organizations.

From €499/mo

Included: Unlimited gated artifacts
Included: Unlimited public artifacts
Included: Custom storage
Included: Unlimited versions
Included: Google + Microsoft SSO
Included: 365 days audit logs

Book 20 minutes

Features

Authentication

Viewers click a link and sign in with their Google or Microsoft account, or a one-time password. No app to install. No account to create. No IT ticket.

Comments and edits

Inline comments on every artifact. Your agent reads them via MCP, fetches the current version, republishes with short_id and base_version, and resolves the thread. For a small fix, your team selects Edit and changes the page directly. Every change lands at the same URL.

Publish in 15 seconds

Ask your agent to publish the file to Display, in your terminal or in Claude Desktop. No git repo, no deploy pipeline, no project to configure.

A URL that never changes

Every artifact gets a URL that keeps working. Share in Slack, link in Notion, paste in email. It still works six months later.

Unlimited viewers

No per-seat pricing at any tier. Share with your PM, exec, legal team, or designer for the same flat price.

Any agent

Cursor, Codex, and Claude Code all work, along with any agent that creates HTML or Markdown output.

Try it free

Publish a Swagger UI or Redoc build in 15 seconds, no card
Every engineer signs in with the company account they already use
Unlimited viewers on every plan

Publish your API docs free See pricing

FAQ

Common questions.

Does the "Try it out" feature work in display.dev-hosted Swagger UI?+

Yes, if your API is accessible from the viewer's browser. display.dev serves the Swagger UI as intended – including the live request functionality. CORS on your API must allow requests from acme.dsp.so.

Can I host multiple API versions?+

Yes. Ask your agent to publish the new docs as a separate artifact. Each version gets its own URL. Link them from a changelog page or Notion.

What about private APIs that should only be accessible internally?+

display.dev gates the documentation page – only company emails can view the Swagger UI. The API itself remains on your internal network or behind its own auth. display.dev controls who can read the docs, not who can call the API.

Does display.dev work with AsyncAPI or GraphQL schema docs?+

Any static HTML documentation tool works. AsyncAPI Studio, GraphQL Playground (static export), Redoc, Stoplight Elements – if it builds to one self-contained HTML file, your agent can publish it.

Can I keep my existing Confluence page and link to display.dev for interactive docs?+

Yes. Link from your Confluence doc to acme.dsp.so/0kzNYG7O-api-docs. Confluence gets the searchable, structured context; display.dev hosts the interactive explorer.

Publish your first artifact in 15 seconds.

Free tier. No credit card. One-time password auth on free, Google + Microsoft SSO on Pro (€49/month flat).

Get started free →See pricing