Documentation Index
Fetch the complete documentation index at: https://docs.livepeer.org/llms.txt
Use this file to discover all available pages before exploring further.
Building a multi-tenant AI video application on Livepeer means solving three infrastructure problems before you write a single line of product code: authenticating your users, metering their usage, and signing probabilistic micropayment tickets on their behalf. pymthouse solves all three as a hosted or self-hosted service. pymthouse is a community project by John (@eliteprox), an active Livepeer orchestrator operator and go-livepeer contributor. The platform is open source, self-hostable, and free to use during beta.
Core capabilities
pymthouse provides three integrated services that Livepeer application developers would otherwise build from scratch. Identity and authentication - pymthouse runs a full OpenID Connect (OIDC) provider. Your application registers as an OIDC client, and pymthouse issues scoped short-lived tokens for your end users. This implements RFC 8693 token exchange, meaning it slots into existing OAuth 2.0 flows. Admin authentication usesnext-auth with Google, GitHub, or Bearer token options.
Multi-tenant billing - Each developer application on pymthouse gets its own isolated OIDC client namespace, user registry, and billing plan. Plans are configurable as free, subscription, or usage-based. The Builder API lets you provision users and record usage against per-user ledgers, denominated in wei to match the on-chain payment unit and avoid floating-point precision loss.
Remote payment signing - pymthouse proxies signing operations to a go-livepeer signer sidecar. Your application calls one endpoint; pymthouse authenticates the caller, signs the Livepeer probabilistic micropayment ticket, records usage, and returns the result. The audit trail is maintained in the usage ledger.
The following diagram shows the request flow for a typical user-initiated AI inference call routed through pymthouse.
System architecture
pymthouse is built on Next.js (App Router) with a PostgreSQL database managed via Drizzle ORM. Thego-livepeer remote signer runs as a Docker sidecar or external service, communicating with pymthouse over a local HTTP API.
The recommended deployment splits the Next.js app to Vercel and the go-livepeer signer to a container host (Railway, Render, or Fly.io). A Dockerfile.signer, railway.json, and render.yaml are included in the repository for each target.
Key API endpoints
pymthouse exposes four API surfaces. All use OAuth 2.0 client credentials (RFC 6749) for machine authentication. OIDC endpoints at/api/v1/oidc - Standard OpenID Connect discovery, JWKS, authorisation, token, and UserInfo endpoints. Use the discovery document (/.well-known/openid-configuration) in production integrations to avoid path drift between versions.
Builder API at /api/v1/apps/{clientId}/users - Confidential client API for provisioning end users, minting short-lived scoped tokens, and managing user attributes within a specific app namespace.
Usage API at /api/v1/apps/{clientId}/usage - Read-only, tenant-scoped endpoint for billing dashboards and per-user cost attribution. Monetary totals are returned as decimal strings of wei - parse with a BigInt-capable library.
Signer proxy - Accepts signed inference or transcoding requests, forwards to the go-livepeer signer, and writes usage records on each call.
Getting started
pymthouse is available as a hosted service (free during beta) and as a self-hosted open-source deployment. Hosted - Create an account at pymthouse.com, register your application in the dashboard, and integrate the Builder API. Time to first token is under five minutes. Self-hosted - Clone the repository, configure environment variables (see.env.example), run database migrations, seed OIDC signing keys, and start the go-livepeer signer sidecar. Full deployment instructions are in DEPLOYMENT.md and docs/vercel-deployment.md.
The OIDC seed command initialises JWT signing keys required before any token issuance:
Resources
Related pages
AI authentication guide
Set up API authentication for AI inference requests in your Livepeer application.
Production checklist
Review the operational checks before moving an AI integration into production traffic.
NaaP - Network as a Platform
Plugin-based network portal for developers and operators building on Livepeer AI compute.
Builder opportunities
Explore grants, RFPs, and open-source contribution paths for ecosystem builders.