Luis Out of call volume quota - azure

I have a Luis application and I am using the starter key for development. I am getting
Out of call volume quota. Quota will be replenished in xxxxxxxx.
I know that you have 1000 query per month but I only used 188 ( value on the dashboard). Is there another reason for getting out of Quota?

Are you working with the starter key?
The starter key only allows 1000 calls per month and doesn't work fine.
Here you have an extract from Microsoft FAQ:
Why did I get an email saying I'm almost out of quota?
Your authoring/starter key is only allowed 1000 endpoint queries a month.
Create a LUIS subscription key (free or paid) and use that key when
making endpoint queries. If you are making endpoint queries from a bot
or another client application, you need to change the LUIS endpoint
key there.
Check this to know how to create a LUIS Key.

Related

Binance API : How to get Binance User ID using API

How to get Binance User ID using API. I just created a bot and I need unique value to create a bot activation so a user can use my bot only for that account.
That is why I need a User ID by Binance API. How can I get a User ID or get any other unique value like a User ID by API.
Binance does not share any unique ID of each user, most likely for privacy reasons.
You can partially bypass this limitation by querying balances of each API key. If there are two API keys with the same set of balances, chances are it's the same user. Mind that this solution is not easily scalable. With thousands of users you'll have to run thousands of requests to get their balances. And probably cache these results, so that you don't run into rate limits (number of API requests from your server IP), which introduces another inaccuracies.

Client billing/client usage for microsoft cognitive services speech to text?

I'm working on a website that is supposed to offer users to make use of azures cognitive services api. They can play audio or use their microphone to transform speech into text.
I'm currently using azures js sdk and technically it's working fine. However, I noticed a big shortcoming with this approach. The sdk connects through a websocket with the azure server, which exposes the subscription key to the client. So every member could theoretically read it out and sell it or alike.
Furthermore, if the client connects directly with azure, I have no secure way of preventing clients abusing the service. I need a way to measure roughly how much time a customer uses the service to take into account individual billing.
I could not find anything about that in the official documentation. So what are my options?
Should I redirect the clients' audio input to my own server, do some quantitative analysis, and then forward the input from a server side connection to azure? I fear with many concurrent customers, it might get laggy or connections might get dropped...
Is there any way to attach at least client ids or alike to azure websocket connection that I can read out somehow later?
Do you have any advice for me?
Given your additional comment, I would suggest that you switch your implementation from using subscription key to using authentication tokens.
That would:
generate a unique token for each client, based on 1 global subscription key
not expose your subscription key to your clients
restrict the use of the API, as the token is only valid for 10 minutes
Each access token is valid for 10 minutes. You can get a new token at any time, however, to minimize network traffic and latency, we recommend using the same token for nine minutes.
See documentation here for global implementation. In a nutshell, you need to implement this token generation in your backend, and serve the page to your client with this token instead of the key.
Side note 1: be careful about the maximum number of concurrent requests (100 - see here).
Note 2: that will not help you bill clients given their usage as you have just 1 key and there is no way to identify distinct usages in it

Salesforce functionality limited by Docusign Plan

Testing out the platform I was running on both a developer account and a Trial Business Pro account until I purchased a standard plan.
Up until I purchased the standard plan, envelope statuses would update by the second and the functionality built with the Apex Toolkit was working well.
Once changing to the standard paid plan, envelopes statuses take 10-15 minutes to update and some functionality is not working.
My question is:
Do the different plans have different status updating times in Salesforce?
Is functionality of the Apex Toolkit limited between the different plans?
Does the Connect option (which is missing now) have anything to do with the above?
Thanks!
They do not. Writeback to Salesforce takes place via DocuSign Connect. Some plans don't support Connect out of the box but the actual writeback times / delays do not differ between account plan types.
Indirectly, the only way that a plan type can interfere with an API call that worked on another plan type is if it had entitlement to a feature that your new plan does not, IE: The ability to allow Comments, to set recipient signing language, to set envelopeID Stamp Control, etc...
I would highly suspect that it does -- in fact I'm a little surprised that your writebacks are happening at all if you don't have Connect enabled. Salesforce adds an object reference IE: Opportunity / AccountIds to the envelope's custom fields on send. When Connect sees these fields, it knows to write back to that specific object. Without Connect enabled and configured it shouldn't be able to process these writebacks at all.
I think you should have a conversation with your Account Rep first regarding Connect entitlement, then you can reconnect your Salesforce instances to the updated DocuSign account which is something that we can help you with.
Regards,
Matt

Google Directions API billing

I am implementing an Android app and I want to use the Directions API but I get this error when I try the HTTP GET Request:
{
"error_message" : "You must enable Billing on the Google Cloud Project at https://console.cloud.google.com/project/_/billing/enable Learn more at https://developers.google.com/maps/gmp-get-started",
"routes" : [],
"status" : "REQUEST_DENIED"
}
I know I have to enable billing, what I want to know is the limits. I am doing this app for student purposes so this app won't be used by any users but me. I wanna know If it's safe to put my credit card if there is a limit that you can use it for free. I know there is a free trial but after that any request, even one will cost me money??
Thank you.
If you are using the free GCP tier, the free trial ends when you use all of your credit, or after 3 months, whichever happens first.
At that time, the following conditions apply:
You must upgrade to a paid account to continue using Google Cloud.
All resources you created during the trial are stopped.
Any data you stored in Compute Engine is lost.
Your account enters a 30-day grace period, during which you can recover resources and data you stored in any Google Cloud services during the trial period.
You might receive a message stating that your account has been canceled, which only indicates that your account has been suspended to prevent charges.
If you want to manage your expenses you may set up budget alerts https://cloud.google.com/billing/docs/how-to/budgets#create-budget also you can set up capping usage for it https://cloud.google.com/apis/docs/capping-api-usage

How to get available credits for an Azure Datamarket API Key?

Been using the Bing Search API https://datamarket.azure.com/dataset/5BA839F1-12CE-4CCE-BF57-A49D98D29A44, but I used up all my credits without noticing, and now I am receiving a message like "The number of fobidden or denied requests per minute from the same IP address has reached the maximum threshold that is allowed. Please try again after".
How can I check if an API Key has sufficient transaction credits on the Azure Marketplace?

Resources