ARTEDUSA VERIFY — FOR AI BUILDERS

Your AI writes the lot description. The auctioneer carries the liability.

Check every master's name against sourced attestations BEFORE publication: attested / contradicted / unavailable verdict in ~30 ms, never fabricated. Every attestation carries its citation (source_ref), its confidence and its status.

Factual context: in France, the vocabulary of attribution statements in public auction is regulated by décret n° 81-255 of 3 March 1981; the Cour de cassation confirmed an auction operator's liability for lack of diligence on an attribution (Cass. civ. 1re, 4 Dec. 2024, n° 23-17.569). These references are cited for documentary purposes — this page is not legal advice.

Try the oracle Become a design partner

The corpus, live

These counters are read live from GET /api/v1/verify/coverage — the same numbers your pipeline will read at onboarding. Nothing rounded, nothing promised.

Reading live coverage…

Try the oracle — on the real data

Two real requests against the production API. The first shows an attestation with a real dimension contradiction; the second shows refuse-to-fabricate: outside the corpus, the oracle answers unavailable — never an invention.

The integration flow

1 — GET /coverage at onboarding

Your tool reads the coverage manifest once, then only calls the oracle on covered artists. Zero noise, zero wasted calls.

2 — POST /verify inside the pipeline

The draft description mentions a covered master → your pipeline posts {subject_artist, subject_title} and gets the verdict in ~30 ms, inside the generation budget.

3 — Three verdicts, three branches

attested → sourced notes injected into the description. contradicted → banner + requalification following the décret 81-255 vocabulary ("attributed to", "school of"). unavailable → displayed as-is + operator-research escalation on high-estimate lots.

4 — Archived request_id = audit trail

The replayable request_id archived in the lot record is a timestamped trace of the documentary checks performed before publication. Even an unavailable has audit value.

The call, as-is

REST — POST /api/v1/verify

curl -X POST https://api.artedusa.com/api/v1/verify \
  -H 'Content-Type: application/json' \
  -d '{
    "subject_artist": "Jean-Baptiste Camille Corot",
    "subject_title": "Nymphs and Fawns"
  }'

Response (abridged)

{
  "engine": "records-attestation/v1",
  "request_id": "12950a3a-d015-452e-8c27-13109054cdc8",
  "subject": {"artist": "Jean-Baptiste Camille Corot",
              "title": "Nymphs and Fawns"},
  "verdict": "attested",
  "verified_pillars": ["provenance", "authentication",
                       "market", "condition"],
  "contradicted_pillars": ["authentication"],
  "attestations": [
    {"pillar": "provenance",
     "claim": "…",
     "source_ref": "Alfred Robaut, L'Œuvre de Corot, …",
     "confidence": 0.9,
     "status": "verified",
     "verified_by": "…"}
    // … 41 more
  ],
  "near_matches": [],
  "disclaimer": "…"
}

MCP — artedusa-verify server

Two tools: verify_art_records + verify_coverage. Zero-dependency JSON-RPC stdio server, stdlib only.

{
  "mcpServers": {
    "artedusa-verify": {
      "command": "python3",
      "args": ["/path/to/artedusa-ai/scripts/mcp_verify_server.py"],
      "env": {
        "ARTEDUSA_API_URL": "https://api.artedusa.com",
        "ARTEDUSA_VERIFY_KEY": "…"
      }
    }
  }
}

Full schema (OpenAPI) in the backend API docs.

What we do not cover

Transparency is the feature. The real limits, stated plainly:

Current coverage: 1,535 artworks / 675 public-domain artists. Most calls will get unavailable — that is the intended behaviour, never an invention.
No prices, no estimates, no bulk market data (see Artprice or LiveArt for that).
No image analysis or visual authentication (see Art Recognition).
No contemporary art — public-domain masters only.
The third of claims imported from Wikidata is not a catalogue-raisonné authority: they are attributed to their source and confidence-tiered below operator research.
No spoliation, sanctions or AML clearance.
The requalification suggestion is documentary assistance — not legal advice.

Data licence

Claims marked "import:wikidata" derive from Wikidata (CC0). Those facts are freely reusable — we are not selling you those facts, we sell the attestation service on top: matching, verdicts, verification statuses, the audit request_id.
Operator-researched claims are proprietary.
Permitted use: grounding and citation with source_ref in your systems and descriptions.
Bulk redistribution of operator claims and model training on those claims: by contract only.

Access & pricing

Pay-per-use only — no subscription. Monthly invoicing of actual usage, by bank transfer; no online payment.

Sandbox

Free

No key, rate-limited. Evaluate the API and the corpus before any decision.

Design partner pilot

Free · 2-3 months

3 to 6 seats. Guided integration into your pipeline, direct input on the corpus roadmap.

Production

€0.10 / call — metered

Pay-per-use only: dedicated metered key, you pay for served calls and nothing else. Monthly invoicing by bank transfer, volume discounts.

Volume

Custom quote

Still pay-per-use — contracted degressive rate above 10,000 calls/month, with SLA.

On-demand research

€590 / €1,490 excl. VAT per work

Sourced operator dossier — the escalation for high-estimate lots. Delivered claims join the corpus and stay queryable through the API.

Become a design partner

3 to 6 seats for the free pilot (2-3 months). Tell us which pipeline you are building; we reply within 48 business hours.