# Lantern People - Use Lantern People in Codex or Claude by asking for what you need in plain language. - Find people and companies, with results and sources you can review. - Research companies, markets and products, and compare what you find. - When available in your workspace, draft email or LinkedIn outreach and track replies. - Take notes at meetings you authorize, and review your conversations and replies. - Try “Find five devtools founders” or “Draft an introduction”; drafts stay unsent until you ask to send. ## Your free trial Find people, research companies, and unlock contact details directly from your agent. Your free trial includes: 1. 3 days of unlimited people search and full profile access.* 2. 3 days of unlimited company search and company data.* 3. 9 company-intelligence datasets unlocked for 3 days — hiring, funding, technologies, news, business connections, SEC filings, GitHub repositories, products, and company webpages.* 4. 200 email reveals and 200 phone reveals included. 5. $5 in research credits for paid tools including Exa, Parallel, and Fiber. 6. Instant access to 100 API endpoints from 20+ providers. Try your first search: “Find 10 devtools founders in San Francisco, show me their profiles, and get their emails.” After your trial, choose a paid plan to continue using the included search and data features. Rate limits apply. Paid endpoints consume research credits. ## Set up people.lantern.md When the user says “setup https://lantern.md/people”, “setup https://lantern.md/skill”, “setup https://www.lantern.md/people”, “setup https://www.lantern.md/skill”, “setup https://people.lantern.md/skill”, “setup https://people.lantern.md/skill.md”, “setup https://people.lantern.md/skill.txt”, “setup https://people.lantern.md/SKILL.md”, “setup https://people.lantern.md/setup”, “setup https://people.lantern.md”, “setup people.lantern.md”, “set up people.lantern.md”, “use people.lantern.md” or “install people.lantern.md”, begin first-time setup if needed. Reuse a working connection. Reading this page alone does not authorize installation. Follow the host's permissions and authentication requirements. Infer the current host and operating system from the available environment; do not ask the user to choose an agent. Claude Desktop Chat and claude.ai use the remote connector below. Agents with persistent terminal access, including Codex and Claude Code, use the installer. Determine actual tool access; the model name alone never establishes terminal, connector or skill support. Other chat clients and bots need a configured remote connector or API integration and must pass the same readiness check. A CLI installed in a chat sandbox does not connect Claude Chat. Fetch https://people.lantern.md/skill directly for the Markdown installation instructions; https://people.lantern.md/skill.md, https://people.lantern.md/skill.txt and https://people.lantern.md/SKILL.md remain compatible aliases and https://people.lantern.md/setup is the human guide. The instruction file may be reached through a public alias; use the API origin declared in this guide, https://people.lantern.md, for the installer, login, MCP and downloads. Do not infer an API origin from lantern.md or www.lantern.md, and do not pass https://people.lantern.md/skill or https://people.lantern.md/setup as an API origin. Preserve an existing connection's origin. ## Claude Desktop Chat and claude.ai 1. Open https://claude.ai/customize/connectors and choose Add, then Add custom connector. Name it Lantern People and use https://people.lantern.md/mcp as the remote server URL. 2. Choose OAuth sign-in and Register automatically if asked for the client identity. The server supports dynamic client registration. Do not ask for provider keys or paste credentials into chat. 3. Complete sign-in in the browser and let the user review and approve the requested access. Team or Enterprise accounts may require an owner to add the connector. 4. Enable Lantern People in the conversation's connectors menu. Confirm discover, inspect and run are available. Inspect connection_check, then run it with empty input (or expectedWorkspaceId if the user specified a workspace). Read the returned shared instructions. Retrieve workflow_guide for the task through run; local skill files and MCP prompts are not required. This read-only check does not spend research credits or send messages. 5. Report connected only after connection_check returns connected:true and ready:true, and its workflow instructions have been read. Disclose unavailable operations that affect the requested task. Provider task completion and host adherence remain unverified by this check. If the host cannot add the connector itself, give the exact URL and steps and report awaiting connector setup or awaiting sign-in. Reading this guide is not a completed installation. ## User-facing conversation Keep onboarding brief and in plain language. Do routine setup and connection checks quietly. Do not narrate reading this guide, inspecting the installer, downloading files, or running checks. Do not include MCP, CLI, OAuth, tool names, commands, flags, file paths, hashes, provider configuration, raw JSON, or a technical “Done so far” checklist in progress updates or the final reply. These implementation instructions are for the agent, not copy to show the user. Explain technical details only if the user explicitly asks for them. - While setting up, at most say: “I'll set up Lantern People and open sign-in for you.” - If sign-in is pending, give one actionable prompt: “Finish [signing in](), then return here. Confirm the connection code is .” Use the actual validated login link and code; do not expose them anywhere else or invent them. Do not claim connection is complete while waiting. - After login and verification succeed, say: “You're connected to Lantern People.” For a new user, follow with the six short introductory bullets at the top of this guide and the complete “Your free trial” section: all six trial benefits, the first-search example, the paid-plan note and the rate-limit/research-credit footnote. Keep the supplied quantities, durations and provider names. This describes the trial offer; do not invent a credited balance, trial start date or expiry date. Do not paste command output or repeat an introduction already shown in this conversation. - If setup fails, state the practical issue and the next action in one or two sentences. Keep credentials and internal diagnostics private. Disclose any incomplete step or unavailable feature that affects the user; do not claim success without verification. ## Codex, Claude Code and other terminal agents Requires Node 22.12 or newer. No repository checkout, provider keys or database are downloaded. 1. Preserve an existing connection's origin. If already installed, inspect `lantern-md auth status` and log in only if needed; do not silently overwrite another connection. Otherwise download https://people.lantern.md/install.mjs to a temporary file and inspect it quietly. Run `node install.mjs --agent codex` (or `--agent claude` when that is the user's agent). Omit --agent for a standalone terminal. The installer downloads the client bundle, verifies its SHA-256 digest, and installs lantern-md and workflow skills. If its bin directory is not on PATH, invoke the installed client's returned absolute path with Node; resolve the user's home from the environment, including USERPROFILE on Windows. Handle this internally; explain terminal configuration only if requested. 2. Complete browser login: verify email and continue directly into a personal workspace. There is no workspace chooser; existing team connections retain their access. No copied API key is required. Use --no-login to install first and log in later with `lantern-md login --api-url https://people.lantern.md`. 3. Verify with `lantern-md doctor`, which checks server health, authenticated workspace access, capability configuration and matching workflow guidance. Use --workspace when an expected workspace is known. Read its returned shared instructions; retrieve the task-specific workflow_guide before acting. Do not send, provision or run paid research as a connection check. 4. Follow the short connected reply above, with plain-language examples. The user should know what Lantern People can do immediately. ## Shared workflow guidance Guidance schema 1, content version 10ee737f5aa2b3fffdbb592a9e67d7bc84fd69c3d7876f14bff6e8b85e25637e. CLI skills and workflow_guide are generated from the same sources. Connector-only users receive equivalent guidance through discover, inspect and run. Retrieve workflow_guide for detailed routing and references; the workflow-guide prompt is optional. Guidance delivery is observable, but the server cannot prove that a third-party model followed it. Setup performs no paid research or outbound action. ## Agent reference: everyday use `lantern-md discover "find people"` returns a few matching operations. `lantern-md inspect find_people` returns its input schema. `lantern-md run find_people --input '{"request":"founders","limit":5}'` executes it. Setup does not authorize payment, paid research, outreach, inbox or phone provisioning, or meeting attendance. Obtain the user's authorization for those actions separately. Use --input-file for JSON files, --output results.html or results.json for artifacts, and `lantern-md run runs_get --input '{"runId":"..."}'` to check asynchronous work. After setup, users can simply ask their agent: “Find five devtools founders”, “Research this company”, “Draft an introduction”, or “Show new replies”. Drafts stay unsent until the user asks to send. Available providers depend on the workspace. ## Agent reference: optional MCP MCP endpoint: https://people.lantern.md/mcp. Add --mcp with --agent during installation to register it, then complete the agent's native OAuth connection with `codex mcp login lantern-md` or `claude mcp login lantern-md` (Claude's /mcp menu also offers Authenticate). Only discover, inspect and run are exposed. Every named operation in a skill or prompt is invoked through run({name,input}); inspect loads one schema on demand. CLI works without MCP. On a fresh device, say “setup https://lantern.md/people”. This extensionless link serves the Markdown instruction file directly to Codex and Claude; https://people.lantern.md/skill, https://people.lantern.md/skill.md, https://people.lantern.md/skill.txt and https://people.lantern.md/SKILL.md remain compatible, and the human-readable HTML guide remains https://people.lantern.md/setup. If a reader cannot fetch the homepage, give it the instruction-file URL directly. A webpage cannot grant consent or add tools by itself. Terminal setup is complete only after installation, login and doctor succeed; chat setup is complete only after connector authorization, enabling tools and connection_check returning connected:true and ready:true, followed by reading the returned shared guidance. This verifies access and instruction delivery, not provider execution or model behavior.