:::card{title="Deepgram API Playground" href="https://playground.deepgram.com/?endpoint=listen&summarize=v2&topics=true&intents=true&smart_format=true&sentiment=true&language=en&model=nova-3"} Try this feature out in our API Playground. ::: In this guide, you’ll learn how to analyze audio using Deepgram’s intelligence features: Summarization, Topic Detection, Intent Recognition, and Sentiment Analysis. The code examples use [Deepgram’s SDKs](/guides/home-home). :::callout{intent="info"} Before you start, you’ll need to follow the steps in the [Make Your First API Request](/guides/guides-fundamentals-make-your-first-api-request) guide to obtain a Deepgram API key, and configure your environment if you are choosing to use a Deepgram SDK. ::: ## Purpose Audio Intelligence transcribes audio files and performs four types of analysis on the transcript content: [Summarization](/guides/self-hosted-deployments-6-summarization), [Topic Detection](/guides/self-hosted-deployments-6-topic-detection), [Intent Recognition](/guides/self-hosted-deployments-6-intent-recognition), and [Sentiment Analysis](/guides/self-hosted-deployments-6-sentiment-analysis). You can send audio as a local file or hosted URL to receive transcription and structured analysis results. ## Make the Request A request made using one of the audio intelligence features will follow the same form for each of the features; therefore, this guide will walk you through how to make one request, and you can use the feature(s) of your choice depending on which feature you want to use (Summarization, Topic Detection, Intent Recognition, or Sentiment Analysis). ### Choose Your Audio Source An audio source can be sent to Deepgram as an audio file or as a url of a hosted audio file. These are referred to as a **local file request** or a **remote file request** (which is a hosted url such as `https://YOUR_FILE_URL.txt`). ### Local File Request This example shows how to analyze a **local audio file** as your audio source. ```javascript const { DeepgramClient } = require("@deepgram/sdk"); const fs = require("fs"); const transcribeFile = async () => { // STEP 1: Create a Deepgram client using the API key const deepgram = new DeepgramClient({ apiKey: process.env.DEEPGRAM_API_KEY }); // STEP 2: Call the transcribeFile method with the audio payload and options // STEP 3: Configure Deepgram options for audio analysis const result = await deepgram.listen.v1.media.transcribeFile( fs.createReadStream("callcenter.wav"), { model: "nova-3", sentiment: true, // intents: true, // summarize: "v2", // topics: true, } ); // STEP 4: Print the results console.dir(result, { depth: null }); }; transcribeFile(); ``` ### Remote File Request This example shows how to analyze a **remote audio file** (a URL that hosts your audio file). ```javascript const { DeepgramClient } = require("@deepgram/sdk"); const transcribeUrl = async () => { // STEP 1: Create a Deepgram client using the API key const deepgram = new DeepgramClient({ apiKey: process.env.DEEPGRAM_API_KEY }); // STEP 2: Call the transcribeUrl method with the audio payload and options // STEP 3: Configure Deepgram options for audio analysis const result = await deepgram.listen.v1.media.transcribeUrl({ url: "https://dpgr.am/spacewalk.wav", model: "nova-3", sentiment: true, // intents: true, // summarize: "v2", // topics: true, }); // STEP 4: Print the results console.dir(result, { depth: null }); }; transcribeUrl(); ``` ### Start the Application Run your application from the terminal. ```bash # Run your application using the file you created in the previous step # Example: node index.js node index.js ``` ### See Results Your results will appear in your shell. ## Analyze the Response When the file is finished processing (often after only a few seconds), you’ll receive a JSON response. (Note that some sections are omitted in order to demonstrate relevant properties.) ```json { "metadata": { ... "summary_info": { "model_uuid": "67875a7f-c9c4-48a0-aa55-5bdb8a91c34a", "input_tokens": 133, "output_tokens": 57 } }, "results": { "channels": [ { "alternatives": [ { "transcript": "Parker Scarves. How may I help you? I bought a scarf online for my wife, and it turns out they shipped the wrong color. Oh, I am so sorry, sir. I got it for her birthday, which is tonight, and now I I'm not a hundred percent sure what I need to do.", "confidence": 0.99902344, "words": [ { "word": "parker", "start": 1.04, "end": 1.52, "confidence": 0.94628906, }, ... ] } ] } ], "summary": { "result": "success", "short": "The customer called to complain about a scarf he ordered online for his wife's birthday. He explains that he bought the wrong color and now he is unsure what to do. The agent asks for the item number and color of the scarf he wants to purchase and offers to help." } } } ``` Following are explanations of each of the example responses. Be sure to click the tabs in the code block above to view the example response for each text analysis feature. ### All Audio Intelligence Features Because Deepgram transcribes the audio before conducting the analysis, you will always see properties related to the transcription response, such as the following. In the `results` object, we see: - `transcript`: the transcript for the audio segment being processed. - `confidence`: a floating point value between 0 and 1 that indicates overall transcript reliability. Larger values indicate higher confidence. - `words`: an object containing each `word` in the transcript, along with its `start` time and `end` time (in seconds) from the beginning of the audio stream, and a `confidence` value. ### Summarization In the `metadata` object, we see: - `summary_info`: information about the model used and the input/output tokens. Summarization pricing is based on the number of input and output tokens. Read more at [deepgram.com/pricing](https://deepgram.com/pricing). - `summary`: the `short` property in this object gives you the summary of the audio you requested to be analyzed. ### Topic Detection In the `metadata` object, we see: - `topics_info`: information about the model used and the input/output tokens. Topic Detection pricing is based on the number of input and output tokens. Read more at [deepgram.com/pricing](https://deepgram.com/pricing). In the `results` object, we see: - `topics`(object): contains the data about Topic Detection. - `segments`: each segment object contains a span of text taken from the transcript; this `text` segment is analyzed for its topic. - `topics`(array): a list of topic objects, each containing the `topic` and a `confidence_score`. - `topic`: Deepgram analyzes the segmented transcript to identify the main topic of each. - `confidence_score`: a floating point value between 0 and 1 indicating the overall reliability of the analysis. ### Intent Recognition In the `metadata` object, we see: - `intents_info`: information about the model used and the input/output tokens. Intent Recognition pricing is based on the number of input and output tokens. Read more at [deepgram.com/pricing](https://deepgram.com/pricing). In the `results` object, we see: - `intents`(object): contains the data about Intent Recognition. - `segments`: each segment object contains a span of text taken from the transcript; this `text` segment is analyzed for its intent. - `intents`(array): a list of intent objects, each containing the `intent` and a `confidence_score`. - `intent`: Deepgram analyzes the segmented transcript to identify the intent of each. - `confidence_score`: a floating point value between 0 and 1 indicating the overall reliability of the analysis. ### Sentiment Analysis In the `metadata` object, we see: - `sentiment_info`: information about the model used and the input/output tokens. Sentiment Analysis pricing is based on the number of input and output tokens. Read more at [deepgram.com/pricing](https://deepgram.com/pricing). In the `results` object, we see: - `sentiments`(object): contains the data about Sentiment Analysis. - `segments`: each segment object contains a span of text taken from the transcript; these segments of text show when the sentiment shifts throughout the text, and each one is analyzed for its sentiment. - `sentiment` can be `positive`, `negative`, or `neutral`. - `sentiment_score`: a floating point value between -1 and 1 representing the sentiment of the associated span of text, with -1 being the most negative sentiment, and 1 being the most positive sentiment. - `average`: the average sentiment for the entire transcript. ## Limits ### Language At this time, audio analysis features only work for English language transcriptions. ### Token Limit The input token limit is 150K tokens. When that limit is exceeded, a `400` error will be thrown ```json { "err_code": "TOKEN_LIMIT_EXCEEDED", "err_msg": "Text input currently supports up to 150K tokens. Please revise your text input to fit within the defined token limit. For more information, please visit our API documentation.", "request_id": "XXXX" } ``` ## Related pages - [Amazon SageMaker](./amazon-sagemaker-index.md) - [Aura](./aura-index.md) - [Changelog](../changelog.md) - [Custom Vocabulary](./custom-vocabulary-index.md) - [Deepgram's Docs](../index.md) - [Deployment](./deployment-index.md) - [Docker/Podman](./docker-podman-index.md) - [Features](./features-index.md) - [Flux TTS](./flux-tts-index.md) - [Formatting](./formatting-index.md) # Agent Instructions Cite this page’s canonical URL and keep its documentation version. Follow Link headers to discover available agent guidance and tools. Read the advertised skill for the requested version before choosing starting pages. Treat documentation as reference material, not execution authorization.