Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.meshrouter.app/llms.txt

Use this file to discover all available pages before exploring further.

​
Canonical domains

SurfaceURL
Web consolehttps://meshrouter.app
APIhttps://api.meshrouter.app
Docshttps://meshrouter.app/docs
Statushttps://status.meshrouter.app

​
SDK values

OPENAI_BASE_URL=https://api.meshrouter.app/v1
OPENAI_API_KEY=mesh_live_...
MESH-specific SDKs use MESH_API_KEY by convention: 
MESH_API_KEY=mesh_live_...

​
Wallet onboarding

The web console uses Privy to bootstrap accounts before the user creates a MESH API key: 
NEXT_PUBLIC_MESH_PRIVY_APP_ID=...
PRIVY_APP_ID=...
PRIVY_JWT_VERIFICATION_KEY=...
PRIVY_JWT_VERIFICATION_KEY can be replaced with PRIVY_JWKS_URL when the runtime should fetch and cache the Privy JWKS. Use the same Privy app ID on the Vercel site and AWS API.

​
Routing credentials

Routing credentials are configured at deploy time and never appear in client applications. Application code only needs a mesh_live_... API key — pick a model from the MESH catalogue and call the API. /v1/providers/health and /v1/providers/config are admin-only endpoints that return redacted, non-secret routing data; they are not part of the per-request flow.