Skip to main content
Domains let you route a hostname to a service running in a MeshAgent room (see Services Overview). This gives you a stable URL for a UI, webhook, or integration. A “route” is the mapping between a domain, a room, and a published port. Routes are managed via the MeshAgent CLI.

​
What problem this solves

You have something running inside a room and want a stable URL for it. Routes connect a public hostname to the exact room and port where that service listens.

​
How the pieces relate

  • Service runs inside a room and listens on an HTTP port.
  • Published port makes that HTTP port reachable from outside MeshAgent.
  • Route maps a domain to the room + published port.

​
Create a route (CLI)

​
Use a MeshAgent-managed domain (*.meshagent.app)

  1. Deploy a service that exposes an HTTP endpoint and marks its port as published.
  2. Create a route:
meshagent route create --room my-room --port 8000 --domain my-app.meshagent.app
  1. The hostname is ready once the route is created (no DNS changes required).

​
How to mark a port as published

In your service config, the HTTP port must be marked as published: 
ports:
  - num: 8000
    type: http
    published: true

​
Common use cases

  • Shareable URLs for demos or internal tools.
  • Stable endpoints for external integrations.
  • Dedicated URLs for room-specific web apps.

​
Access control note

If the published port is not public, requests must include a participant token. This lets you keep a stable URL while still requiring authentication.