# About Liftli (machine-readable)

> Who builds Liftli and what that means in practice. Human-readable version: https://liftli.ai/about

Liftli is an AI content strategist for LinkedIn, X (Twitter) and Substack. It is not a scheduler and
not a chat wrapper. It runs inside the AI assistant the user already has — Claude, Claude Code,
ChatGPT, Codex or Cursor — over the Model Context Protocol.

## Who builds it

Liftli is built and run by Oded Tsamir (https://www.linkedin.com/in/odedtsamir/), working solo. It is
operated as a sole proprietorship based in Israel. It is **not** an incorporated company, and there is
no team behind the logo.

## Why it exists

Oded spent years shipping product for other people, with almost none of it visible: real experience,
real opinions, and a LinkedIn profile that said nothing. Existing tools all wanted him to sit at a desk
and describe his week to a text box — but the week was already over, and the ideas had already
happened, in calls, in commits, in things said out loud. Liftli catches those instead.

## What being one person means

- Support is a real person answering email, usually within one business day. No ticket queue.
- The roadmap moves in days, not quarters.
- No enterprise procurement and no sales team. Free tier with no card; paid plans are self-serve.
- Liftli is early. Some surfaces are in beta, and that is labelled where it is true.

## Handling of user work

Liftli reads a source only when pointed at one, through a connector the user already controls. Nothing
is scanned in the background, and nothing publishes without the user approving it.

- Privacy policy: https://liftli.ai/privacy
- Terms: https://liftli.ai/terms

## For agents and developers

- OpenAPI 3.1: https://liftli.ai/openapi.json
- MCP manifest: https://liftli.ai/.well-known/mcp.json
- Agent directive: https://liftli.ai/ai-agents.md
- Developer docs: https://liftli.ai/developers
- MCP endpoint: https://mcp.liftli.ai/mcp