Skip to main content
AI Gateways can register on-chain via the AIServiceRegistry contract using the -aiServiceRegistry flag. Video/transcoding Gateways do not yet have an equivalent on-chain registry - discoverability for video is currently manual and community-driven.A Gateway Explorer Page is in Development:
This guide covers how to make a Gateway reachable and findable, so that other developers and applications can discover and use it.

​
Capability Advertising

Developers choosing a Gateway need to know what it supports. There is no standard machine-readable format for this yet, but publishing a clear capabilities document on the domain is current best practice.
State explicitly whether the Gateway handles:
  • AI inference (and which pipelines: text-to-image, image-to-video, LLM, etc.)
  • Video transcoding
  • Live AI (video-to-video)
  • BYOC pipelines
For AI inference, list the models available via connected Orchestrators. Generate this dynamically from the Gateway’s /getNetworkCapabilities endpoint:
curl https://gateway.example.com/getNetworkCapabilities | \
  jq '[.orchestrators[].capabilities_prices[].model_id] | unique'
Publish customer-facing pricing. The Gateway has two pricing layers:
  • What it pays Orchestrators (-maxPricePerCapability, -maxPricePerUnit) - the cost floor
  • What it charges customers - the business decision
These do not need to match. Most public Gateways add a margin and present pricing in human-readable units (per image, per minute of video) instead of in wei per pixel.
Describe how developers authenticate: API key, OAuth, or open access. If registration is required, link to the signup page.
Document any rate limits and what SLA is offered. Even a best-effort statement (“target 99% uptime”) sets expectations and builds trust.

​
Discovery Methods

These are the mechanisms developers use today to find public Gateways.

​
Marketplace Context

The Livepeer Marketplace is a programmatic interface for Orchestrators to advertise compute and for Gateways to discover and route to that compute. It is not a discovery mechanism for applications to find Gateways. As a Gateway operator, the relationship to the marketplace is as a broker: the Gateway queries it to find Orchestrators, not to list itself for applications to find. The marketplace is upstream of the Gateway, not downstream. 
Applications -> [Gateway] -> Marketplace -> Orchestrators
There is currently no Gateway layer in the marketplace. On-chain Gateway registration (equivalent to how Orchestrators register via ServiceRegistry) is on the roadmap but not yet available.

​
Video Gateways

Video Video Gateways use -serviceAddr differently from AI Gateways. For a Video Gateway, -serviceAddr is the address that the Gateway advertises to Orchestrators so they can report results back. It must be reachable by Orchestrators on the network. This means the Video Gateway’s service address must be publicly reachable on the Gateway’s HTTP port (default 8935). If behind NAT, configure port forwarding or use a server with a public IP. RTMP ingest (port 1935) is separate from the service address and is what video sources connect to. These can be on different ports or even different network interfaces.

​
On-chain Discovery

Gateway Middleware

Auth and routing - prerequisites for a public-facing Gateway.

Opportunities

Revenue models and Foundation support for Gateway operators.

NaaP Multi-Tenancy

Network as a Platform architecture for multi-tenant operation.

Technical Architecture

Network architecture context for how Gateways fit into the ecosystem.
Last modified on March 16, 2026