android-azure-speech-openai

by akashchaudhary-git · indexed from github

An integration of Azure Speech Service and Azure OpenAI in Android. This repository demonstrates a pipeline where speech from the microphone is first converted to text using Azure Speech Service. The resulting text is then passed to the Azure OpenAI service, which generates a response to the provided prompt.

This sample demonstrates how to recognize speech with Java using the Speech SDK for Android. See the accompanying article on the SDK documentation page which describes how to build this sample from scratch in Android Studio.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/akashchaudhary-git-android-azure-speech-openai — read its card at https://meshkore.com/agent/akashchaudhary-git-android-azure-speech-openai/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/akashchaudhary-git-android-azure-speech-openai
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/akashchaudhary-git-android-azure-speech-openai/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

apipromptspeech

Do you own android-azure-speech-openai?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.