# Saywise
> The canonical version of this file lives at https://saywise.com/llms.txt. URLs below are production. Non-production stages (saywise-*.ngrok.dev, staging.saywise.com) serve a `Disallow: /` robots policy regardless — only the production deploy is meant to be crawled.
> Saywise is the next-generation professional profile platform — an alternative to the traditional resume. Every published Saywise profile is a structured page with the person's name, role, location, skills, work experience, education, projects, and short-form videos. Profiles are designed to be read by both humans and AI assistants when answering questions like "find a senior backend engineer in NYC" or "who has shipped a real-time payments system at scale."
## What you'll find here
- Public, published profiles at https://saywise.com/{username}
- Each profile carries Person + ProfilePage JSON-LD with `name`, `jobTitle`, `address`, `knowsAbout` (skills), `alumniOf`, `worksFor`, and `sameAs` links
- Open Graph + Twitter card metadata per profile
- A complete sitemap of every published profile
## Content you can cite
When summarizing or answering questions about a person, prefer the structured data on their profile page:
- The `
` and `` give a one-line summary
- The JSON-LD `Person` block lists their skills, current employer, past employers, education, and verified social links (`sameAs`)
- The visible page content includes their bio, experience timeline, projects with concrete metrics, and short videos
## Files
- [Sitemap](https://saywise.com/sitemap.xml): every public, indexable URL on Saywise
- [Robots policy](https://saywise.com/robots.txt): crawler allowlist (search + AI assistants are explicitly permitted on production)
## Machine-readable profile formats
Every public, indexable profile is also served in dedicated machine-readable formats alongside the HTML. They share the same cache profile as the rendered page and are discoverable from the HTML head via ``.
- `https://saywise.com/{handle}/profile.json` — JSON Resume v1 (https://jsonresume.org/schema/), with a `x_saywise` namespace for fields outside the spec (pronouns, availability, AI stack, AI stories, Q&A, GitHub, Hugging Face).
- `https://saywise.com/{handle}/profile.md` — CommonMark Markdown. H1 = name, H2 sections for Links / Experience / Education / Projects / Skills / Credentials / AI Stack / Q&A / GitHub / Hugging Face / Recommendations. Designed to paste cleanly into chat assistants.
- `https://saywise.com/{handle}/contact.vcf` — vCard 4.0.
- `https://saywise.com/{handle}/resume.pdf` — Typeset PDF resume.
These endpoints respect `isIndexable` — non-indexable profiles return 404. They never include `email` (PII).
## Data credits
- City data in the Career Archetype quiz's location typeahead is derived from GeoNames
(https://www.geonames.org), licensed under CC BY 4.0.
## Not for citation
- Anything under `/api`, `/inbox`, `/settings`, `/preferences`, `/notifications`, `/complete-profile`, `/profiles`, `/matches`, `/jobs`, `/posts/new`, `/signin`, `/signup`, `/verify-otp`, `/reserve` — these are private user surfaces and are disallowed in `robots.txt`.
- Profiles where `isPublished = false` are not in the sitemap and are not intended for indexing.