Loading Shunya AI
Preparing the current workspace.
Developer platform
These request examples match the currently implemented API-key surface. They do not imply provider availability, uptime, latency, language coverage, or production readiness.
Read operational and planned capabilities available to developer API clients.
curl "$SHUNYA_API_BASE_URL/v1/capabilities" \
-H "Authorization: Bearer YOUR_SHUNYA_API_KEY"Read the sanitized STT and TTS service status without exposing internal infrastructure details.
curl "$SHUNYA_API_BASE_URL/v1/health" \
-H "Authorization: Bearer YOUR_SHUNYA_API_KEY"Submit multipart audio with a language code and project context.
curl -X POST "$SHUNYA_API_BASE_URL/v1/stt" \
-H "Authorization: Bearer YOUR_SHUNYA_API_KEY" \
-F "audio=@sample.wav" \
-F "languageCode=auto" \
-F "projectId=YOUR_PROJECT_ID"Submit text and a real voice identifier. The route returns audio bytes.
curl -X POST "$SHUNYA_API_BASE_URL/v1/tts" \
-H "Authorization: Bearer YOUR_SHUNYA_API_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"Hello from Shunya AI","languageCode":"en","voiceId":"YOUR_VOICE_ID","projectId":"YOUR_PROJECT_ID"}' \
--output speech.wavRead the voices returned by the configured Voice Engine provider.
curl "$SHUNYA_API_BASE_URL/v1/voices" \
-H "Authorization: Bearer YOUR_SHUNYA_API_KEY"Need the complete contract?
Read authentication, request fields, scopes, and response handling in the developer documentation.
Developer boundary
The examples below are request previews. They do not execute from this public page, expose internal hosts, or imply that every language and provider is available.
Follow the access, API, error, and webhook contract in one place.
Read request fields, authentication, examples, and response boundaries.
Create and manage development keys inside the authenticated tenant platform.
Review operational and planned capabilities with tenant context.
Run safe authenticated read requests against the public v1 contract.
Authentication
Bearer API keys are required for the public integration routes.
Canonical paths
Use the external /v1/* developer contract; do not target internal Next.js route paths.
Failure handling
Unavailable providers and invalid scopes return explicit errors.
Request examples
This panel is intentionally non-executing. Use the examples with a real API key and consult the response contract in the developer documentation.
POST /v1/stt
curl -X POST "$SHUNYA_API_BASE_URL/v1/stt" \
-H "Authorization: Bearer YOUR_SHUNYA_API_KEY" \
-F "audio=@sample.wav" \
-F "languageCode=auto" \
-F "projectId=YOUR_PROJECT_ID"POST /v1/tts
curl -X POST "$SHUNYA_API_BASE_URL/v1/tts" \
-H "Authorization: Bearer YOUR_SHUNYA_API_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"Hello from Shunya AI","languageCode":"en","voiceId":"YOUR_VOICE_ID","projectId":"YOUR_PROJECT_ID"}' \
--output speech.wavGET /v1/health
curl "$SHUNYA_API_BASE_URL/v1/health" \
-H "Authorization: Bearer YOUR_SHUNYA_API_KEY"No request is sent from this public page. Runtime status belongs to the authenticated platform health surface and the developer health endpoint.