Mock sample for your project: NLPCloud API

The current api version is v3.4 The api methods listed below can be called directly from this page to test the output. You might set the api_key to pre-authenticate all requests on this page (this will work if your secret is blank). API endpoint URL: http://{apiName}.text2data.com/v3/ {method} The api can be consumed directly or using our SDK. Our Excel Add-In and Google Sheets Add-on are also using this api to process the data.

Exude API is an Open Source project, It is used for the primary ways for filtering the stopping, stemming words from the text data. This API is in a very basic level of development need to work on for later changes.

The Football Prediction API allows developers to get predictions for upcoming football (soccer) matches, results for past matches, and performance monitoring for statistical models.

For more information on how to use these APIs, including how to create an API key required for authentication, see Alma REST APIs.

The Word Associations Network API allows developers to embed the ability to find associations for a word or phrase into their mobile apps or web services. Words are grouped by semantics, meaning, and psychological perception. The Word Associations Network API currently supports English, French, Spanish, German, Italian, Portuguese, and Russian vocabulary. Please register and subscribe to one of available tariff plans to get a valid API key.

Rev.ai provides quality speech-text recognition via a RESTful API. All public methods and objects are documented here for developer reference.
For a real-time speech to text solution, use Rev.ai's Streaming API.
Base Endpoint
The base url for this version of the API is
> https://api.rev.ai/speechtotext/v1
All endpoints described in this documentation are relative to this base url.
Quick Start
Follow the getting started checklist
Get your Access Token
You can generate your access token on the settings page of your account. This access token only needs to be generated once and never expires. You can re-generate your token, however this will invalidate the previous token.
Submit a File
To submit an audio file for transcription to Rev.ai:
Retrying Failed Requests
Some errors can be resolved simply by retrying the request. The following error codes are likely to be resolved with successive retries.
| Status Code | Error |
|---|:---|
| 429 | Too Many Requests |
| 502 | Bad Gateway |
| 503 | Service Unavailable |
| 504 | Gateway Timeout |
Note: With the exception of the 429 status code, it is recommended that the maximum number of retries be limited to 5 attempts per request. The number of retries can be higher
for 429 errors but if you notice consistent throttling please contact us at.

Below is the documentation for the API calls. You can try them out right here.

Check texts for style and grammar issues with LanguageTool. Please consider the following default limitations: your daily request limit depending on your plan maximum number of requests per minute: 20 (free) / 80 (Premium) maximum number of characters per minute: 75,000 (free) / 300,000 (Premium) maximum number of characters per request: 20,000 (free) / 60,000 (Premium) for the free version, also consider the limitations documented here Note: any parameters or outputs not part of this documentation are internal and must not be relied on Need more generous limits? Just contact us.

NamSor API v2 : enpoints to process personal names (gender, cultural origin or ethnicity) in all alphabets or languages. By default, enpoints use 1 unit per name (ex. Gender), but Ethnicity classification uses 10 to 20 units per name depending on taxonomy. Use GET methods for small tests, but prefer POST methods for higher throughput (batch processing of up to 100 names at a time). Need something you can't find here? We have many more features coming soon. Let us know, we'll do our best to add it!