Luis is no longer free ?
I didn't open LUIS dashboard for 10-11 days. I'm seeing this now. They changed a lot of things there.
I must get azure key to get my LUIS app works ?
According to the pricing details, LUIS is not free. You are able to make 10K calls per month without charge, after which you are charged $0.75 per 1000 calls. Without more detail I am unsure of your second question. An azure key may be used to link LUIS to your bot.
Just to clarify LUIS has the same model as before, the new portal just highlights this information in a different way that's a little more confusing (we're working on it).
No Azure Account; free for 1000 requests/month using programmatic api key
With Azure, free for 10,000 requests per month (F0 plan in Azure)
With Azure, $.75/1000 calls
The thing that's new and confusing is the programmatic key with the low quota isn't connected to your app by default. We're going to fix that shortly.
Same happened to me. I had to create LUIS app in Azure and then provide key to LUIS application on LUIS.ai. But in LUIS app on azure, you can select the pricing tier as free if 10k calls per month suffice your application usage or choose paid plan according to need.
A start-key is default available with each LUIS model which can be used upto 10k calls per month
LUIS is free for Testing and Educational use. It is about 10000 conversations per month. However in production environment it has to be paid.
The important this is you can access LUIS feature via Azure or can independently integrate it into your application. The method of costing will depend on that as well.
Related
I need to create a scheduler for my own SaaS, and I'm trying to understand whether Google Calendar API is a fit for that. Basically I could have hundreds of thousands of calendars. Each calendar may be a user of my service, but not a Google user. It seems that perhaps I could use resource calendars under my Google Cloud service account. My biggest concern is whether my usage will fall within the Calendar API's service quotas, either automatically or by requesting a quota increase?
Yes service accounts will fall within quota usage limits. There is also a limit about creating more then 25 calendars in a day causing the user to end up in read mode for the rest of the day.
pricing
Google Calendar API Usage Limits
The Google Calendar API has a courtesy limit of 1,000,000 queries per day.
To view or change usage limits for your project, or to request an increase to your quota, do the following:
If you don't already have a billing account for your project, then create one.
Visit the Enabled APIs page of the API library in the API Console, and select an API from the list.
To view and change quota-related settings, select Quotas. To view usage statistics, select Usage.
On the one hand, you could work around the quota issues by sharding your users across multiple Service Accounts. You would probably also want to shard them across multiple App IDs.
On the other hand, don't do it. In my experience, using Google APIs outside their intended use case doesn't end well.
I started receiving this message from when querying LUIS using the starter key, however, I reached only 600 hits to the end point so far as per the dashboard across all apps (the limit is 1000 right?).
I added a new key using an azure subscription, but the docs say that when developing or authoring, I should be using the authoring key. My questions are:
1- How am I getting this error when I just reached 700 hits only across all my LUIS apps.
2- if I want to use the new endpoint key, do I do development/testing using this key since I can't use the authoring one for now? What's the best practice in this case?
Reaching the quota:
The quota is about several things:
global usage
per second/minute usage
You probably have reached the quota per second? Moreover, the value of number of hits on the portal may not be working, I already had a LUIS projects showing 0 hits for weeks whereas it was used.
You will found below the values:
Link: Microsoft documentation about limits here
Using new key
You should use an endpoint key when you just query LUIS. From the documentation:
LUIS uses two keys: authoring and endpoint. The authoring key is
created for you automatically when you create your LUIS account. When
you are ready to publish your LUIS app, you need to create the
endpoint key, assign it to your LUIS app, and use it with the endpoint
query.
I am currently using Kinvey only for the business logic. Everything else I am using other services. It seemed that I must be logged in to use business logic so I made one account and made the user register to that account when opening the app. I am confused if that will be an okay approach since I believe I saw on another post that after so many downloads, it will raise a flag on Kinvey's side. Is that true? I also just saw these images in the users section and am not sure what this means.
[
[
To answer your question about pricing, you can review our pricing plans at https://www.kinvey.com/pricing/.
Kinvey monitors customers in the free developer plan to check if their usage exceeds the limits. We do this by checking API calls per month, number of active users, data/file storage used etc for your kid - not by App Store downloads.
If that happens, Kinvey support or sales will reach out to you to help you transition to the next pricing tier or help you to reduce your consumption with optimization or other options.
Your queries about master secret, authentication are best answered in this Kinvey security guide: http://devcenter.kinvey.com/rest/guides/security
Regards,
Wani
Kinvey Support
I recently started an internship concerning Master Data Management in Talend. Part of the Master Data Management proces involves the cleansing of data. In my case I have to cleanse a few addresses. After doing some research I bumped into the Google Places API, which would do the trick for me. At first I wasn't aware of the so called quota limits that are bound to this API so I decided to read up on it some more. Basicly I have quite a few addresses to cleanse, so the 1000 requests per day limit won't cut it. As of yesterday I decided to increase that limit to 150 000 requests by verifying my identity using my creditcard. The requests were indeed increased to 150 000 but after a few hours my billing account was closed without warning and the limit went back to 1000 requests.
My question is: is the increase of the quota limit only available for businesses or are individual users eligible for it too?
I basicly filled in my own name as the name of the business when I created the billing account for my own project. That billing account is closed now. I really need that quota increase to be able to finish my project so I'm wondering if you guys are able to enlighten me. The image below is part of the form which has to be filled in to create a billing account.
for this amount of quota you have to identify yourself through your credit card and thats it. you can use this key for personal use or business does not matter . as the whole app has that much of search quota. no matter how many people install that app.
so the answer is it is eligible for individual users too.
thank you
You may have different terms in your country. We don't have VAT in the US, although we do have state-specific sales tax on some goods and services. I suspect that Google cannot offer this service in your country without a business tracking the VAT for it. I use the Google Search API with Custom Search Engines on both personal and business accounts from the US with just CC validation. You might look to see if there are Google services resellers local to you who can offer you the Place API.
I want to set up a Windows Azure account.
I'm an MSDN Subscriber so I get it for "free" the first 16 months.
Still, Microsoft want my credit card number just in case I go over the free limit.
In theory, this means I'm writing a carte blanche to MS to bill my credit card.
I want to know if anyone has been using Azure and if there's anyway of setting it to simply stop working if it gets near the cap where it would start to cost me something??
Today, there are no usage caps you can place on your account. Regarding the credit card and carte blanche ability to bill you: you'd only be billed for overage beyond the "free" stuff. Microsoft recently instituted an email-alert feature that lets you know when you've used 75% of your available resources. I believe that went live a few weeks ago.
Simply put: you get 750 compute-hours monthly (metered on a 1-hour boundary). This gives you enough hours to run a single, small instance 24x7, as there are just under 750 hours in a month. If you leave two instances running full-time, you'll go over your allotment and be charged.
If you're just learning, the MSDN account is fantastic. Just remember to delete your deployment at the end of the day (or when you're done trying something out), instead of letting it run 24x7. With a bit of prudence, you'll easily be able to test multi-instance applications and avoid ever being charged.
You can also log into the billing portal from the Azure portal. This shows a very detailed breakdown of your monthly usage, and with a quick scan you'll see how you're doing regarding compute-hours.
I keep mentioning compute-hours but not storage or bandwidth. Unless you're doing some extreme development, I doubt you'll run into any storage or bandwidth overruns. Same goes for SQL Azure - stick with Web Edition databases (and only 3 databases) and you'll have no issue there.
I wrote two blog posts that might also be helpful when thinking about how to manage cost so you don't get charged:
The True Cost of Web and Worker Roles
Staging and Compute-Hour Metering
In addition to David's answer, I would also suggest maximizing your use of the local Azure runtime that comes with the SDK. You can create web & worker roles and blobs/tables/queues. Iterate there until you are happy with how everything works - then publish to the public cloud.
There is no charge for the SDK or the local runtime.
The December 2011 release of Windows Azure introduced a much revamped billing portal which, amongst other things, introduced the ability to cap spend on introductionary accounts and MSDN accounts.
Whilst you still need to provide credit card for your MSDN Account, all accounts are automatically created with spending limit of $0; a limit one can remove from the billing portal.
See - http://www.brianhprince.com/post/2011/12/20/New-Sign-Up-for-Windows-Azure-and-Spending-Caps.aspx