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.
Zero data retention
Made & hosted in the EU
100 trial credits
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.
Native SDKs for TypeScript, Python, and Go. OpenAPI spec for everything else. MCP server for AI agents and Claude Code skills. n8n integration for visual workflows.
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.
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.
PDFs, DOCX, XLSX, CSV, PNG, JPEG, WebP, HEIF, GIF, SVG, HTML, Markdown, and plain text. See the Document Extraction docs for full format details.
Can I chain multiple operations together?
Yes. Every API returns structured JSON designed to feed into the next. Extract data from a document, generate a report from the results, create a thumbnail — all with one credit pool and one auth token.
Official SDKs for TypeScript, Python, and Go with full type safety and automatic retries. Full OpenAPI 3.1 spec for code generation in any other language. MCP server for AI agent frameworks.
How long does it take to get started?
Sign up, start the 7-day trial, get an API key, and make your first request in under five minutes. See the Getting Started guide.
How does pricing work?
Every API call costs a fixed number of credits. Credits are shared across all APIs — no per-service billing. Start with 100 trial credits, then choose a subscription or pay as you go. See Credits & Pricing.
What happens when the API returns an error?
Credits are automatically refunded for failed requests — no action needed. This applies to validation failures, server errors, and async webhook processing failures. See Errors.