Free is live — no invite needed
Generate across providers. Keep the receipts.
One API across every provider you connect — with cross-provider failover, byte-exact custody, and a C2PA audit trail on every output.
Free tier, no credit card. Pro & Team are on the way.
Don't stop using fal — stop depending on fal.
Every visual here is a real pipeline output — model and provider named on each. No stock, no mockups.
Keep the receipts
A provider rate-limits mid-job; the endpoint fails over and keeps going — byte-exact, C2PA intact, every step on an append-only ledger.
One API across the providers you connect
fal
Replicate
Runware
Black Forest Labs
OpenAI
ElevenLabs
WaveSpeed
EvoLink
Kie.ai
PiAPIThe problem
Provider infrastructure is built to serve inference — not to be depended on.
Your outputs vanish
Providers delete generated files aggressively — Replicate after about an hour, fal after about seven days. If a provider URL is your only copy, you have already lost the master.
Models retire under you
Vendors sunset models within months of launch. A pipeline pinned to one model inherits that model's lifespan — usually without notice you can act on.
429s arrive with your traffic
Capacity errors spike exactly when you launch. A single-provider pipeline turns someone else's overloaded GPUs into your incident.
Aggregators fail over within themselves
Every aggregator retries inside its own catalog. When the aggregator itself degrades, every model behind it degrades with it. Nobody fails over across companies.
What Wakemark does
Route it. Keep it. Prove it.
Three jobs, one API, above every provider you connect. You bring the keys and pick the models; Wakemark keeps the pipeline standing, keeps the outputs, and keeps a receipt for every step.
Route across companies
Capability-based routing over the providers you connect — different companies, not one catalog. When a provider returns a 429, a 5xx, or a timeout, the job fails over to the next automatically and your endpoint keeps answering. Retries fire only on provider-side failures, never on your own bad input, so failover never double-spends.
Keep every byte
Every output is streamed into durable storage and SHA-256-verified before the provider's URL expires — byte-exact, never transcoded, never “optimized”. The master stays yours long after the provider's own link is gone.
Prove the whole chain
C2PA Content Credentials on every output, an append-only event ledger of each provider interaction, and a lineage graph from prompt to published asset — the receipts an aggregator, sitting inside one catalog, structurally can't produce.
Cross-provider by design
One prompt. Every provider you connect.
Capability routing means the same job can run on any provider behind your keys — so a 429 or an outage at one becomes a failover, not an incident. Below is a single prompt, submitted through five providers on Wakemark's own adapters. Same brief, five renders — each one streamed into byte-exact custody with its own receipt.
You bring the keys and pick which providers to route across. Wakemark keeps the endpoint answering when one of them can't — and keeps a receipt for whichever one did.
Own your masters.
Generated media is an asset your organization paid for. Wakemark treats it that way: hash-verified custody, under your control, for as long as you need it — not until a provider's cleanup job runs.
BYOK storage
Your bucket. Your bytes.
Our receipts.
Point Wakemark at an S3-compatible bucket you own — R2, AWS, Backblaze, Storj, or your own MinIO. Generated output lands there byte-exact, hashed and provenance-stamped. The storage is yours; we keep the record.
- Verified on connect
A live write → read → delete round-trip runs before we save — a wrong or under-permissioned key fails loudly, naming the exact problem.
- Byte-exact custody
Every output lands with its sha256 and a provenance sidecar. C2PA bytes untouched; the ledger records where it went.
- We never cross the line
Presigned, short-lived reads keep your bucket private. On the way out, we drop our access — the objects stay yours.
- Free, forever
The bytes never touch our bucket, so BYOK storage costs nothing — at any retention, on every plan.
round-trip verified on connect
Works with any S3-compatible bucket
EU AI Act · Article 50
The transparency deadline is dated. Your evidence should be too.
Article 50 requires outputs of generative AI systems to be marked in a machine-readable format and detectable as artificially generated. The Commission's Code of Practice on marking and labelling (final version published 10 June 2026) names C2PA Content Credentials as an exemplar mechanism — the same standard Wakemark stamps on outputs today.
2 Aug 2026
EU AI Act Article 50 transparency obligations apply.
2 Dec 2026
Deadline for machine-readable marking for systems already on the market.
€15M / 3%
Maximum penalties — €15M or 3% of worldwide annual turnover.
Designed to support Article 50 workflows
- Machine-readable marking by default — C2PA Content Credentials attached to outputs as they move through the pipeline.
- An append-only event ledger recording every generation: provider, model, parameters, timestamps, raw responses.
- Byte-exact archived outputs whose hashes match what the ledger says was produced.
- A lineage graph connecting each published asset back to the jobs and inputs that made it.
Wakemark is infrastructure, not legal advice. Article 50 obligations sit with the organizations that provide and deploy AI systems — how you meet them is a decision for you and your counsel. Wakemark gives you the marking, custody, and audit trail to build on.
For developers
One request. Every provider you connect. No babysitting.
curl -X POST https://api.wakemark.ai/v1/jobs \
-H "Authorization: Bearer wk_live_…" \
-d '{
"capability": "text-to-image",
"input": { "prompt": "product hero shot, studio light" },
"routing": {
"providers": ["fal", "replicate", "runware"]
},
"idempotency_key": "launch-hero-001"
}'
# fal returns 429 at your launch spike → the job fails over
# to replicate; the ledger records both attempts.
{
"id": "job_01JZKQ6M3R…",
"status": "succeeded",
"provider": "replicate",
"assets": [{ "sha256": "9f2c…", "c2pa": true }]
}Cross-provider failover
Retries route across companies, not within one catalog — and only on provider-side failures, never on your own bad input.
Byte-exact custody
Outputs are streamed to storage and SHA-256-verified. Provider URL expiry stops being your problem.
Hard spend caps
Caps are enforced before submit. A job that would cross the cap is rejected, not billed.
C2PA passthrough
Content Credentials are stamped and preserved through the pipeline, sidecars included.
Passthrough mode
Provider-specific parameters are forwarded untouched. The job still lands in the ledger; the output is still archived.
From the pipeline
Real outputs. Real receipts.
Every visual on this page is a real pipeline output of the model named in its caption — generated through Wakemark's own provider adapters and archived byte-exactly. On this wall: the Kling and FLUX families, MiniMax, Z-Image and more, served across fal, Replicate, Black Forest Labs, OpenAI, Runware and the aggregators. Hover to play. No stock, no mockups.
Every output has a byte-exact digest, the model and provider that made it, and an append-only ledger behind it — verify any asset's provenance for yourself, no account needed.
Pricing
Usage-based — never a markup on routed spend.
Free is live today — bring your own provider keys and start generating now. Pro, Team and Enterprise are on the way: join the waitlist and we'll tell you the moment billing opens. Nothing is charged today, and these numbers may change before general availability.
Free
Available now$0
no credit card
- Bring your own provider keys (BYOK)
- Capability routing + cross-provider failover
- Byte-exact output custody, audit ledger & lineage graph
- Public /verify + a receipt on every output
- 1,000 jobs/month
- 1 GB platform storage, kept indefinitely by default (configurable per project)
- Hard cap at the allowance — generation stops, never a surprise bill
Pro
Coming soon$19/mo
+ metered usage
- Everything in Free
- 5,000 jobs/month included, then $0.005/job
- 25 GB storage included, then $0.05/GB-month overage
- BYOK storage stays free forever, at any retention
- Hard spend caps you set yourself — never a silent overage
Team
Coming soon$99/mo
+ metered usage
- Everything in Pro
- Projects: per-project retention & routing policy
- 5 seats included, then $15/seat/month
- 100 GB platform storage included
- Org-level hard spend caps
- Priority support
Enterprise
Coming soonLet's talk
custom deployment & terms
- Everything in Team
- Private verification, SLA & DPA
- Dedicated deployment
- Advanced governance controls
FAQ
Honest answers
Is this just another aggregator?
No. Aggregators sell access to many models behind one API and fail over only within their own catalog. Wakemark is the layer above providers and aggregators: it routes across different companies, keeps byte-exact custody of the outputs, and maintains the audit trail. Keep your fal account — Wakemark makes it survivable.
Do you resell provider credits?
No. Wakemark is BYOK: you bring your own provider keys, and providers bill you directly at their own prices — no markup on routed spend. Keys are stored envelope-encrypted (a per-secret AES-GCM data key, wrapped by a KMS root key and bound to your tenant) and exist in plaintext only in memory, at the moment a request is signed.
Is the media on this page real?
Yes — every loop and still was generated through the providers Wakemark routes, and each caption names the provider and model that made it. No stock footage, no placeholders.
What happens to my bytes?
Every output is streamed into storage and verified against its SHA-256 hash — byte-exact, never transcoded, never “optimized”. Outputs live in durable custody long after the provider's own URL has expired. Your masters don't disappear.
When does Article 50 apply?
Article 50 of the EU AI Act applies from 2 August 2026. Systems already on the market before that date have until 2 December 2026 to implement machine-readable marking. The Commission's Code of Practice (final version, 10 June 2026) names C2PA Content Credentials as an exemplar marking mechanism. Penalties run up to €15M or 3% of worldwide turnover.
Does using Wakemark make me compliant?
No tool can make you compliant, and you should be suspicious of any that claims to. Wakemark is designed to support Article 50 workflows — machine-readable C2PA marking, a verifiable audit ledger, durable custody — but the legal obligations sit with your organization and depend on how you deploy. Bring your counsel; we bring the evidence trail.
I need a provider-specific feature your API doesn't model.
Use passthrough mode: provider-specific parameters are forwarded untouched, while the job still flows through the ledger, the output is still persisted, and C2PA marking still happens. You get the provider's exotic features and keep the audit trail.
Publishing AI-generated media into the EU?
The deadlines are dated and the wave is here. Free is live — start today, no invite needed. Pro and Team are on the way; their waitlists are on the pricing page.