Meishi
meishi

Your Identity Context for AI

Your Identity
Context for AI.

Write who you are once. Every AI agent starts already knowing you — your background, your projects, your decisions. And as you work, agents write back what they learn, so your Meishi grows with you.

Free to start. No credit card.

Every new AI. Same introduction.

Claude

"I'm a PM building a SaaS tool. Our stack is Next.js and Postgres. We've decided to..."

Cursor

"I'm a PM building a SaaS tool. Our stack is Next.js and Postgres. We've decided to..."

ChatGPT

"I'm a PM building a SaaS tool. Our stack is Next.js and Postgres. We've decided to..."

You paste your background. You explain your stack. You repeat your decisions.
Every. Single. Session.

AI tools have no memory between sessions, no shared understanding across tools, and no way to know what you've already decided. You become the integration layer — manually re-briefing every agent, every time.

How it works

Three steps. Then never again.

01

Write once

Fill in who you are, what you're building, and what you've already decided. Plain text.

02

Connect an agent

Paste one snippet into any agent's system prompt. That's it.

03

They remember

Every agent starts informed. Decisions accumulate. Context compounds.

The API

What agents see

On session start, an agent calls GET /api/v1/context and receives everything you've written — your role, current projects, past decisions, things not to repeat, and every note agents have left over time.

Agents can write back with /write or leave observations with /append. Every change is logged, attributed, and reversible.

GET /api/v1/context

// every agent reads this on session start

{

"context_memory": "I'm a product engineer and solo founder. I think in systems,
write in bullet points when planning, and go deep before I go broad.
I have low patience for hand-holding but high patience for nuance.
I prefer being challenged over being agreed with. Native Hebrew speaker,
working in English. I make decisions fast and revisit them rarely.",
"who_i_am": "Senior PM turned founder. 8 years in B2B SaaS. Strong in
product strategy, systems design, and API-first thinking.
Weaker in frontend polish and visual design. I write code but
I'm not an engineer by training. I prefer TypeScript over JS.",
"what_im_building": "Meishi — a portable AI identity layer. Users write their
context once and every agent reads it via API. B2B SaaS,
solo founder, pre-revenue. Stack: Next.js 15, Neon Postgres,
Clerk auth, Vercel, Resend. Domain: meishi-ai.com.",
"decisions_made": "Web-only for now, no mobile app. AES-256 encryption
before DB — per-user keys, never plaintext in storage.
Free tier first, no freemium upsell mechanics. Shipping fast,
polishing after traction. No pricing page until first 100 users.",
"dont_repeat": "What REST APIs are. How React hooks work. Why TypeScript
is useful. How Tailwind classes work. What a JWT is.
Basic git commands. What a product-market fit is.",
"notes": "[2026-03-08] Prefers responses under 200 words unless asked.
[2026-03-10] Decided against pricing page until 100 users.
[2026-03-12] Rebranding from Context Passport to Meishi.
[2026-03-14] Landing page live. Focus shifts to first users."

}

Built right

Nothing you have to think about.

🔒

AES-256 encrypted

Your context never touches our DB as plaintext. Unique key per user.

📋

Full audit log

Every read and write is recorded — who, when, before/after.

🕓

Version history

Snapshots before every agent read. Restore any version instantly.

🔑

Scoped API keys

Read-only, write-only, or full access. Revoke any key instantly.

Works with any agent

Plain Bearer token REST API. Claude, GPT, Cursor — all of them.

📝

Append-only notes

Agents leave timestamped notes. You read them. Nobody overwrites them.

FAQ

Questions

Stop re-explaining yourself.

Set up once. Every AI knows you.

Create your passport →