Deepgram STT Action

This action facilitates speech-to-text conversion through Deepgram API integration, permitting the conversion of spoken audio to the text equivalent for interactions. As part of the contrib action group, it is configured as a singleton. The package requires Jivas library version 2.0.0 and above.

Package Information

• Name: jivas/deepgram_stt_action
• Author: V75 Inc.
• Architype: DeepgramSTTAction

Meta Information

• Title: Deepgram STT Action
• Group: core
• Type: action

Configuration

• Singleton: true

Dependencies

• Jivas: ^2.0.0

---

Best Practices

• Validate your API keys and model parameters before deployment.
• Test pipelines in a staging environment before production use.

---

🔰 Contributing

• 🐛 Report Issues: Submit bugs found or log feature requests for the deepgram_stt_action project.
• 💡 Submit Pull Requests: Review open PRs, and submit your own PRs.

Contributing Guidelines

1. Fork the Repository: Start by forking the project repository to your GitHub account.
2. Clone Locally: Clone the forked repository to your local machine using a git client.

   git clone https://github.com/TrueSelph/deepgram_stt_action
   

3. Create a New Branch: Always work on a new branch, giving it a descriptive name.

   git checkout -b new-feature-x
   

4. Make Your Changes: Develop and test your changes locally.
5. Commit Your Changes: Commit with a clear message describing your updates.

   git commit -m 'Implemented new feature x.'
   

6. Push to GitHub: Push the changes to your forked repository.

   git push origin new-feature-x
   

7. Submit a Pull Request: Create a PR against the original project repository. Clearly describe the changes and their motivations.
8. Review: Once your PR is reviewed and approved, it will be merged into the main branch. Congratulations on your contribution!

Contributor Graph

🎗 License

This project is protected under the Apache License 2.0. See LICENSE for more information.

0.0.3 → This Version

• Added check for API key in invoke

All Changes

0.0.1

• Initialized package using jvcli

0.0.2

• Updated healthcheck routine to directly test validity of API key
• Uppdated Readme

0.0.3

• Added check for API key in invoke