Skip to main content
Routes expose services running inside your agent container to the internet. Open the Routes section from your agent’s detail page. Click ADD to create a new route:
OptionDescription
Path RouteMap a URL path prefix to a container port
Custom DomainRoute a hostname to a container port

Path Routes

Path routes forward traffic from a URL path to an internal port. The path prefix is stripped before reaching your service. Example: A request to /app/api/users with path prefix /app arrives at your service as /api/users.

Adding a Path Route

FieldDescription
Path PrefixURL path (e.g., /app)
PortContainer port (1025–65535)
ProtectedRequire gateway token authentication

Path Format

  • Must start with /
  • Letters, numbers, hyphens, underscores only
  • Cannot overlap with reserved paths (/v0, /chat, /config)

Custom Domains

Custom Domains is currently in beta.
Custom domains route traffic from a dedicated hostname to a container port. Unlike path routes, the full request path is forwarded as-is.

Pinata Subdomains

Get a random platform-assigned subdomain on *.apps.pinata.cloud.
FieldDescription
PortContainer port (1025–65535)
ProtectedRequire gateway token authentication
Result: https://swift-fox-347.apps.pinata.cloud → your port

Bring Your Own Domain

Use your own domain (e.g., app.example.com).
FieldDescription
DomainYour domain
PortContainer port
ProtectedRequire gateway token authentication

DNS Setup

After registering, configure these DNS records:
  1. TXT record — Verify domain ownership
  2. CNAME record — Point to the Pinata proxy
Domain status progresses: pendingpending_sslactive

Public vs Protected

ModeBehavior
ProtectedRequests require a gateway token
PublicOpen to the internet
Public routes expose your service without authentication. Only use for services that handle their own auth.

Constraints

LimitValue
Path routes per agent10
Custom domains per agent5
Port range1025–65535
Reserved port18789 (gateway)