# Copies for AI

Source: https://wire.ia.br/documentation/en/api/copias-para-ia

> How the secure token works, the isolated copy of a vault and the review of changes.



The secure token exists so you can hand a vault to an AI without risking the original. The AI works on a copy; you decide what comes back.

## How it works [#how-it-works]

<Steps>
  <Step>
    **You create the secure token** in Settings → Developer and pick a vault. The app sends a copy of the text of that vault's pages to the server. Password-protected pages stay out.
  </Step>

  <Step>
    **The AI uses the API as usual.** `GET /vaults` shows a single vault, with an id of `copia-` and 16 characters. It lists, reads, searches, creates, edits and deletes pages in that copy.
  </Step>

  <Step>
    **You review.** In **Copies for AI**, the app shows how many changes are waiting. **Review changes** lists each new, edited or deleted page, with the text the AI left.
  </Step>

  <Step>
    **You choose what to bring.** With the original vault open in the app, check the changes you want and tap **Bring into the vault**. They enter your device and go up to Drive on the next sync. Ctrl Z undoes it. **Discard selected** removes the changes from the list without touching your vault.
  </Step>
</Steps>

## For whoever programs the AI [#for-whoever-programs-the-ai]

Nothing changes in how you call the API. Use the copy's id where the vault id would go:

```bash
VAULT=$(curl -s https://wire.ia.br/api/v1/vaults \
  -H "Authorization: Bearer $PAPER_TOKEN" | jq -r '.[0].id')

curl "https://wire.ia.br/api/v1/vaults/$VAULT/pages" \
  -H "Authorization: Bearer $PAPER_TOKEN"
```

Differences from the regular token:

* Search returns a snippet of text with each result.
* It doesn't upload files or touch the calendar (`403` or `400`).
* The copy takes up to 6000 pages. The original vault must have up to 20 MB of text to be copied.
* Changes the person makes in the original vault after the copy don't show up for the AI. To give it the new version, the person creates another secure token.

## What gets stored [#what-gets-stored]

The copy sits on the Paper server, in plain text, for as long as the token exists. It's deleted when the person revokes the token or turns developer mode off. Reviewing doesn't delete the copy: the AI can keep working on it. This is in the [privacy policy](https://wire.ia.br/en/privacy/).

## Tell this to the AI [#tell-this-to-the-ai]

If the AI knows it's working on a copy, it feels freer to reorganize and you keep the final word. The **Copy instructions for the AI** button, which appears when you create the token, already builds a text with the token, the account ID, the API base and the link to the [documentation map](https://wire.ia.br/documentation/agents/raw.json).