Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Google Speech to Text API key restrictions? #50

Open
thunderchuck opened this issue Feb 8, 2017 · 1 comment
Open

Google Speech to Text API key restrictions? #50

thunderchuck opened this issue Feb 8, 2017 · 1 comment

Comments

@thunderchuck
Copy link

Hello,

I was just wondering what, if any, restrictions are there with respect to running the script with the included Google Speech to Text API Key? For example, would it be appropriate for business use? Or would that be breaking Google's TOS somehow?

Thanks.
@BingLingGroup
Copy link

BingLingGroup commented Feb 13, 2019 •
edited
Loading

quotas
But these are the docs for cloud speech api. The api used in autosub is some kind of Reverse Engineering:
google-speech-v2
accessing-google-speech-api-chrome-11
Google speech API - Stack Overflow
And the source of the api key is pretty clear, which is from chromium and autosub has used since the repo was created.
Reference: your api key #1
chromium-google-api-keys

@BingLingGroup BingLingGroup mentioned this issue Feb 13, 2019
Open
@BingLingGroup BingLingGroup mentioned this issue Feb 22, 2019
Open
@BingLingGroup BingLingGroup mentioned this issue Mar 18, 2019
Closed
@BingLingGroup BingLingGroup mentioned this issue Nov 10, 2019
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@thunderchuck @BingLingGroup