Build with the snapWONDERS API

1 Getting started — your first call

Everything is one REST API at https://snapwonders.com/api. Your very first call needs no key and no upload — just confirm the service is up:

Then make your first authenticated call — creating a hide session. A working key returns an upload_uid; a 401 tells you exactly what to fix (see the next step):

2 Get your API key

Create a key on your account, then send it as the X-Api-Key header on every request. Keys start with sw_ — send the whole key.

• Create an account, then click the activation link we email you. Keys created on an unverified account are rejected by the API — this is the most common reason a brand-new key returns 401.
• Generate a key at snapwonders.com/profile/api-keys — free accounts work, no credit card.
• Header on every authenticated call: X-Api-Key: sw_your_key_here
• Health and the get-started/discovery calls need no key.

If a call returns 401, the error code tells you exactly what is wrong, so you are never guessing:

• missing_api_key — no X-Api-Key header was sent.
• malformed_api_key — a header is present but not a valid key shape.
• invalid_api_key — a well-formed key that is not recognised, revoked, or expired.
• account_not_verified — your key is fine. The account that owns it has not verified its email address. Click the activation link, then retry with the same key. Generating a new one will fail in exactly the same way.
• account_inactive — your key is fine, but the account cannot use the API.

3 The APIs

Three products share one session → job → poll → download shape. Files upload over plain HTTP — one request per file — then you start a job and poll it to completion.

4 MCP — for AI agents

The same capabilities are exposed as tools over the Model Context Protocol, so an AI agent (Claude, Cursor, VS Code Copilot, and others) can call them directly. Transport is Streamable HTTP, spec 2025-03-26.

• Endpoint: https://snapwonders.com/mcp
• Auth: the same X-Api-Key header (three discovery tools — status, vaultify_get_started, snapwonders_get_started — need no key).

For example, adding it to Claude Code is one line:

Working on files on your own machine

The endpoint above is a remote server, which means it cannot see your files — you upload them first, then point the agent at the session. If you would rather say "analyse ~/Downloads/photo.jpg" and have it just work, there is also a local MCP server: it runs on your own machine, so it can read the file, upload it, run the job and save the results back to disk in one step.

It needs uv and an API key. For Claude Desktop, add this to your MCP configuration:

Four tools — analyse_file, hide_file, reveal_file and convert_file — each doing a whole task end to end. Source, full configuration and the security notes are in the GitHub repository.

5 SDKs

Official client libraries wrap the API — including picking the right upload method and handling resumable transfers — into one idiomatic call, so a whole hide job is a couple of lines, in Python, JavaScript/TypeScript, PHP, or Go.

6 Other languages — generate a client

No SDK for your language yet? The API ships a full OpenAPI 3 spec, so you can generate a typed client for Ruby, Java, C#, Kotlin, Swift, Rust, and dozens more with OpenAPI Generator: