BlogFor those that won't leave their coding agent

Discover Agents · Coming soon

Deploy an agent just by asking.

Stand up an agent that knows one thing cold — your raise, your product, your repo — and put it where the conversation happens. You configure it through the agent you already use. Powered by Lisa's infrastucture.

Get early access See how it works

Configure with

01 · Configure in your coding agent

✻ claudediscover.me · mcp

> Deploy a Discover agent for the Project X raise.

Load the deck, financials, and FAQ. Keep it link-only.

⏺ agent_create name: "project-x-raise"

⎿ preset created · visibility: unlisted

⏺ agent_corpus_ingest ~/Projects/x

⎿ deck.pdf · financials.md · faq.md

⎿ indexed 142 passages

⏺ Live → discover.me/jamie/raise

⎿ humans can chat · agents can call it over MCP

02 · Talk to it anywhere you embed it

Project X — Raise roomgrounded · won't invent

Ask me anything about the Project X round.9:41 AM

What's the round size, and how much is committed?9:42 AM

A $3M seed at a $15M post. About $1.1M is committed so far.deck.pdf · p.129:42 AM

Who's leading it?9:43 AM

That's not in what I was given, so I won't guess — I've logged the question for Jamie. Want an intro?9:43 AM

Ask about the raise…

01·How it works

Load it. Gate it. Deploy it.

01·Load it

Point your agent at the docs, repo, or files it should know. It ingests and indexes them into a private corpus — no forms, no uploads.

02·Gate it

Set who can reach it: public, unlisted by link, or specific connections. The agent answers only from what you loaded.

03·Deploy it

Get a link and an MCP endpoint. Embed the chat beside a deck, next to a file, or on a page — and let other agents call it directly.

What you ship

Reachable at a link. Embeddable anywhere.

Deploying hands the agent a public address and a drop-in chat widget. Share the link, or paste the embed beside your deck, docs, or pricing page — and machines get the same agent over MCP.

Reachable at a link

Every agent gets a public address. Send it to anyone — they talk to it in the browser, no install. Keep it unlisted and only people with the link get in.

discover.me/jamie/raise

Embed the chat

Paste one snippet to drop the chat beside your deck, docs, or pricing page. Every embed stays in sync with the corpus.

<iframe
  src="https://discover.me/jamie/raise?embed=true"
  width="420" height="640"
  style="border:0;border-radius:24px;box-shadow:0 20px 60px rgba(0,0,0,.12)"
  title="Ask Jamie's agent" loading="lazy">
</iframe>

02·One agent per job

An agent for anything worth explaining.

The raise room: A data room for Project X. Load the deck, financials, and FAQ; gate it to people you share the link with. It answers diligence questions 24/7 and tells you what they asked.
A support agent: Point it at your product docs. Customers — and their agents — get grounded answers about how it works, with the source attached.
A docs agent for your repo: Drop it next to an open-source project. It answers questions about the API and conventions straight from the README, manifests, and code.
Your representative: An agent that knows your work and speaks for it when you can't be in the room. One job among many — not the umbrella.

03·Two surfaces

Powered by Lisa's infrastucture.

Every agent is both an embeddable chat for people and a callable endpoint for machines. Drop the chat beside your deck or docs, and let someone else's agent reach yours over MCP to get a grounded answer back. It's the agent-era version of an API to your work.

04·Why it's safe to share

It answers from what you gave it.

Answers from what you gave it

It draws only from the corpus you loaded, and cites the source. When the answer isn't in there, it says so and logs the question for you — it does not invent numbers, customers, or facts.

You set who can reach it

Public, unlisted by link, or scoped to specific connections. Deploy a public docs agent and a private investor room from the same place, with different doors.

Every conversation comes back to you

See what people asked, where they got stuck, and what got escalated. A read-only agent that captures the conversation is intelligence a static page can't give you.

Read-only by design

These agents answer. They take no actions, run no tools, and don't modify their own knowledge. Safe to put in front of a stranger.

For agents

An agent reaching another agent.

A deployed Discover agent is a knowledge-backed endpoint your own agent can call over MCP. Ask it a question, get a grounded answer with its sources, and carry that back into your work.

MCP endpoint https://api.discover.me/mcp

Connect your agent →

Early access

Be first to deploy an agent.

Loading…