Introduction

Let’s upgrade…

We propose 3 billing plans, each for a specific purpose:

PlanPurposePayment model
TestTry our API, learn all details of use, develop and test the integration.Free
BusinessUse the integration of your system and the GoSpeech SaaS application.- Prepaid tiered quota prices (optional) - Possibility of pay per use and billing at the end of the month
EnterpriseUse GoSpeech API in an on-premise environment.Monthly payment for the on-premise instance. Find out more at Enterprise.

When you start your working with our API (see Quick start) and the request for a Developer account is confirmed you´ll automatically get access to Test billing plan.

📘

Note

Don't confuse developer billing plans with regular user billing plans. Read more about regular user billing plans.

Compare plans

Features

Test

Business

Enterprise

Limits

Speech recognition

Mocked

Real

Real

Number of calls

1000 calls/day
10000 calls/month

No limits

No limits

Single upload limit

10 MB

No limits

No limits

API possibilities

Upload a file

✔️

✔️

✔️

Retry to recognize

✔️

✔️

✔️

Get Records list

✔️

✔️

✔️

Get status update

✔️

✔️

✔️

Get Transcript

.json, .docx, .txt, .pdf

.json, .docx, .txt, .pdf

.json, .docx, .txt, .pdf

Edit record title

✔️

✔️

✔️

Load keywords

✔️

✔️

✔️

Delete record

✔️

✔️

✔️

Create Managed User

✔️

✔️

✔️

Edit managed user

✔️

✔️

✔️

View all managed users

✔️

✔️

✔️

Delete managed user

✔️

✔️

✔️

Change email notifications

✔️

✔️

✔️

Developer functionality

Integration configuration

✔️

✔️

✔️

View usage history

✔️

Server hosting

On-premise

✔️


📘

Note

We highly recommend to create two separate Developer accounts to not mix prod and test data. Consequently create one for testing purposes with Test plan, and another one for production with Business plan.


📘

Note

There are no Test or Business plans on Enterprise installation. If you want to test the integration, it might lead to speech recognition consumption and respective costs for your enterprise server. As a workaround for integration testing we recommend to use a developer account with Test plan on our SaaS environment.