# 1885 API-Portal (Auriga Strategy) > Central catalog of Auriga/1885 APIs for the German construction industry. All APIs: Bearer-key auth (product-scoped, revocable via Unkey); keys via self-service form at https://developer.1885.cloud (production keys approved by Auriga); sample data, capability catalog (/v1/stories) and accuracy report (/v1/tuev) need no key. Trust model everywhere: every value with a verifiable citation; unknowns returned as not_checkable, never guessed. Canonical base URLs live in the api namespace (.api.1885.cloud). The former .1885.cloud addresses remain permanently valid aliases — published URLs are never moved. ## APIs - Document Intelligence — https://di.api.1885.cloud — machine-reads tender packages & geotechnical reports (classification, extraction with citations, LAGA/DK/AVV analytics, knowledge hub) AND checks incoming invoices (par. 14 UStG mandatory fields, arithmetic probes, IBAN/VAT-ID check digits, duplicate + IBAN-change alarms against 581k group bookings; XRechnung/ZUGFeRD read deterministically, scans via OCR, async batch jobs; sample invoice GET /v1/beispiele/rechnung, Python SDK GET /v1/sdk/python, OpenAPI https://di.api.1885.cloud/openapi.json). Agent entry: https://di.api.1885.cloud/llms.txt · MCP: POST https://di.api.1885.cloud/mcp?apiKey= - TGA tender data / TGA-Ausschreibungs-Daten (LIVE) — https://tga.api.1885.cloud — TGA positions from German tenders for building-services subcontractors: trade assignment per VOB/C ATV (DIN 18379-18382, 18386) with honest provenance (position anchors + lot inheritance), margin-critical calculator findings (commissioning, documentation debt, core drilling ownership, bauseits, time-and-material, maintenance, sampling, VDI 6022) each with state + verbatim LV quote. Agent entry: https://tga.api.1885.cloud/llms.txt · OpenAPI: https://tga.api.1885.cloud/openapi.json - Site traffic safety / Baustellensicherheits-Daten (LIVE) — https://bss.api.1885.cloud — traffic safety data from German tenders for BSS subcontractors: closure type/location/traffic plan per LV position via two-path consensus (dissent goes to human review, never guessed), margin-critical contract rules (verkehrsfuehrung, abrechnung_vorhaltung) with document+page+verbatim quote, traffic sign plan classification. Agent entry: https://bss.api.1885.cloud/llms.txt · OpenAPI: https://bss.api.1885.cloud/openapi.json - Energy documents / Energie-Belege ISO 50001 (LIVE) — https://energie.api.1885.cloud — energy data from utility invoices and delivery notes, audit-proof for ISO 50001 EnMS: consumption, market location ID with BDEW check digit, meter reading probes, DVGW G685 recalculation (gas), par. 40 EnWG mandatory fields, measured-vs-ESTIMATED flag, per-meter period watchdog (gaps/overlaps). Agent entry: https://energie.api.1885.cloud/llms.txt · OpenAPI: https://energie.api.1885.cloud/openapi.json - Invoice inbound check / Rechnungseingangspruefung (LIVE) — https://rechnung.api.1885.cloud — every incoming invoice checked, every value cited: par. 14 UStG mandatory fields (incl. par. 33 small-amount rule), arithmetic probes, IBAN/VAT-ID/Leitweg-ID check digits, EN 16931 base fields, duplicate + IBAN-change alarms; e-invoices read deterministically, scans via OCR, async jobs. Agent entry: https://rechnung.api.1885.cloud/llms.txt · OpenAPI: https://rechnung.api.1885.cloud/openapi.json (same engine as di.1885.cloud/v1/pruefung — second door, old door stays) - Disposal tender data / Entsorgungs-Ausschreibungsdaten (LIVE) — https://entsorgung.api.1885.cloud (permanent alias: reconic.api.1885.cloud) — read-only curated LV position data with disposal grading (tenders, Positionsart/Stoffstromart, AVV, EBV/LAGA/DepV/RuVA classifications, purpose classification with evidence quotes; human MENSCH decisions are final). Agent entry: https://entsorgung.api.1885.cloud/llms.txt · OpenAPI: https://entsorgung.api.1885.cloud/openapi.json - Regelwerke (BETA) — https://regelwerke.api.1885.cloud — citation-backed answers on German construction regulations: 100k+ indexed sections from ~3,800 source documents (laws, VOB/A-C, DGUV, ASR, TRGS, RSA 21, state procurement/Tariftreue law, federal-highway engineering canon ZTV-ING/TL-TP-ING/HVA B-StB, rail-construction layer DGUV 78/101-024 + EBA, ~2,700 construction court decisions). Routes: ask (+SSE stream), search, katalog, format-rules(+validate), router. Agent entry: https://regelwerke.api.1885.cloud/llms.txt - Fakten-Hub / Datenplattform (LIVE) — https://hub.1885.cloud — curated PGB master data, every row carries stichtag (data date) + quelle (source). Doors as paths: /energie/v1/ (energy documents, ISO 50001 views, refuelling ledger, vehicle deployment) and /kreditoren/v1/ (supplier master from 798k+ invoices since 2017 with official register match + insolvency status). Contract technically enforced (object+field whitelist per data product, default-deny, writes append-only where agreed, limit<=1000). SEPARATE key system: 1885 API keys do NOT open the hub; consumers get their own hub key with per-data-product approval (access register) — request via marcus.ehlers@auriga-strategy.com. MCP + GraphQL doors follow under the same address. - Search — planned (web search/read/browse as a building block for 1885 apps and agents; one key, per-key quotas and metering). - Stoffstrom data for partners (LIVE) — https://stoffstrom.api.1885.cloud — disposal-chain partner data: target facilities (landfill atlas with OFFICIAL DK class + full AVV admission list per site; filters bundesland/dk/avv/plz/q), carriers with official EfB register match (source per entry), disposal positions from real invoices (quantity/unit price/total + verbatim citation per row). GET /v1/fuhren publishes the BINDING weighing-slip schema (gross/tare/net, vehicle, ziel_deponie_id, eur_pro_t, beleg_pdf) with the data pipeline honestly flagged im_aufbau. Separate partner scope stoffstrom (the tender-data key does NOT open this surface). Agent entry: https://stoffstrom.api.1885.cloud/llms.txt · OpenAPI: https://stoffstrom.api.1885.cloud/openapi.json ## Operational endpoints (public, no key) - Story catalog DI (check capabilities FIRST): https://di.api.1885.cloud/v1/stories — every capability as a user story (what/for whom, honest status produktiv/teilweise/geplant); request missing stories via POST https://di.api.1885.cloud/v1/stories/wunsch · human view https://di.api.1885.cloud/stories - Live status: https://developer.1885.cloud/status?format=json (checks the real chain gateway->service) - Changelog: https://developer.1885.cloud/changelog?format=json (every published API change, dated) - Accuracy report DI: https://di.api.1885.cloud/v1/tuev (goldset measurement runs per pack, with methodology) ## Operations promise & data protection (Etappe C) - Reliability & operations contract: https://developer.1885.cloud/verlaesslichkeit — availability TARGET 99.5%/month (measured, no credit SLA during POC — honest), support weekdays <1 business day, rate limits (429+Retry-After), idempotency, versioning (additive-only, /v2 + Deprecation/Sunset headers, >=6 months), offboarding (no lock-in) - Data protection & retention: https://developer.1885.cloud/datenschutz — processing in Frankfurt (Fly fra + Supabase eu-central-1), full subprocessor list (incl. LLM providers per request + EU VIES), sync documents never stored, async stores RESULTS only, tenant-separated memories, deletion on request; GDPR Art. 28 DPA exists as a DRAFT (legal review pending — stated honestly) - Pricing: deliberately individual per application during the POC (no public price list yet); free exploration via self-service sandbox (POST https://di.api.1885.cloud/v1/sandbox, 14 days) and keyless surfaces ## Human portal https://developer.1885.cloud (German)