Background Removal for Content & Publishing Pipelines

Trigger from CI/CD, webhooks, or automation platforms. One HTTP endpoint, no account, no rate limit on paid requests.

100% Private
AI-Powered
No Upload Required

Content teams, developers, and automation platforms need reliable image processing that fits into existing workflows. The Clear Canvas x402 API is a single HTTP endpoint — no SDK required, no account to manage, no rate limit on paid requests. Use it from GitHub Actions, Zapier, n8n, Make.com, or any platform that can make an HTTP POST request.

Why Use Clear Canvas

  • Single HTTP endpoint — works with any HTTP client or automation platform
  • No rate limit on paid requests — run as many as your pipeline needs
  • EXIF metadata stripped automatically — privacy-safe for content workflows
  • Works with Zapier, n8n, Make.com, GitHub Actions, and custom webhooks
  • Pay only when you process — 402 discovery probes are free
  • Testnet support — validate your pipeline on Base Sepolia before going live

How It Works

  1. 1

    Pick your automation platform

    Choose where background removal fits in your workflow: a CI/CD step, a CMS media processor, a Zapier action, or a custom webhook handler. The API is plain HTTP — it works anywhere.

  2. 2

    Configure an HTTP POST step with your image

    Set Content-Type to image/png, image/jpeg, or image/webp. Send the raw image bytes as the request body. The first request returns HTTP 402 with payment details.

  3. 3

    Handle the x402 payment step

    Use the Coinbase x402 SDK to sign a $0.05 USDC transfer and attach it as the X-PAYMENT header. Most automation platforms support custom headers — set it as a step output and pass it forward.

  4. 4

    Pass the result to the next pipeline step

    On HTTP 200, the response body is your transparent image. Write it to a CDN bucket, attach it to a CMS asset, or feed it into the next processing step.

Frequently Asked Questions

Do I need to install an SDK?

No. The API is plain HTTP and works with any HTTP client. An x402 client library (available for TypeScript and Python) makes payment signing easier, but you can implement the payment header manually if you prefer.

Can I use this in GitHub Actions?

Yes. Add a step that POSTs your image binary, reads the X-PAYMENT value from a repository secret wallet, and writes the 200 response body to your artifact directory or uploads it to storage.

Is there a Zapier or n8n integration?

Not a pre-built node yet. Use Zapier's Webhooks by Zapier action or n8n's HTTP Request node with custom headers to implement the x402 payment flow. Full documentation is in the integration guide.

What happens to my image data?

Images are processed in memory and never stored to disk. EXIF metadata is automatically stripped before processing. Nothing is persisted after the response is sent.

How do I control spending in a pipeline?

Manage your budget by controlling the USDC balance in your pipeline wallet. When the balance runs out, requests return HTTP 402 (payment required) and your pipeline can alert you to top up.

Ready to Get Started?

No sign-up needed. Your images stay on your device.