https://docs.truebees.eu/blog Truebees Platform Docs Blog 2026-04-03T00:00:00.000Z https://github.com/jpmonette/feed Truebees Platform Docs Blog https://docs.truebees.eu/img/favicon.ico <![CDATA[Introducing the Truebees Verification API]]> https://docs.truebees.eu/blog/verification-api-launch 2026-04-03T00:00:00.000Z We are excited to announce the Truebees Verification API in closed beta — a REST API that lets you programmatically detect AI-generated and deepfake media at any scale. It is not generally available yet. If you would like to try it, email support@truebees.eu. This new API replaces the legacy API at https://app.truebees.eu/api, which will be retired on 15 May 2026.

What's new​

Beyond replacing the legacy API, this release brings several major upgrades:

  • Multi-media support — analyse images, video, and audio in a single unified API
  • More models and pipelines — access an expanded catalogue of detection pipelines, each tuned for different media types and use cases
  • Same simple interface — submit a file, poll for the result; the async model you already know

Migration deadline​

The legacy API at https://app.truebees.eu/api will be retired on 15 May 2026. It is replaced by two dedicated services; access to those replacements is part of the closed beta — contact us to enroll.

Legacy endpointReplacement
https://app.truebees.eu/api (authentication)https://app.truebees.eu/api/v2
https://app.truebees.eu/api (media verification)https://verify.truebees.eu

We recommend migrating as soon as you have beta access. For migration help or to request enrollment, email support@truebees.eu.

What it does​

The Verification API analyses media files and returns one of three verdicts:

VerdictMeaning
realThe file is consistent with authentic, unmanipulated media
generatedThe file shows AI-generation or synthesis artifacts
unknownThe pipeline could not determine authenticity with sufficient confidence

Each verdict comes with a confidence score (0.0–1.0) and a human-readable explanation, so your application can make informed decisions — accept, flag, or route to human review.

How it works​

The API is asynchronous and built around two endpoints:

Submit a media file for verification:

curl -X POST https://verify.truebees.eu/api/v1/verification_request \
  -H "Authorization: Bearer <ACCESS_TOKEN>" \
  -F "file=@video.mp4" \
  -F "pipeline=cantaloupe"

This returns a requestId immediately while processing happens in the background.

Poll for the result:

curl -X GET \
  "https://verify.truebees.eu/api/v1/verification_request/<REQUEST_ID>" \
  -H "Authorization: Bearer <ACCESS_TOKEN>"

Once status is completed, the verdict field is populated with the result.

Authentication​

Access is controlled via service principals — machine credentials (Client ID + Client Secret) managed from the Truebees dashboard. Exchange them for a short-lived Bearer token using the Auth API, then use that token on every verification call.

Get started​

If you are enrolled in the closed beta, the Getting Started guide takes you from zero to your first verdict in under 5 minutes, and the API Reference covers schema details and all available options. If you are not yet in the beta, contact support@truebees.eu to get started.

Interactive API docs are also available at verify.truebees.eu/docs.

]]> Stefano Tavonatti https://gitlab.com/StefanoTavonatti