Concepts
Core entities in the Pixel Systems API and how they fit together in a verification workflow.Job
A job groups one or more files submitted for verification in a single unit of work. Each job has a unique jobId and optional metadata. The API returns a job as a single JobResult envelope: a job-level status (processing, completed, or error) and, for single-file jobs, a verdict once completed — individual files are not listed in the response, and multi-file jobs report the job-level status only.The fastest flow is one call to Assess (POST /v1/assess), which creates the job, uploads the file, and waits for the verdict. To read a result later, poll the job until its status leaves processing. For quick uploads without code, use drag-and-drop in the dashboard, which creates the same jobs without an API key.Jobs are used to:
- Group related files and shared metadata for a case or batch
- Track per-file analysis status and results
File
A file is one uploaded asset on a job — usually an image. Each file has an id, name, type, and size, and is analyzed independently.The API accepts image uploads in JPEG, PNG, and HEIC/HEIF formats. Files must be at most 25 MB, at least 768px on the shorter side, and at least 0.5 megapixels for reliable analysis.Files are analyzed independently, but the public API reports one job-level status: a job stays processing until every file's analysis finished, then reports completed (or error if any file failed). A verdict is included for single-file jobs; per-file runs and per-file verdicts are not exposed by the public API.
Application
An application is a workspace inside your organization. It isolates jobs, files, API keys, members, and settings. Every API call is scoped to an applicationId.Organization admins create applications from the dashboard.Applications are used to:
- Separate environments or client projects within one org
- Scope API keys and job history
- Control team access and application settings
Pipeline
A pipeline is the set of checks Pixel runs on every file an application submits. Each application has exactly one, set when the application is created. To change it, contact support.The pipeline determines:
- Which file types the application accepts
- Which signals appear on a job result
- Which verdicts a job can return
- AI detection. Checks whether an image was generated or edited by AI. Returns AI generated, authentic, or inconclusive.
- E-commerce. Checks that a photo is an original camera capture rather than a screenshot, an image already published elsewhere online, or an AI generation. Returns verified, not verified, or inconclusive.
- Document authenticity. Checks PDF documents for signs of tampering and AI-written text, and reports what the document metadata says about its origin.
API key
An API key authenticates server-side requests to the Pixel Systems API. Generate keys per application from the dashboard.Send the key as a Bearer token in the Authorization header for endpoints such as submitting a file for assessment and reading job results.
Keep API keys on the server
Never expose API keys in browser code or public repositories. Rotate keys if they are compromised.