# snapWONDERS — including Vaultify snapWONDERS is a photo and video forensic analysis and media conversion platform. It exposes what digital media secretly contains: GPS coordinates, device fingerprints, encoder signatures, steganographic payloads, manipulation evidence, and 80+ forensic checks. Vaultify is the steganography product within the snapWONDERS suite: hide encrypted files invisibly inside photos and videos, and reveal them. Core analysis and steganography are available with no account required. Pro plans provide extended limits, priority processing, and advanced features — see https://snapwonders.com/pricing for details. Available on clearnet, Tor (.onion), and I2P. The API and the MCP endpoint route on all three networks, but in practice MCP is used over clearnet — most AI tool clients cannot reach .onion or .b32.i2p addresses. ## Steganography tools (Vaultify) - Hide a file inside a photo or video: https://vaultify.snapwonders.com/upload/hide - Reveal a hidden file from a photo or video: https://vaultify.snapwonders.com/upload/reveal ## How steganography works in Vaultify - Payload encrypted with AES-256; key derived using Argon2id key stretching - Encrypted payload embedded using LSB steganography across cover photo or video pixel data - Output is an ordinary-looking photo or video — no visual difference, no metadata indicating payload - Extraction requires the correct passphrase and the Vaultify reveal tool ## Analysis tools (snapWONDERS) - Forensic photo and image analysis: https://snapwonders.com/upload/analyse-photo-or-image - Forensic video analysis: https://snapwonders.com/upload/analyse-video - Media conversion (video/image format conversion): https://snapwonders.com/convert-features ## Forensic capabilities (80+ checks) - Error Level Analysis (ELA) — detects re-saved and manipulated regions in JPEG images - DQT JPEG encoder fingerprinting — identifies camera firmware or software that created a JPEG - Huffman table fingerprinting — secondary JPEG encoder signal - GPS and location analysis — precise coordinates, altitude, bearing, reverse-geocoded address - Device fingerprint profiles — matches claimed camera Make/Model against accumulated signal data - Steganography detection — LSB analysis, chi-square, RS analysis, sample-pair, polyglot, trailing data - Metadata privacy audit — EXIF, IPTC, XMP, MakerNote, Windows XP fields, serial numbers - Video forensic analysis — MP4, MKV, WebM, AVI, MOV; encoder, codec, HDR, DRM detection - AI detection — C2PA Content Credentials (signed AI declarations and camera-capture proof), AI declarations in the file's own metadata, known generator watermarks, and a trained pixel analysis that can still catch many AI images after labels are stripped, most from older AI tools and fewer from the newest - Noise field analysis, anti-forensics detection, temporal plausibility, serial number format checks ## Image format support JPEG, PNG, WebP, GIF, HEIC/HEIF, AVIF, BMP, TIFF, DNG, JPEG XL (JXL), and 13 camera RAW families: Canon CR2/CR3, Nikon NEF, Sony ARW, Fujifilm RAF, Olympus ORF, Panasonic RW2, Pentax PEF, Samsung SRW, Hasselblad 3FR/FFF, Leica RWL, Epson ERF, Kodak DCR. ## Video format support 350+ format variants including MP4, MOV, MKV, WebM, AVI containers with H.264, H.265/HEVC, VP8, VP9, AV1, MJPEG, and many more codecs. ## API and MCP integration All APIs are hosted at https://snapwonders.com/api. The MCP server is at https://snapwonders.com/mcp. - REST API status: https://snapwonders.com/api/status - OpenAPI 3.x spec: https://snapwonders.com/api/openapi.json - Swagger UI: https://snapwonders.com/api - MCP server (JSON-RPC 2.0, protocol 2025-03-26): https://snapwonders.com/mcp ### Uploading files MCP tool calls carry JSON, so file bytes travel over plain HTTP alongside the MCP session. There are two upload methods: - Direct (recommended): a single POST to https://snapwonders.com/api/upload with the file as the request body and headers X-Api-Key, X-Upload-Uid, X-Filename, Content-Type. No base64 metadata, no byte offsets. Accepts files up to 95 MB (99,614,720 bytes); the exact figure is returned as max_upload_bytes by every session-create call, so read it rather than assuming. The response reports ready_for_job_start, so no separate verification call is needed. Send X-Client-Upload-Id to make a retry safe. - Resumable (TUS): https://snapwonders.com/api/tus — required above 95 MB, and better on unreliable connections or when progress reporting is needed. No per-file size cap is applied at upload time; size is checked when the job is started, against per-tier total-size and file-count limits. A 413 from the direct endpoint names the size limit and the TUS endpoint in its response. MCP tools — discovery (no API key required): `status`, `vaultify_get_started`, `snapwonders_get_started` MCP tools — steganography / Vaultify (X-Api-Key required): `vaultify_session_create`, `vaultify_session_files`, `vaultify_job_start`, `vaultify_job_status`, `vaultify_job_results` MCP tools — forensic analysis (X-Api-Key required): `snapwonders_analyse_session_create`, `snapwonders_analyse_session_files`, `snapwonders_analyse_job_start`, `snapwonders_analyse_job_status`, `snapwonders_analyse_job_results`, `snapwonders_analyse_result` MCP tools — media conversion (X-Api-Key required): `snapwonders_convert_session_create`, `snapwonders_convert_session_files`, `snapwonders_convert_job_start`, `snapwonders_convert_job_status`, `snapwonders_convert_job_results` ## Official SDKs - Python (3.10+): pip install snapwonders — https://github.com/snapWONDERS/snapWONDERS-SDK-Python - JavaScript / TypeScript (Node 18+): npm install @snapwonders/sdk — https://github.com/snapWONDERS/snapWONDERS-SDK-JavaScript - PHP (8.2+): composer require snapwonders/sdk — https://github.com/snapWONDERS/snapWONDERS-SDK-PHP - Go (1.21+): go get github.com/snapWONDERS/snapWONDERS-SDK-Go Developers hub: https://snapwonders.com/developers ## About Built by Kenneth Springer (goldenSoftwareENGINEERS, ABN 72 080 510 827). Personal site and author profile: https://kennethbspringer.au Origin story: https://kennethbspringer.au/our-story