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.

• Generate a key at vaultify.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 which of three things 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, expired, or inactive.

Already have a key starting with vlt_? It stays valid — nothing to do. Only the prefix on newly generated keys changed.

3 The APIs

Three products share one session → job → poll → download shape. Files upload over the resumable TUS protocol (out of band), 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).

Add it to Claude Code in one line:

5 SDKs Preview

Official client libraries wrap the API and the fiddly TUS upload into one idiomatic call, so a whole hide job is a couple of lines. Python first, then JavaScript/TypeScript.