The Content Origin Authentication API is designed to discern whether textual content comes from an artificial intelligence (AI) model or a human author. With the proliferation of AI-generated content across various platforms and industries, there is an urgent need to authenticate textual content and maintain transparency in communication.
Leveraging sophisticated natural language processing (NLP) methods and machine learning algorithms, the API examines and evaluates the linguistic features of textual passages.
Applicable to a range of applications and industries where the veracity of textual content is important, the API is an essential tool. For example, in the fields of journalism and media, the API helps news organizations and editors discern AI-generated articles or reports without human intervention or editorial oversight. By flagging such content, news outlets maintain their editorial standards and preserve the integrity of their reporting.
In essence, the Content Origin Authentication API provides a powerful solution to validate the credibility of textual content and uncover instances of AI-generated text across multiple applications and industries. Leveraging advanced NLP techniques and machine learning algorithms, the API enables users to cultivate transparency, integrity and trustworthiness in textual exchanges.
It will receive a parameter and provide you with a text.
Besides the number of API calls, there is no other limitation.
To use this endpoint you must indicate text in the parameter.
Content Detection - Endpoint Features
| Object | Description |
|---|---|
text |
[Required] Indicates a text |
{"all_tokens": 31, "used_tokens": 31, "real_probability": 0.9677795767784119, "fake_probability": 0.032220423221588135}
curl --location --request GET 'https://zylalabs.com/api/3911/content+origin+authentication+api/4630/content+detection?text="In the vast expanse of the digital realm, algorithms tirelessly churn out words, weaving a tapestry of ideas and concepts that transcend human limitations."' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The Content Origin Authentication API determines whether a given text was written by a human or generated by an artificial intelligence model.
Users only need to enter a text.
There are different plans suits everyone including a free trial for small amount of requests, but it’s rate is limit to prevent abuse of the service.
Zyla provides a wide range of integration methods for almost all programming languages. You can use these codes to integrate with your project as you need.
The Content Detection endpoint returns a JSON object containing probabilities indicating whether the text is AI-generated or human-written.
The key fields in the response include "real_probability," which indicates the likelihood of the text being human-written, and "fake_probability," which shows the likelihood of it being AI-generated.
The response data is structured in a JSON format, with fields clearly labeled to indicate the probabilities of the text being real or fake, making it easy to interpret.
The primary parameter for the Content Detection endpoint is the text input, which users must provide to analyze its origin.
Users can utilize the returned probabilities to assess the authenticity of the text. A higher "real_probability" suggests the text is likely human-written, while a higher "fake_probability" indicates AI generation.
The Content Detection endpoint provides information on the likelihood of text being AI-generated or human-written, which is crucial for applications in media, academia, and content moderation.
Data accuracy is maintained through advanced natural language processing techniques and machine learning algorithms that continuously learn from new text samples to improve detection capabilities.
Typical use cases include verifying news articles for authenticity, ensuring academic integrity in research papers, and moderating user-generated content on platforms to prevent misinformation.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Service Level:
100%
Response Time:
903ms
Service Level:
100%
Response Time:
7,340ms
Service Level:
100%
Response Time:
691ms
Service Level:
100%
Response Time:
1,116ms
Service Level:
90%
Response Time:
721ms
Service Level:
100%
Response Time:
137ms
Service Level:
100%
Response Time:
814ms
Service Level:
100%
Response Time:
262ms
Service Level:
100%
Response Time:
881ms
Service Level:
100%
Response Time:
672ms
Service Level:
100%
Response Time:
5,411ms
Service Level:
100%
Response Time:
14,851ms
Service Level:
100%
Response Time:
1,718ms
Service Level:
100%
Response Time:
1,347ms
Service Level:
100%
Response Time:
54ms
Service Level:
100%
Response Time:
55ms
Service Level:
100%
Response Time:
2,957ms
Service Level:
100%
Response Time:
649ms
Service Level:
100%
Response Time:
1,738ms
Service Level:
100%
Response Time:
6,199ms