# Welcome

> Source: https://pixelsystems.com/docs


Welcome to the Pixel Systems API documentation.

## What is Pixel?

Pixel verifies the authenticity of files. Submit a file and receive a result: a verdict on whether the file is AI-generated or manipulated, with the evidence behind it, so your workflow can act on it. A job can carry several files, and the API returns one result per file.

## How it works

Every verdict carries a confidence level and a per-dimension breakdown: each dimension's key and score, plus structured evidence where the analysis produced some, such as the camera make and model or the pages a reverse image search found. The API returns keys and values, not display text, so your integration renders them in its own words. Pixel informs the decision rather than making it: a reviewer can see why a file was flagged, and your workflow can branch on the result (auto-approve, route to review, or block).

Verification runs on Pixel's own forensic pipelines, built for both images and documents (PDF), on infrastructure we own end to end. The API accepts images (JPEG, PNG or [HEIC/HEIF](https://en.wikipedia.org/wiki/High_Efficiency_Image_File_Format)) and PDF documents; see [Assess a file](https://pixelsystems.com/docs/api/assess) (`/v1/assess`) for size limits and request details.

## How to use the docs

The docs are split into guides and reference:

- [Get started](https://pixelsystems.com/docs/get-started) walks through creating an application, choosing an integration path, and running your first verification.
- [Concepts](https://pixelsystems.com/docs/concepts) defines the objects the API works with: applications, jobs, files, and API keys.
- The [API reference](https://pixelsystems.com/docs/api) covers [authentication](https://pixelsystems.com/docs/api/authentication), [rate limits](https://pixelsystems.com/docs/api/rate-limits), and [error codes](https://pixelsystems.com/docs/api/error-codes), with one page per endpoint, starting at [Assess a file](https://pixelsystems.com/docs/api/assess) (`/v1/assess`).
- [No-code](https://pixelsystems.com/docs/no-code) covers running verifications from the dashboard, without writing code.

Integrating for the first time? Read Get started end to end, then keep the [API reference](https://pixelsystems.com/docs/api) open while you build. Evaluating Pixel without writing code? Go straight to the [drag and drop](https://pixelsystems.com/docs/no-code/drag-and-drop) guide.

## No-code verification

You do not need to write code to use Pixel. The dashboard's [no-code](https://pixelsystems.com/docs/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](https://pixelsystems.com/docs/no-code/drag-and-drop) guide.

## SDKs

TypeScript SDKs are available on request, ahead of their public release: a [client SDK](https://pixelsystems.com/docs/sdk/client) for browser uploads and a [server SDK](https://pixelsystems.com/docs/sdk/server) for backend integrations. [Contact us](https://pixelsystems.com/contact) for access. The REST API covers the same operations in the meantime.

## Contact us

To get started with Pixel, [contact us](https://pixelsystems.com/contact) or [book a demo](https://pixelsystems.com/book-a-demo). We set up your organization; from there, applications are self-serve in the dashboard, and so are API keys where your organization has API access.