How to sign up for the Text Analytics API
Text Analytics resources are available 24-7 in the cloud. Before you can upload your content for analysis, you must sign up to get an access key. Each call to the API requires an access key on the request.
Start with an Azure Subscription. You can create a free account to experiment at no charge.
Create a Cognitive Services API account, choosing the Text Analytics API. Your key is generated when you sign up.
For Text Analytics, there is a Free tier for exploration and evaluation, and billable tiers for production workloads. You can have multiple sign-ups in each subscription: one free, one paid, and so forth. You can switch to a tier offering more transactions if your request volume increases.
There is no service level agreement for services in Preview or the free tier. For more information, see SLA for Cognitive Services
How to change tiers
Start with a Free tier and then transition to a billable tier for production workloads. Standard billing is offered at graduated levels. You can switch tiers and still keep the same endpoint and access keys.
Click Price tier.
Choose a tier and click Select. The new limits take effect as soon as the selection is processed.
How billing works
Billing is based on the number of transactions. You can purchase a block of transactions at a specific tier in a monthly billing cycle, and then if you go over, a small overage charge is applied per transaction. If you routinely go over the maximum limit, consider switching to a higher tier.
Please see the pricing page for more information.
What constitutes a transaction in the Text Analytics API?
Any annotation to a document counts as a transaction. Batch scoring calls will also take into consideration the number of documents that need to be scored in that transaction. So for instance, if 1,000 documents are sent for sentiment analysis in a single API call, that will count for 1,000 transactions.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.