Welcome
Welcome to the Pixel Systems API documentation.The Pixel Systems API verifies the authenticity of files. Submit a file and receive a verdict: an assessment of whether the file is AI-generated or manipulated, a confidence level, and a per-dimension breakdown your workflow can act on. Verification runs on Pixel's own forensic pipelines, built for both images and documents (PDF), on infrastructure we own end to end.
Core capabilities
The API currently supports:
- Verify a file in one call. POST /v1/assess accepts an image file (JPEG, PNG, or HEIC/HEIF) up to 25 MB as multipart/form-data. By default the call waits up to 30 seconds and returns the verdict; if analysis is still running it returns 202 and you poll the job.
- Read results later. GET /v1/jobs/:jobId returns a job's status, with the verdict once it completes; GET /v1/jobs browses previous submissions with pagination.
- Authenticate with API keys scoped to an application, sent as Authorization: Bearer <api_key>. See Authentication, rate limits, and error codes.
Not a developer?
You do not need to write code to use Pixel. The dashboard's no-code option runs the same verification as the API: drag a file into your application, and the verdict appears in the browser with the full per-dimension breakdown. Start with the drag and drop guide.
SDKs
TypeScript SDKs are available on request, ahead of their public release: a client SDK for browser uploads and a server SDK for backend integrations. Contact us for access. The REST API covers the same operations in the meantime.
Explore the docs
Jump to the guides and reference material for your integration:
- Get started — create an application, choose an integration path, and run your first verification
- Concepts — applications, jobs, files, and API keys
- API reference — authentication, error codes, and endpoint docs
- Contact — how to reach the team