> ## Documentation Index
> Fetch the complete documentation index at: https://docs.samsa.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Erkennungs-Infos abrufen
> Eine maschinenlesbare Beschreibung jeder Samsa-Markierungstechnik, ihres Decoders und ihres gehosteten Erkennungsstatus.
```
GET https://detect.samsa.ai/v1/public/detect/info
```
Liefert eine statische, maschinenlesbare Beschreibung des Erkennungsdienstes: die
angewandten Methoden, die Aufbewahrungspraxis, externe Prüf-Links und — je
Markierungstechnik — alles, was Dritte brauchen, um die Erkennung unabhängig von Samsa
zu integrieren und zu nutzen.
Das ist das JSON-Gegenstück zu
[So funktioniert die Erkennung](https://detect.samsa.ai/how-detection-works), Samsas
öffentlicher Information nach Maßnahme 3.4(b) für die Europäische Kommission und
weitere Interessengruppen. Der Endpoint nimmt keine Parameter entgegen, liest keine
Client-Daten und gibt keine personenbezogenen Daten zurück.
```bash curl theme={null}
curl https://detect.samsa.ai/v1/public/detect/info
```
## Response
| Feld | Typ | Beschreibung |
| ------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| `service` | string | Kennung des Dienstes. |
| `methods[]` | array | Die angewandten Erkennungsmethoden, je mit `type` (`metadata` oder `watermark`), `role` (`authoritative` oder `corroboration`) und `description`. |
| `retention` | string | Die Aufbewahrungspraxis als Fließtext. |
| `external_verification` | object | Links, um Ergebnisse unabhängig von Samsa zu prüfen. Aktuell `c2pa`. |
| `result_pdf_availability_hours` | integer | Wie lange eine [signierte Ergebnis-PDF](/de/content-verification/results) abrufbar bleibt. |
| `marking_techniques[]` | array | Integrations- und Zugangsinformationen je Technik — siehe [unten](#markierungstechniken). |
| `info_page_url` | string | URL der menschenlesbaren Fassung dieser Information. |
### Markierungstechniken
Jeder Eintrag in `marking_techniques[]` beschreibt eine Technik:
| Feld | Typ | Beschreibung |
| ------------------------------- | -------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| `id` | string | Stabile Technik-ID: `c2pa`, `trustmark-q` oder `video-seal`. |
| `kind` | enum | `metadata` oder `watermark`. |
| `modalities[]` | array | Für welche von `image` und `video` die Technik gilt. |
| `display_name` | string | Menschenlesbarer Name. |
| `description` | string | Was die Technik ist und welche Rolle sie im Urteil spielt. |
| `algorithm_id` | string \| null | Die in C2PA gelistete Algorithmus-ID. `null` für C2PA selbst, das ein Herkunfts-Manifest ist und kein Soft-Binding-Algorithmus. |
| `soft_binding_label_mappings[]` | array | Je Signaturweg das Assertion-`label`, unter dem die Soft-Binding-Nutzlast geführt wird, mit `lane`-Name und erläuterndem `detail`. |
| `decoder` | string \| null | Woher du einen unabhängigen Decoder für diese Technik bekommst. |
| `pinned_artifacts` | object | SHA-256 der von Samsa gepinnten Modell-Artefakte, nach Rolle (zum Beispiel `encoder`, `decoder`). |
| `hosted_decode_status` | enum | `available` oder `not_yet_available` — der Status **von Samsas gehostetem Detektor** für diese Technik. |
| `hosted_decode_detail` | string | Der Status als Fließtext. |
| `notes` | string \| null | Ein Vorbehalt je Technik, sofern einer gilt. |
| `info_url` | string | URL der menschenlesbaren Beschreibung dieser Technik. |
`hosted_decode_status` beschreibt **den Detektor**, nicht die Markierung. Beide
Wasserzeichen-Techniken melden `not_yet_available`: Die gehostete
Wasserzeichen-Erkennung ist vor dem 2. Februar 2027 geplant, und bis dahin meldet der
Detect-Endpoint diese Techniken als `not_checked`, niemals als falsches „kein
Wasserzeichen“.
```json Response theme={null}
{
"service": "daku-detect",
"methods": [
{
"type": "metadata",
"role": "authoritative",
"description": "C2PA manifest verification is the authoritative provenance signal: a valid, trusted, allowlisted Samsa manifest identifies content as created with Samsa."
},
{
"type": "watermark",
"role": "corroboration",
"description": "Invisible watermark decodes provide best-effort corroboration and degrade gracefully when a decoder backend is unavailable; they never override the C2PA verdict."
}
],
"retention": "Samsa does not retain uploaded content: uploads are processed in memory and are never persisted or logged. Only a no-PII audit row (request id, coarse region bucket, verdict facts) is recorded.",
"external_verification": {
"c2pa": "https://verify.contentauthenticity.org"
},
"result_pdf_availability_hours": 24,
"marking_techniques": [
{
"id": "c2pa",
"kind": "metadata",
"modalities": ["image", "video"],
"display_name": "C2PA Content Credentials",
"description": "Cryptographic provenance manifest embedded in the asset; the authoritative detection layer for both images and video.",
"algorithm_id": null,
"soft_binding_label_mappings": [],
"decoder": "Validate with any independent C2PA validator (c2patool, verify.contentauthenticity.org) or with our hosted API POST /v1/public/detect.",
"pinned_artifacts": {},
"hosted_decode_status": "available",
"hosted_decode_detail": "Live: C2PA manifest verification is served by our public API and by any independent C2PA validator.",
"notes": "Trust anchoring per lane, split by asset SIZE rather than media type: the Trufo lane covers images and video up to the inline size ceiling, and Trufo's C2PA Root CA is on the official C2PA Trust List, so those manifests chain to a trust-listed root; the own-cert lane covers re-signed assets and anything above that ceiling, carrying the same assertions and validating structurally against the Samsa signer chain. Samsa's own C2PA conformance application (generator product 'Samsa Media Service') is filed and under review.",
"info_url": "https://detect.samsa.ai/how-detection-works"
},
{
"id": "trustmark-q",
"kind": "watermark",
"modalities": ["image"],
"display_name": "TrustMark Q (image imperceptible watermark)",
"description": "Adobe TrustMark Q imperceptible image watermark; a best-effort corroboration signal that never overrides the authoritative C2PA verdict.",
"algorithm_id": "com.adobe.trustmark.Q",
"soft_binding_label_mappings": [
{
"lane": "Trufo-signed (assets up to the inline size ceiling)",
"label": "ai.samsa.soft-binding",
"detail": "The Trufo wire contract rejects c2pa.* custom labels, so the standard soft-binding payload (naming com.adobe.trustmark.Q) is carried under this Samsa RDNN label. Third parties MUST read this label to find the signpost on Trufo-signed assets."
},
{
"lane": "own-cert (re-signed assets and anything above the ceiling)",
"label": "c2pa.soft-binding",
"detail": "Own-cert-signed content carries the identical payload under the standard C2PA soft-binding label."
}
],
"decoder": "Adobe's open-source `trustmark` package (https://github.com/adobe/trustmark).",
"pinned_artifacts": {
"encoder": "80a3c3c0cb8cd16d0de4411ee7df122029424a0d5c510d875506adb90276bb9c",
"decoder": "28b177ef112965e7e4bf2153b06f4464ce5ced52b68e6da3bbf5e1d15084f110"
},
"hosted_decode_status": "not_yet_available",
"hosted_decode_detail": "Hosted watermark decode is not yet available in our public API; it is scheduled before 2 February 2027. Until then the API reports this technique as not_checked (never a constructed 'absent' false negative).",
"notes": null,
"info_url": "https://detect.samsa.ai/how-detection-works"
},
{
"id": "video-seal",
"kind": "watermark",
"modalities": ["video"],
"display_name": "Meta Video Seal (video imperceptible watermark)",
"description": "Meta Video Seal imperceptible video watermark; a best-effort corroboration signal that never overrides the authoritative C2PA verdict.",
"algorithm_id": "com.aiwatermark.videoseal.1",
"soft_binding_label_mappings": [
{
"lane": "Trufo-signed (assets up to the inline size ceiling)",
"label": "ai.samsa.soft-binding",
"detail": "Signing-route selection is by asset SIZE, not by media type, so video signed through the Trufo lane carries the soft-binding under this Samsa RDNN label for the same reason images do (the Trufo wire contract rejects c2pa.* custom labels). Third parties MUST read this label as well as the standard one."
},
{
"lane": "own-cert (re-signed assets and anything above the ceiling)",
"label": "c2pa.soft-binding",
"detail": "Own-cert-signed video carries the identical payload under the standard C2PA soft-binding label."
}
],
"decoder": "Open-source facebookresearch/videoseal (https://github.com/facebookresearch/videoseal).",
"pinned_artifacts": {},
"hosted_decode_status": "not_yet_available",
"hosted_decode_detail": "Hosted watermark decode is not yet available in our public API; it lands with the watermark-interoperability work, before 2 February 2027.",
"notes": "The VideoSeal watermark embed itself goes live with the video lane once its validation completes, a separate axis from provisioning the public detector; do not read this as hosted decode being live.",
"info_url": "https://detect.samsa.ai/how-detection-works"
}
],
"info_page_url": "https://detect.samsa.ai/how-detection-works"
}
```
Dieselbe Information als menschenlesbare Seite, inklusive der Details zur
Vertrauensverankerung hinter jedem Signaturweg.