Ship content-processing workflows without vendor glue
You're maintaining Puppeteer for screenshots, Sharp for images, Tesseract for OCR — each with its own install headaches and breaking changes. Iteration Layer gives solo developers and small dev teams stable workflow contracts for extraction, transformation, and generation.
One output feeds the next
APIs that cover every step of EU content workflows — ingestion, transformation, generation, and exports. One key, one credit pool, and structured JSON responses designed to chain together.
Extract inputs
Turn documents, websites, and other sources into structured output.
Document Extraction
Extract structured data from documents with confidence scores.
Document to Markdown
Convert documents, images, and websites into clean Markdown.
Website Extraction
NewExtract typed JSON from public web pages with citations.
Audio Extraction
Coming SoonTranscribe audio and extract structured data with speaker labels.
Generate outputs
Create images, spreadsheets, and files from the same workflow state.
Image Transformation
Resize, crop, upscale, and convert images in one request.
Image Generation
Compose dynamic images from layers, text, QR codes, and fonts.
Document Generation
Generate PDF, DOCX, EPUB, and PPTX files from JSON content.
Sheet Generation
Generate XLSX and CSV sheets with formulas and styles.
EU AI workflow runtime
Run document, image, and file steps through one EU-hosted workflow layer with shared API conventions and billing.
You're dealing with this every day
Here's what changes when you stop juggling tools and start building pipelines.
Five libraries, five failure modes
Puppeteer for PDFs, Sharp for images, Tesseract for OCR, a CSV parser for spreadsheets — each with its own API style, error handling, and Docker configuration.
One API, every capability
Extract documents, transform images, generate PDFs, spreadsheets, and images — all from one SDK with structured JSON in and out. One set of docs, one set of conventions.
Three vendors, three invoices
Separate accounts, separate API keys, separate invoices. Every new cloud service adds credentials to manage and another bill to reconcile.
One key, one credit pool
A single API key and a shared credit pool across every operation. One invoice, one dashboard, one set of credentials to manage.
Glue code at every seam
Piping the output of one service into the input of another means format conversion, error handling, and retry logic you write and maintain yourself.
Structured output, no glue
Every API returns typed JSON designed to feed into the next. Extract data, then generate a report from the result — no format conversion or model-response parsing layer.
Real-world pipelines, ready to ship
Each recipe chains multiple APIs into a complete workflow. Pick one, tweak it, and deploy — or use it as a starting point for your own pipeline.
Compress Image to Target File Size
Compress an image to fit within a specific file size in bytes using quality-first compression.
Convert Document for Knowledge Base
Convert external documents — specs, contracts, reports — to markdown for knowledge base ingestion.
Convert Document for RAG Ingestion
Convert a document to clean markdown suitable for chunking and embedding in a RAG pipeline.
Convert Image Format
Convert an image between PNG, JPEG, and WebP formats with quality control for web optimization.
Convert Website to Markdown for RAG
Extract clean title, summary, markdown sections, and source metadata from a public documentation page for RAG ingestion.
Convert Document to Markdown
Convert PDF, DOCX, HTML, or image documents to clean, structured Markdown.
Official SDKs for every major language
Install the SDK, set your API key, and start chaining requests. Full type safety, automatic retries, and idiomatic error handling included.
European by design
Your data is processed on EU-hosted infrastructure and never stored beyond temporary logs. Zero data retention, GDPR-compliant workflows, and a Data Processing Agreement are available for every customer. Learn more about our security practices .
EU-hosted core processing
Application and processing infrastructure runs in Europe, with provider-scope ISO 27001 and BSI C5 evidence documented for procurement reviews.
Zero data retention
Customer files and processing results are not stored after the request. Usage logs are retained for 90 days and automatically deleted.
Clear answers for security teams
Give reviewers the answers they need up front: where files are processed, what is retained, which subprocessors are involved, and how AI inputs, outputs, review gates, and audit records move through each workflow.
Pricing
Start usage-based. Switch to a subscription when your volume becomes predictable.
Usage-based
Graduated pricing. Your effective rate decreases automatically as monthly usage grows.
- No monthly commitment
- Pay only for credits used
- Automatic volume discounts as usage grows
Predictable volume
Fixed recurring credit packs with lower effective credit prices for steady usage.
- Lower effective per-credit prices
- Fixed recurring credit packs
- Predictable monthly budget
Try Iteration Layer with 100 credits
Start with one shared trial pool before choosing subscription or pay-as-you-go billing.
Solving real problems, step by step
Vendor sprawl, GDPR headaches, broken pipelines — we wrote about the problems you're facing and how to fix them.
The Model Is Not the Moat. The Orchestration Layer is.
Model choice is becoming interchangeable for many agent workflows. Durable systems depend on schemas, routing, review, state, and outputs.
Composable APIs vs. Point Solutions: Total Cost of Ownership for Content Processing
Multi-vendor stacks vs unified platforms — integration time, credential sprawl, billing reconciliation, and concrete TCO calculations for a typical 5-project agency.
Building a Multi-Client Document Pipeline with One API
A practical guide to setting up project-scoped API keys, per-client extraction schemas, shared credit pools, and budget caps for agency document processing.
Frequently asked questions
What file formats can I process?
Can I chain multiple operations together?
What real workflows do you run with these APIs?
What languages and SDKs do you support?
How long does it take to get started?
How does pricing work?
What happens when the API returns an error?
Where is my data processed?
Build your first workflow in minutes
Chain our APIs into a workflow you can test with your own data during the 7-day trial.