About the API:
The Papermill Text Comparison API is a tool designed to help detect cases of potential misconduct in academic publishing. It compares papers submitted to a database of previously submitted papers, known as "papermill-products," to identify similarities and alert users to possible instances of plagiarism or other forms of misconduct.
One important note is that the output of this API should not be considered evidence of misconduct. Instead, it serves as a helpful tool to flag potential issues that require further investigation.
The API takes article metadata as input and classifies articles into three categories: red, orange, and green. A "red" classification means that the query article is highly similar to past papermill-papers, while an "orange" classification indicates that there is some degree of similarity. A "green" classification means that no similar past papermill-papers are known.
The Papermill Text Comparison API can be used by academic publishers, universities, and other organizations to help ensure the integrity of their research publications. By identifying potential instances of misconduct early on, the API can help prevent issues such as plagiarism from going unnoticed.
It is worth noting that the API should be used as one tool in a broader suite of measures to ensure the integrity of academic publications. While the API can help detect potential issues, it cannot replace the need for thorough peer review and other forms of quality control.
Overall, the Papermill Text Comparison API is a valuable tool for academic publishers, researchers, and other stakeholders in the academic community. By providing alerts for potentially problematic submissions, the API can help ensure the integrity and quality of research publications.
Pass any text that you want to analyze.
The Papermill Text Comparison API takes article metadata as input and classifies articles into ‘red’, ‘orange’, and ‘green’.
‘red’ means that there are past papermill papers that are highly similar to the query article.
‘orange’ means that there are past papermill papers that are a little bit similar.
‘green’ means that no similar past papermill papers are known.
Academic Publishers: Academic publishers can use the Papermill Text Comparison API to check for similarities between submitted papers and previously published works in their database. The API can help publishers identify cases of plagiarism and other forms of misconduct.
Universities: Universities can use the API to check for similarities between student papers and past submissions in their own databases, as well as in external databases such as the ones used by academic publishers.
Research Institutes: Research institutes can use the API to check for similarities between research proposals and previously published works. This can help ensure that research proposals are original and not simply a repetition of previously published work.
Journal Editors: Journal editors can use the API to check for similarities between submitted papers and previously published works in their journals. This can help ensure that the journal publishes only original research.
Research Funders: Research funders can use the API to check for similarities between research proposals and previously published works. This can help ensure that grant funds are not used to repeat previously published work and that grant funds are used for original research.
Besides API call limitations per month, there is a limitation of:
- 10 requests per day on the Basic Plan.
The Papermill Text Comparison API is a system that alerts you when a paper is similar to past papermill products. As such, the output of this API should not be considered to be ‘evidence’ of misconduct. Instead, the output is alerted that can help you to find cases of misconduct.
The PTC takes article metadata as input and classifies articles into ‘red’, ‘orange’, and ‘green’.
‘red’ means that there are past papermill papers that are highly similar to the query article.
‘orange’ means that there are past papermill papers that are a little bit similar.
‘green’ means that no similar past papermill papers are known.
The purpose of this method is only to show the likelihood of a paper coming from a papermill and it is currently limited to cases in biomedical science where papermills have already produced large numbers of similar papers.
Document Posting - Endpoint Features
Object | Description |
---|---|
Request Body |
[Required] Json |
"{\"message\": [{\"id\": \"retracted_article_id2\", \"title\": \"Silencing circANKRD36 protects H9c2 cells against lipopolysaccharide-induced injury via up-regulating miR-138\", \"abstract\": \"Background: Myocarditis refers to the inflammatory process that affects the muscle tissue of the heart. Persistent myocardial inflammation promotes myocardial cell damage, which ultimately leads to heart failure or death. Therefore, we aimed to explore the functional impacts of circANKRD36 on myocarditis. Methods: H9c2 cells were pre-treated with lipopolysaccharide (LPS). Viability and apoptosis were evaluated utilizing CCK-8 assay and flow cytometry. Inflammatory cytokines mRNA expression and production were assessed by qRT-PCR and ELISA. Western blot was utilized to distinguish apoptosis and inflammatory related factors expression. Sequentially, the above mentioned parameters were reassessed when overexpressed miR-138. Results: LPS declined viability and as well as raised apoptosis and inflammatory injury in H9c2 cells. Silencing circular RNA ANKRD36 (si-circANKRD36) alleviated apoptosis and inflammatory injury induced by LPS. MiR-138 expression was suppressed by LPS and elevated by si-circANKRD36. Increase of viability and inflammatory injury induced by si-circANKRD36 was alleviated by down-regulation of miR-138. Eventually, si-circANKRD36 inhibited p38MAPK/NF-\\u03baB pathway which activated by LPS via up-regulating miR-138. Conclusion: Si-circANKRD36 exerted its anti-apoptosis and anti-inflammatory function under the condition of LPS in H9c2 cells through p38MAPK/NF-\\u03baB pathway and up-regulation of miR-138.\", \"message\": {\"status\": \"red\", \"message\": \"This article is highly similar to other papers which are believed to have originated from paper-mills. This does not necessarily mean that this paper originated in a paper-mill. We recommend taking special care to check that this paper meets your criteria for consideration before peer-review.\"}}], \"status_code\": 200}"
curl --location --request POST 'https://zylalabs.com/api/1915/papermill+text+comparison+api/1621/document+posting' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"id": "retracted_article_id2",
"title": "Silencing circANKRD36 protects H9c2 cells against lipopolysaccharide-induced injury via up-regulating miR-138",
"abstract": "Background: Myocarditis refers to the inflammatory process that affects the muscle tissue of the heart. Persistent myocardial inflammation promotes myocardial cell damage, which ultimately leads to heart failure or death. Therefore, we aimed to explore the functional impacts of circANKRD36 on myocarditis. Methods: H9c2 cells were pre-treated with lipopolysaccharide (LPS). Viability and apoptosis were evaluated utilizing CCK-8 assay and flow cytometry. Inflammatory cytokines mRNA expression and production were assessed by qRT-PCR and ELISA. Western blot was utilized to distinguish apoptosis and inflammatory related factors expression. Sequentially, the above mentioned parameters were reassessed when overexpressed miR-138. Results: LPS declined viability and as well as raised apoptosis and inflammatory injury in H9c2 cells. Silencing circular RNA ANKRD36 (si-circANKRD36) alleviated apoptosis and inflammatory injury induced by LPS. MiR-138 expression was suppressed by LPS and elevated by si-circANKRD36. Increase of viability and inflammatory injury induced by si-circANKRD36 was alleviated by down-regulation of miR-138. Eventually, si-circANKRD36 inhibited p38MAPK/NF-κB pathway which activated by LPS via up-regulating miR-138. Conclusion: Si-circANKRD36 exerted its anti-apoptosis and anti-inflammatory function under the condition of LPS in H9c2 cells through p38MAPK/NF-κB pathway and up-regulation of miR-138."
}'
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 API returns a classification of the submitted article based on its similarity to past papermill papers. The classifications are 'red' (high similarity), 'orange' (some similarity), and 'green' (no known similar papers). Additionally, it provides metadata about similar articles, including titles and abstracts.
The key fields in the response data include 'id' (identifier of the similar article), 'title' (title of the similar article), and 'abstract' (summary of the similar article). These fields help users understand the context of the similarities.
The response data is structured as a JSON object containing a 'message' array. Each entry in the array represents a similar article, with fields for 'id', 'title', and 'abstract', allowing users to easily parse and utilize the information.
The API provides information on the similarity of submitted articles to previously published works, including classifications of similarity and details about articles that are similar. This helps users identify potential misconduct.
The API compares submitted articles against a database of previously submitted papers, known as "papermill-products." This database includes works primarily in biomedical science, where papermills have produced numerous similar papers.
Users can customize their requests by providing specific article metadata as input. This metadata may include the title, authors, and abstract of the article being analyzed, allowing for tailored comparisons against the database.
Typical use cases include academic publishers checking submitted papers for originality, universities verifying student submissions, and research funders ensuring grant proposals are unique. These applications help maintain the integrity of academic work.
Users can utilize the returned data by analyzing the classification and reviewing the details of similar articles. A 'red' classification may prompt further investigation, while 'green' indicates originality, aiding in decision-making for publication or funding.
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.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world’s most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the ‘X-Zyla-API-Calls-Monthly-Remaining’ field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the ‘X-Zyla-RateLimit-Limit’ response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
The ‘X-Zyla-RateLimit-Reset’ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it’s important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
100%
Response Time:
250ms
Service Level:
100%
Response Time:
113ms
Service Level:
100%
Response Time:
2,034ms
Service Level:
83%
Response Time:
1,132ms
Service Level:
100%
Response Time:
162ms
Service Level:
100%
Response Time:
263ms
Service Level:
100%
Response Time:
162ms
Service Level:
100%
Response Time:
502ms
Service Level:
100%
Response Time:
1,208ms
Service Level:
100%
Response Time:
365ms
Service Level:
100%
Response Time:
755ms
Service Level:
100%
Response Time:
2,074ms
Service Level:
100%
Response Time:
1,289ms
Service Level:
100%
Response Time:
527ms
Service Level:
100%
Response Time:
477ms
Service Level:
100%
Response Time:
117ms
Service Level:
100%
Response Time:
139ms
Service Level:
47%
Response Time:
726ms
Service Level:
100%
Response Time:
652ms
Service Level:
100%
Response Time:
928ms