Contents.team, inside the tools you already use.

Photos in, a priced, defensible contents inventory out. Connect it to your browser or your own claims platform.

The process you plug into.

Whatever the entry point, every claim runs through the same pipeline, and a person reviews it before anything leaves.
  1. 01

    Room photos from anywhere.

    Photos in

    Upload from a phone, grouped by room and kept as the evidence behind each line they produce. An existing item list can come in as a spreadsheet instead.
  2. 02

    AI drafts the visible items.

    Items identified

    Each photo becomes editable item lines with a name, category, quantity and condition. Uncertain details are flagged for a person to review rather than guessed silently.
  3. 03

    Like-kind prices with a source.

    Replacement priced

    Every item gets a replacement price from an established retailer, with the product link kept on the line so a reviewer can open it and check.
  4. 04

    Depreciation, RCV and ACV.

    Valued

    Age and condition drive depreciation, so each line carries replacement cost value and actual cash value side by side.
  5. 05

    A carrier-ready export.

    Out the door

    An XactContents-format XLSX, a branded PDF report, or a ZIP of every photo by room, each with the source links and valuation fields intact.

Available today.

These work with every Contents.team account today.

Chrome extension

Price an item from any retailer’s page. The side panel reads the product title, model and price, and applies them to an item on your claim with the source link attached. It never changes the item’s review status.

  • Works on any store’s product page
  • Keeps the source URL on the line
  • Connect it from Settings → Connections

Imports and exports

Bring an existing list in from a spreadsheet, and hand the finished inventory to whatever comes next in the claim.

  • Spreadsheet import from our template
  • XactContents-format XLSX
  • Branded PDF report
  • ZIP of photos by room

Early access

A partner API for your platform.

Claims platforms, restoration software and TPAs can run the Contents.team pipeline from their own product. We are building it with our first partners, so the shape below is a preview, not a contract.
  1. 01

    Create a claim

    Open a claim from your system with your own reference id, so both sides stay linked.

  2. 02

    Send room photos

    Upload photos tagged by room. Contents.team identifies, prices and values the items.

  3. 03

    Receive the inventory

    A signed webhook fires when items are priced. Fetch the line items, or pull the XLSX or PDF export.

Inventory API
Create claims, upload room photos, and read priced line items.
Webhooks
Signed events when an inventory is ready and when an item is priced.
Exports
Fetch the XactContents-format XLSX or the PDF report for a claim.
A priced itemPreview, subject to change
{
  "id": "itm_8f2c41",
  "claimRef": "YOUR-CLAIM-1042",
  "room": "Living room",
  "description": "Samsung 65\" QLED 4K Smart TV",
  "category": "Electronics",
  "quantity": 1,
  "condition": "good",
  "rcvCents": 129999,
  "depreciationBp": 2000,
  "acvCents": 103999,
  "source": {
    "retailer": "Best Buy",
    "url": "https://www.bestbuy.com/..."
  },
  "photoIds": ["pho_31a9"]
}

Money is in cents and depreciation in basis points, so there is no floating-point rounding between systems.

How we handle your data

Every organization’s claims, photos and items are isolated from every other organization’s. Integrations act with the permissions of the account that connected them, and an owner or admin can disconnect any of them from Settings at any time. Photos are stored privately and encrypted at rest; we don’t sell or share your data, and we don’t use it to train outside models.

Read the privacy policy and the data processing agreement.

Your platform here.

Building claims, restoration or inventory software? Tell us how your users work and we’ll scope the integration with you.