snap.com valid

Snap for Developers

Documentation for Snap developer tools. Each platform has different capabilities — do not assume a feature on one platform exists on another.

For agents: Snap for Developers docs: Lens Studio API reference, class guides and deprecation notices for Snap developer platforms.

lens studiosnap developersar lensesapi referencedeprecations

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T20:01:16.391Z. Cached copy · Source on snap.com

# Snap for Developers

> Documentation for Snap developer tools. Each platform has different capabilities — do not assume a feature on one platform exists on another.
>
> **Lens Studio** — Desktop application for creating AR Lenses. Supports face tracking, body tracking, hand tracking, world tracking, 3D objects, animations, materials, scripting (JavaScript/TypeScript), and the VFX and Material Editor.
>
> **Camera Kit** — SDK for integrating Snap AR Lenses into third-party iOS, Android, and Web apps. Provides camera session management, lens rendering, and lens scheduling. Does not support all Lens Studio features (e.g. no Spectacles-specific APIs and certain Snapchat-specific APIs).
>
> **Spectacles** — AR glasses platform. Supports hand tracking, spatial anchors, world query, depth sensing, voice input (ASR), Bluetooth, location, WebView, and multiplayer (Sync Kit). Uses TypeScript with Spectacles Interaction Kit (SIK) and UI Kit. Many APIs are Spectacles-only.
>
> **Snap Kit** — SDKs for social integration: Login Kit (OAuth), Creative Kit (sharing to Snapchat).
>
> **Games** — Building social-first games inside Snapchat Lenses: Game Suite, Connected Framework for live multiplayer, Character/Camera Controller, Joystick, Input Action, Leaderboard, and Turn Based components. Built with Lens Studio; connected to the camera and Snapchat's friend graph.
>
> **Web Lenses** — Web apps (HTML/JavaScript, for example built with PlayCanvas) zipped and published to Snapchat as Lenses through My Lenses, without Lens Studio. They run in a sandboxed webview with no network, camera, microphone, or motion-sensor access, and Lens Studio scripting APIs are not available. Snapchat features come through the Web Lens API (@snap/web-lens-api): leaderboards, Bitmoji, and storage.
>
> **Marketing API** — Snapchat ads ecosystem APIs: Ads API, Ads Gallery API, Conversions API, and Public Profile API. Includes tutorials, business onboarding info, and full reference docs.
>
> **API Reference** — Lens Studio scripting API and Snapchat for Web embeds.
>
> Use this file as an index. To get full content for a page, fetch the linked .md file (e.g. /spectacles/get-started/introduction.md).


## API Reference

- [Overview](/api/home.md): Find API references for each product.
- [Lens API Deprecation](/api/lens-api-deprecation.md): Guide to deprecated Lens Studio APIs, their modern replacements, and the timeline for when deprecated APIs will be blocked.
- [Assets](/api/lens-studio/Classes/Assets.md): Assets are resources imported into Lens Studio. See also: Importing and Updating Resources Guide
- [Components](/api/lens-studio/Classes/Components.md): Components are attached to SceneObjects and define object behavior. See also: Inspector Panel
- [Events](/api/lens-studio/Classes/Events.md): Events are triggered by certain criteria and can be bound in scripts to execute code. See also: Script Events Guide
- [Other Classes](/api/lens-studio/Classes/OtherClasses.md)
- [Providers](/api/
…

Related sites

Find similar publishers by meaning →

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=snap.com · GET /v1/domain/snap.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for snap.com:
1. POST https://agentwebmap.com/v1/sites/snap.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://snap.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/snap.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/snap.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.