Clay
Clay is an AI platform whose mission is to connect opportunity through intentions and personalities. It is built to understand what people are trying to become, what opportunities they are ready for, and which collaborators, projects, communities, jobs, events, or partners fit their personality and timing. Clay is not a chatbot, not a resume parser, not a dating app, and not a generic marketplace.Where to start
Introduction
Read the product contract, the core primitives, and how Clay reasons about fit.
Quickstart
Stand up the workspace, run the backend, preview specs, and start the mobile app.
The published site mirrors the layout in
apps/specs/docs.json. If a page moves, the navigation
moves with it in the same change.Product surfaces
Intentions
The direction signal — goals, constraints, timing, and readiness.
Personalities
The fit signal — communication, rhythm, motivation, taste, social energy.
Opportunities
The taxonomy of what Clay can route toward, and how fit is explained.
Consent
How translated fit signals leave Clay only with explicit user permission.
Companion experience
How Clay should feel in daily use — proactive, curious, useful, and safely interruptible.
Curious pet memory
How Clay asks, learns, and organizes personal patterns into user-owned MDX knowledges.
User experience flows
End-to-end journeys, user stories, and the consent-aware action loop.
Mobile capture flow
The first iOS screen — intention, readiness, personality signal, consent, next action.
Visual system and workflows
Design language
The tactile plasticine system, token meanings, and component behavior.
Themes
The Acid Lime, Editorial, and Dark Plum theme packs and when each is used.
Mascot
Clay the mascot — anatomy, expressions, animations, evolution, and rendering.
Components
Buttons, inputs, cards, dialogs, navigation, profile, chat, and feed contracts.
Motion
Motion tokens, easing curves, and reduced-motion guarantees.
3D and Rive pipeline
How mascot, motion, and 3D scenes are generated and shipped across surfaces.
Landing page sections
The section-by-section breakdown of how
apps/landing pitches Clay.Engineering and reference
Architecture
Tour the backend, landing app, mobile app, specs site, and generated client boundaries.
Workspace
The pnpm + Turborepo layout and per-package scripts that ship Clay.
@clay/client
The Fern-generated TypeScript SDK consumed by every Clay app.
Backend overview
The Hono + OpenAPI contract that runs on the Cloudflare Worker.
API reference
Implemented HTTP routes, Zod schemas, and the generated OpenAPI contract.
OpenAPI pipeline
How Hono route schemas become the OpenAPI YAML consumed by Fern.
Environment & bindings
Wrangler variables, bindings, and the secret-handling guardrails.
Deploy
Ship the API, landing page, and specifications site to Cloudflare.
Decision records
Browse the ADR index for the durable choices behind Clay’s product and platform.
Glossary
Look up canonical terms used across Clay’s product and platform.
CI
The scripts and Turborepo tasks that act as Clay’s CI gate before deploy.
Auth model
How Clay intends to authenticate users, services, and Cloudflare-bound requests.
Testing policy
Why Clay ships without an automated test framework, and what stands in for tests.
What you will find here
Product
- Intentions as a first-class signal
- Personalities as a first-class signal
- Opportunity across people, teams, projects, jobs, events, communities, and partners
Platform
apps/backend— Cloudflare Worker, Hono, OpenAPIapps/landing— Next.js static export pitching siteapps/mobile— Expo iOS app for intention capture and opportunity workflowsapps/specs— this Mintlify specifications site, exported to Cloudflare Pages