Visork is in its pilot phase. There is no self-serve signup: access to the detection API is granted after a scoping call and platform verification. For a CSAM detection endpoint this is a deliberate control, not a waitlist — we verify who is calling the API before credentials exist.
How pilot access works
Every pilot follows the same four steps:
- Intro call. Thirty minutes: what you run, what you are processing, and what is forcing the decision now.
- Scoping. We agree the detection module, a threshold profile for your risk tolerance, and what a successful benchmark looks like.
- Benchmark. You receive an API key and 100 free analysis credits, and measure detection quality and latency against your own traffic — not our demo set.
- Commercial terms. We quote against the volume the benchmark actually showed. Nothing is signed before that number exists.
What a pilot expects from you
A pilot works best when:
- you operate an EU platform processing user-generated images,
- content volume makes manual review impractical,
- your engineering team can ship a REST call,
- someone owns trust & safety or compliance by name,
- you are willing to benchmark on real traffic.
It is probably too early if you need video, text, or grooming detection today, if a signed SLA is a precondition to piloting, or if there is no integration capacity for the next quarter.
What integration looks like
The integration surface is one REST endpoint: your backend submits an image, and the response carries a probabilistic score, the verdict against your configured threshold, and an audit-log entry. Where you call it is up to your pipeline — inline at upload time to block before publication, or asynchronously to feed a review queue.
Detection describes what the result means and how to reason about thresholds; Security & data handling describes what happens to the content you send.
Where is the API reference?
The full API reference — endpoint schemas, error codes, and integration examples — is shared during scoping rather than published here. The conceptual documentation is public precisely so that your engineers and your DPO can evaluate the service before the first call.
Ready to start? Request pilot access.