farcaster.xyz valid

Farcaster Snap Documentation

This file aggregates all Farcaster Snap documentation (2.0) for LLM consumption.

For agents: Aggregated developer documentation for Farcaster Snaps 2.0: building, integrating, persistent state, examples, HTTP spec and headers for LLM use.

farcaster snapssnap speccontent negotiationpersistent statehttp headers

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T14:26:44.556Z. Cached copy · Source on farcaster.xyz

# Farcaster Snap Documentation

> This file aggregates all Farcaster Snap documentation (2.0) for LLM consumption.
> Source: https://docs.farcaster.xyz/snap/

---

## Introduction

# Introduction

Snaps are simple, nimble apps embedded in Farcaster casts. They render in the feed and
respond to user input — buttons, sliders, text — without executing any code on the
client. A snap server returns JSON; the Farcaster client displays it.

> **Beta:** This is all still in beta and may change significantly over the next few
> weeks or months.

Using Claude Code? Tell your agent to

```bash
use https://docs.farcaster.xyz/snap/SKILL.md to build me an app that
```

## Learn

- [Building a Snap](/snap/building) — Ways to create a snap, from AI-assisted generation
  to manual implementation with the template.
- [Integrating Snaps](/snap/integrating) — How to serve snap JSON alongside your normal
  site using content negotiation on the `Accept` header.
- [Persistent State](/snap/persistent-state) — The key-value store available on every
  snap handler invocation for persisting state between requests.
- [Examples](/snap/examples) — Sample snap response payloads showing common UI patterns.

## Reference

- [Spec](/snap/spec-overview) — The full HTTP protocol: content negotiation,
  request/response lifecycle, versioning, and validation rules.
- [HTTP Headers](/snap/http-headers) — `Accept`, `Content-Type`, `Vary`, and `Link` for
  snap responses and fallbacks.
- [Elements](/snap/elements) — All 16 components: display, data, container, and field
  types.
- [Buttons](/snap/buttons) — The `button` component, variants, layout, and how POST
  payloads are constructed when a user taps.
- [Surfaces](/snap/surfaces) — The app surface where a snap interaction happens.
- [Actions](/snap/actions) — The 9 action types and their params.
- [Effects](/snap/effects) — Page-level overlays (confetti, etc.) that fire on render.
- [Constraints](/snap/constraints) — Per-component validation limits and URL rules.
- [Theme & Styling](/snap/theme) — How accent colors work and why snaps specify only a
  palette name rather than hex values.
- [Color Palette](/snap/colors) — The named palette colors available for accent,
  progress bars, and bar charts.
- [Authentication](/snap/auth) — How POST requests are authenticated with JSON Farcaster
  Signatures (JFS) and how servers verify them.

## Agents

- [Agents](/snap/agents) — Machine-readable docs, the skill file, and starting points
  for AI tools building or integrating snaps.
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=farcaster.xyz · GET /v1/domain/farcaster.xyz · 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 farcaster.xyz:
1. POST https://agentwebmap.com/v1/sites/farcaster.xyz/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://farcaster.xyz/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/farcaster.xyz/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/farcaster.xyz).
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.