Portable context, on one link

The link that speaks for you.

Brief your stand-in once. It gathers what you need, answers what it can, and returns a clean record of the rest.

Let my agent handle it

Or try it right here.

Brief your stand-in

What should this link do? I can ask questions, answer them, or both.

Live stand-in Waiting

Your stand-in appears here

Pick an example or describe the job in your own words.

Context capsule Ask + answer

You review before it ships stand.in/your-link

Visitors need no account Answers come only from what you approved Unanswered questions return to you

Here’s the problem.

You explain it. Then you explain it again.

Context lives in calls, docs, inboxes, and whoever happened to be in the room. Every handoff loses the nuance.

You explain it once A call, a doc, a voice memo

Someone needs more The nuance never made the handoff

Your stand-in answers The loop ends at the link

How it works

Brain dump in. Briefing out.

Stand.In turns what you know into a reviewed link that keeps working after you send it.

Brief it

Talk, type, paste notes, attach files. It listens first and asks second.
Approve every fact

Each extracted piece of context waits for your yes. Edit it, keep it private, or cut it.
Send one link

Readers get the briefing first, then a conversation that knows its sources.
Close the gaps

Whatever it could not answer comes back to you as a short list, not a transcript.

What it does

One link, working three jobs.

Ask for context, give it away, or let one conversation do both.

Gather what you need.

Interview clients, candidates, or collaborators before the first call. It follows the useful threads.

What would make this project successful for you?

A launch the support team can actually maintain.

What would make it hard to maintain?

Give what you know.

Publish a readable page with grounded chat behind it.

"Can I approve the homepage?"Yes, once legal signs off and the value proposition stays unchanged.

Do both.

Answer first, then gather the missing details in the same conversation.

For agents

Humans get the page. Agents get the context.

Your agent can draft everything. Nothing reaches a reader until it is approved.

Filing and approving are separate steps, on purpose. Everything an agent files waits as a proposal, and anything sensitive is held back until it is confirmed out loud.

create_stand_in

“Build a Capsule from these notes.” One call, ready for review.

add_context / add_file

Plans changed? File the update. You approve it.

list_questions / answer_gap

See every question your link could not answer.

Point an agent at it

Point your agent at this page and it finds the capsule on its own. Or connect it directly:

Your agent · authoring

Generate a token under Agent access, then:

claude mcp add --transport http standin \
  https://usestandin.vercel.app/api/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"

Their agent · reading and asking

No account, no key. The share link is the credential:

claude mcp add --transport http standin-respond \
  https://usestandin.vercel.app/api/respond/mcp

Prefer a terminal? npx usestandin ask <link> "your question". Full protocol for machines at /llms.txt.

Pricing

Start free. Make it yours when you're ready.

Everything is free while we are in beta. Here are the plans as they will land.

Free

Your first stand-in.

One published stand-in
Full capture, briefing, and ask
Your asks inbox
About 100 answered questions a month
Carries the Stand In mark

Start free

Stop repeating yourself.

Brief it once. Send the link. Let it do the explaining.

Create a stand.in · 2 min