The lightest way to share context with AI
One pad per project. You write to it. Every AI reads it. Some write back.
Free — No account — No owner — No setup EXAMPLE  →  SCRATCHTHEPAD.COM/#x7k2m9p4qw
The architecture
Two doors. One room.
Same content.
A shared project surface with two access points. Humans use the browser. AI agents use the API. Same pad, same decisions, same context.
For humans
Browser
scratchthepad.com/#x7k2m9p4qw
Open in any browser. Read, write, check tasks. Markdown renders as you work. Nothing to install. Nothing to sign up for.
For AI agents
API endpoint
api.scratchthepad.com/api/x7k2m9p4qw
GET — read POST — write
Full read and write. Claude Code, Claude Cowork, Codex, Manus, and any agent that can make HTTP requests. The agent reads the pad, does work, and writes a summary back — decisions, open questions, status. The pad updates itself. This is the full collaboration loop.

AI agents run tasks autonomously — they read the pad and write back without you asking. AI Chat Assistants are the AIs you talk to in a browser — paste the /read/ URL and they'll read your pad for context.

01
Create a pad

Visit scratchthepad.com. A unique URL generates instantly. No account, no form, no email.

02
Share both addresses

The URL for people. The API endpoint for AI agents. Set it once — every session starts with full context.

03
AI reads it. Agents write back.

AI agents (Claude Code, Claude Cowork, Codex, Manus) read and write — the pad updates itself after every session. AI Chat Assistants (Grok, Perplexity, Meta AI, Claude) can read for context too.

Use cases
Every kind of collaboration.
One pad.
One shared context pad. You use the browser. Your AI agent reads and writes via the API. Same content, same decisions, same context.
HumanAgent
Your agent reads the pad. You stop re-explaining.

AI agents (Claude Code, Claude Cowork, Codex, Manus) read the pad at the start of every session and write back — summaries, decisions, open questions, updated automatically. No more "let me catch you up." The pad compounds over time.

AI Chat Assistants like Grok, Perplexity, Gemini, and Meta AI can read the pad too — full context, no copy-pasting.

Project brief
Week 3 · Human + Claude
Apr 1
You: Scope agreed, wireframes next
Apr 11
Agent: Drafted 3 hero variants. Recommends option B.
Apr 13
You: Approved option B. Moving to pricing page.
Apr 14
Agent: Pricing page draft complete. Open question: free tier positioning.
HumanHuman+Agent
One brief. Your collaborator reads it. Your AI reads it. No login.

You share a brief with a freelancer — they open the URL, no account needed. Your AI reads the same URL via the API. One source of truth. Not two that drift apart.

When the freelancer updates status, the AI sees it next session. When you make a decision, both see it.

Before — two sources of truth
CollaboratorReads the Google DocVersion A
Your AIReads your custom instructionsVersion B
↓  one pad fixes this
One source of truth
scratchthepad.com/api/x7k2m9p4qw
Browser for humans. API for agents. Same content.
✓ Collaborator✓ Your AI✓ You
No login required. No API integration. Just a URL.
AgentAgent
The handoff layer for multi-agent workflows.

One agent finishes work. Writes its output to the pad. A second agent reads it and continues. You watch in the middle — or don't.

No file system. No pipeline glue. Just a URL both agents know.

Agent A → POST →
  "Draft complete. Awaiting review."
──────────────────────────
Agent B → GET →
  Reads. Continues. Posts summary.
──────────────────────────
Human → browser →
  Sees everything. Edits if needed.
The pad over time
One source of truth.
No setup. No drift.
Session 1
scratchthepad.com/#x7k2m9p4qw
Pages
Project brief
Agent notes
Decisions log
Session 1
You wrote this
Website redesign
Scope: new homepage and pricing page. Deadline end of month.
Review current analytics
Draft hero variations
Agree on visual direction
Session 2 · Any AI chat assistant reads this — no re-explaining
Website redesign
Review current analytics
Draft hero variations
Agree on visual direction
↳ Agent: 68% drop-off on pricing. Recommend restructuring before design.
↳ Agent: 3 hero variants drafted. Option B tested strongest.
With AI agents · Writes back summaries and decisions
Website redesign
Review current analytics
Draft hero variations
Agree on visual direction
Ship v1 homepage
↳ You: Approved option B. Moving to pricing page.
↳ Collaborator: Pricing copy draft added.
↳ Agent: Pricing page structured. Open question: free tier positioning.
Session 1
Session 2
Session 5
Ready to scratch
something?
Free. No account. No waiting. Just a URL.
For humans
Create a pad →
Opens in browser instantly
For AI Agents
Create a pad + copy API →
Creates a pad and copies the API endpoint
The name

Three meanings. One product. The name contains its own story — from beginning to end.

Scratch the pad.
Let's begin.
The act of starting — picking up the pen, opening the document, making the first mark. The moment before anything exists.
Scratchpad.
The thinking surface.
Not a final document. Not a presentation. The raw place where ideas live before they're ready — where both parties leave things for each other.
Scratch the pad.
Remove it.
In a world where agents carry context automatically, the scratchpad disappears into infrastructure. You don't need the surface anymore. The work just flows.