The archive is a database wearing a folder costume.

1 · Bulk import the back catalog

Point a loop at the folder (Drive export, S3 bucket, the shared drive of shame). Each file gets one POST; extraction is a background job, so fire away and read back later.

for f in ./contracts/*.{pdf,docx}; do
  curl -s -X POST https://app.version90.com/api/v1/archive \
    -H "Authorization: Bearer $V90_TOKEN" \
    -F "file=@$f" | jq -r '"\(.id)  \(.original_filename // .detail.message)"'
done

2 · Renewal calendar (the invoice should never be the notification)

Extracted expiration_date plus the risk flags on auto-renewal clauses make renewal tracking a nightly cron, not a memory test.

curl -s "https://app.version90.com/api/v1/archive" \
  -H "Authorization: Bearer $V90_TOKEN" \
| jq -r --arg cutoff "$(date -v+90d +%Y-%m-%d)" \
    '.items[] | select(.expiration_date != null and .expiration_date <= $cutoff)
    | "\(.expiration_date)  \(.counterparty)  \(.title)"' | sort
# (date_from/date_to query params filter on EFFECTIVE date; expiration is
#  filtered client-side.) Pipe into Slack, a calendar API, or your tracker.

3 · Warehouse export (contract terms next to revenue data)

Pull the whole structured catalog into your warehouse and suddenly "average payment terms by customer segment" is a SQL query.

import requests

rows = requests.get(
    "https://app.version90.com/api/v1/archive",
    headers={"Authorization": f"Bearer {TOKEN}"},
).json()["items"]

for r in rows:
    detail = requests.get(
        f"https://app.version90.com/api/v1/archive/{r['id']}",
        headers={"Authorization": f"Bearer {TOKEN}"},
    ).json()
    warehouse.insert("contracts", {
        "counterparty": detail["counterparty"],
        "type": detail["agreement_type"],
        "effective": detail["effective_date"],
        "expires": detail["expiration_date"],
        "governing_law": detail["governing_law"],
        "terms": detail["key_terms"],     # structured field/value pairs
        "risks": detail["risks"],
    })

4 · Agent Q&A over the archive (MCP)

Connect the MCP server and the archive becomes something your team can interrogate in plain English — with answers grounded in extracted, cited fields:

• "Do any customer contracts prevent us from using subprocessors?"
• "Which agreements have exclusivity, and in which territories?"
• "Compare the liability caps across our three biggest vendor MSAs."

5 · Auto-file from where contracts actually land

Contracts signed through version90 — native e-sign or a connected DocuSign/Dropbox Sign account — file themselves into the archive the moment signing completes; nothing to build. For everything executed elsewhere (deal-desk email, a CRM attachment field, a counterparty's signing tool), a ten-line handler that base64s the file into upload_to_archive (MCP) or POSTs it to /archive (REST) means the archive is simply always current — no one "does filing" ever again.