DevToolKit API

Automate PDF, image, and OCR workflows

Build privacy-aware automation for background removal, PDF compression, file conversion, and OCR pipelines with clear processing limits and future usage-based credits.

Early accessBackground removalPDF processingOCR plannedUsage-based later

API access is in early development. Current endpoints and limits may change.

What teams could automate

Use cases for ecommerce, documents, OCR, and developer automation.

Early access

Ecommerce product photos

Remove backgrounds, resize assets, and prepare product images at scale.

Background Removal API

Planned

Document automation

Compress PDFs, convert files, and prepare documents for upload portals.

PDF Processing API

Planned

OCR pipelines

Extract searchable text from scanned documents and images.

OCR API

Planned

Developer workflows

Generate repeatable file-processing flows from apps, scripts, and internal tools.

Workflow API planned

Planned API endpoints

Paths, auth, and payloads may change before public launch.

Not production docs

Images

MethodPathStatusNotes
POST/v1/images/remove-backgroundEarly accessInternal gateway exists — public keys not issued yet.
POST/v1/images/compressPlannedImage compression with size and quality presets.
POST/v1/images/resizePlannedResize assets for web, catalog, and delivery pipelines.
POST/v1/images/convertPlannedConvert between common image formats.

PDF

MethodPathStatusNotes
POST/v1/pdf/compressPlannedCompress PDF files with quality presets.
POST/v1/pdf/convertPlannedConvert PDF pages to images or office formats.
POST/v1/pdf/ocrPlannedOCR text extraction from documents and scans.
POST/v1/pdf/mergePlannedMerge multiple PDFs into one output file.

Jobs

MethodPathStatusNotes
GET/v1/jobs/{id}PlannedPoll job status, retries, and completion metadata.
GET/v1/usagePlannedUsage tracking and credit consumption reporting.

Developer code preview

Example integration shape — not a live contract.

https://api.devtoolkitapp.com
Planned example
curl -X POST https://api.devtoolkitapp.com/v1/images/remove-background \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -F "image=@product.jpg" \
  -F "mode=high_quality"

Base URL and auth are not final. Do not use in production yet.

Designed for reliable file jobs

1

Upload file

Send image or PDF input with explicit limits.

2

Create job

Receive a job ID and processing status.

3

Process with limits

Run with timeout, size, and credit guards.

4

Download result

Fetch output via signed URL when ready.

Signed URLs plannedTemporary storage plannedTTL deletion plannedUsage tracking plannedRetries/status planned

Usage-based pricing planned

The API is planned to use credits and monthly included usage. Heavy image, OCR, and PDF jobs may consume more credits depending on file size, pages, and provider cost.

Exact credit pricing is still in testing — not finalized.

Starter credits

Planned

For prototypes and testing.

Growth usage

Planned

For repeat business workflows.

Business / API

Planned

For higher limits, invoices, and support.

API privacy and processing model

Temporary processing

Files are processed for the requested job and should be deleted according to TTL rules.

Clear limits

File size, page count, timeout, and credit limits should be visible before jobs run.

No hidden AI

AI actions should be explicit, consent-based, and priced by action later.

Do not send files you do not own or have permission to process.

Join DevToolKit API early access

Tell us what you want to automate: background removal, PDF compression, OCR, conversion, or batch workflows.

  • Name
  • Email
  • Company (optional)
  • Use case
  • Expected monthly volume

No backend form yet — contact links only. No API keys are issued from this page.

Frequently asked questions

Honest answers about API early access.

Is the API live today?

Not as a public production API. Background removal may be reachable through internal development gateways, but there are no public API keys or stable developer docs yet.

Which APIs are planned first?

Background removal is the first likely candidate, followed by PDF compression, conversion, and OCR endpoints as usage-based credits are defined.

Will there be API keys?

Yes, API keys are planned for authenticated access, rate limits, and usage tracking. They are not available from this page today.

How will files be stored?

Temporary storage with TTL deletion is planned. Files should be processed for the job duration only, then removed according to retention rules.

Will there be usage limits?

Yes. File size, page count, timeout, queue priority, and credit consumption limits are planned and should be visible before jobs run.

Can I use API for customer files?

Only if you have permission to process those files and your use complies with applicable privacy and data-handling requirements.

Are AI features included?

AI-powered actions should be explicit, opt-in where relevant, and credit-based later. They will not run hidden in the background.