One studio, one gateway, every API.
Voice Xpin is the customer-facing studio. Middleware is the governed front door for published APIs, handling identity, metering, permissions, documentation and upstream health while dedicated speech workflows keep their product experience.
How traffic travels
Built-in TTS
The studio validates the user session, calls the Voice API and returns generated audio while keeping engine credentials server-side.
Built-in STT
The studio sends uploaded or recorded audio to Scribe, receives the transcript and stores the product result.
New catalog service
Register an upstream and endpoint in Middleware; the live catalog makes it appear in the API Explorer without a frontend deployment.
What changes when an API is added
Adding a service is a Middleware configuration change. The service becomes visible to Voice Xpin when it is active, has enabled endpoints, and the workspace token or plan has the matching scope.
- 1. Register the upstream base URL, authentication and health path.
- 2. Add endpoint schemas, content types, pricing and scopes.
- 3. Grant the workspace token or plan access.
- 4. Middleware probes the service and publishes the catalog.
- 5. Voice Xpin fetches the catalog and renders the endpoint form automatically.
Status and health monitoring
The public status page probes the studio, Voice API, real TTS synthesis, Scribe, database, object storage and Middleware. Middleware independently probes every active registered upstream.
Public status
The public page reports Middleware health as an aggregate such as “2/2 upstreams up”. Machine monitoring is available at /api/status.
Individual service detail
The Middleware admin console shows each service row, health state and manual probe at middleware.xpin.ae/admin.
Production surfaces
Voice Xpin
Studio · Docs · Status · Status JSON
Source and storage
Staging
No separate staging hostname is configured or verified in the current deployment, so no staging URL is shown here.