> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/docs/es/acciones/workflow-concepts/workflow-steps/content-quality/scan-content-for-plagiarism.md).

# Analizar el contenido en busca de plagio

El paso "Escanear contenido en busca de plagio" te permite comprobar si un texto contiene posible plagio comparándolo con miles de millones de páginas web, trabajos académicos y otras fuentes publicadas. Esta potente herramienta utiliza la tecnología avanzada de detección de plagio de Originality.ai para ayudarte a garantizar la originalidad del contenido y evitar problemas de derechos de autor.

### Cómo configurar el paso Escanear contenido en busca de plagio

* **Contenido**: Ingresa el contenido que te gustaría analizar
* **Dominio a excluir (opcional)**: Introduce una URL para excluirla del análisis. Normalmente se trata de tu dominio, dado que existe una alta probabilidad de solapamiento de contenido entre este contenido y el contenido existente de tu dominio.

<figure><img src="https://3036434873-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-ebed2212fcd3d36fa29f0cfc5c2ab73b741ec9f2%2Fplagiarism-01-step-config.png?alt=media" alt="Scan Content for Plagiarism step with spaceops.io excluded from the check"><figcaption><p>Excluye tu propio dominio del análisis de plagio.</p></figcaption></figure>

### Formato de salida

El paso Escanear contenido en busca de plagio devuelve un objeto JSON que contiene resultados detallados del análisis:

```json
{
  "success": true,
  "disclaimer": "Si intentas analizar contenido de menos de 50 palabras de longitud, tendrás problemas de precisión de la IA.",
  "public_link": "https://app.originality.ai/share/[ID]",
  "title": "Análisis API V1",
  "total_text_score": "93%",
  "results": [
    {
      "phrase": "frase uno",
      "results": [
        {
          "link": "example.com",
          "title": "título",
          "scores": [
            {
              "score": 1.0000000000000002,
              "sentence": "oración uno"
            }
          ],
          "timestamps": {
            "date_modified": "2024-02-26",
            "date_published": "2024-02-26"
          }
        }
      ]
    },
    
    // Resultados adicionales aquí
    
  ],
  "credits_used": 10,
  "credits": 123,
  "subscription": 123,
  "content": "contenido aquí",
  "id": [id]
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.airops.com/docs/es/acciones/workflow-concepts/workflow-steps/content-quality/scan-content-for-plagiarism.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
