SONIC CHECK API

api.soniccheck.io · HARRY_V37

SONIC CHECK API

The service behind soniccheck.io. It runs HARRY, the evidence-screening analyzer, and returns candidate evidence and method-specific similarity signals for qualified human review.

  • Controlled private beta
  • Paid public scanning closed
  • Human review required
Browse the reference Check live status
Public probes
# Liveness
curl https://api.soniccheck.io/api/healthz
{"ok":true}

# Deployment identity
curl https://api.soniccheck.io/api/version
{"service":"sonic-check-api",
 "analyzer":{"versioned_label":"HARRY_V37", …}}

Probes

Service status

Liveness is checked from your browser every time this page loads. Readiness detail is read live wherever the API allows it, and otherwise comes from a timestamped snapshot published with this page.

Checking the API…

Not checked yet

Liveness

—

GET /api/healthz

Readiness

—

GET /api/readyz

Analyzer

—

GET /api/version

Release posture

—

GET /api/product-contract

Basics

Working with the API

JSON over HTTPS. Public probes need no credentials; customer endpoints act on the signed-in soniccheck.io account.

Base URL

https://api.soniccheck.io/api

Every route sits under /api. The service root itself has no page.

Format
JSON over HTTPS; uploads are multipart/form-data
OpenAPI
api.soniccheck.io/openapi.json (OpenAPI 3.1.0)
Swagger UI
api.soniccheck.io/docs
Analyzer
HARRY_V37, reported by GET /api/version

Authentication

Customer endpoints take the Clerk session token from a signed-in soniccheck.io session:

Authorization: Bearer <token>

Tokens are verified against clerk.soniccheck.io and must be issued for soniccheck.io. There are no standalone API keys during the beta.

Browser access

Responses are shared with https://soniccheck.io only. Other web origins can't read them from a browser, so use the command line or a server for anything outside the web app.

Limits

  • Audio uploads up to 100 MB per file.
  • Remote audio URLs aren't accepted in the current deployment.
  • Each scan reserves one scan entitlement.
  • PDF reports need the report add-on or Pro.

Errors

401
Missing or invalid session token
403
Signed in, but not allowed
413
Upload over the size limit
422
Request failed validation
503
Gated feature, such as checkout during the beta

Bodies follow {"detail": …}.

Quick start

First requests

The first two run as-is. The last one needs a session token from your own signed-in account.

Read the public product contract
curl -s https://api.soniccheck.io/api/product-contract \
  | jq '{release_posture, paid_public_scanning, decision: .claims.decision_boundary}'
List plans (AUD)
curl -s https://api.soniccheck.io/api/plans \
  | jq '.[] | {id, price, currency, checkout_enabled}'
Screen a track (signed in)
curl -s https://api.soniccheck.io/api/scans/upload \
  -H "Authorization: Bearer $SONICCHECK_SESSION_TOKEN" \
  -F title="Working title" \
  -F region=AU \
  -F file=@./my-track.mp3

Decision boundary

SONIC CHECK reports candidate evidence and method-specific signals. It does not determine plagiarism, authorship, ownership, infringement, legal clearance or admissibility.

  • originality evidence screening
  • candidate evidence
  • method-specific similarity signal
  • recording-identity candidate
  • human review required