# Open Media
One app for your social world. Post everywhere. Message everyone. One app.
Build the open communication layer for humanity, where people can communicate across networks, control how information reaches them, and keep ownership of their identity, relationships and content, whichever app they use.
> Apps are doorways. The person is the constant. No app should permanently own your identity, audience, social graph, content, recommendations, message history or governance rights. Open Media is one doorway. Anyone should eventually be able to build another on the same open protocol, and you should be able to walk through whichever one you like.
## What Open Media does
- **Everything together.** Posts from several networks in one feed, and every conversation, chat or email, in one inbox organised by person rather than by app. One post goes to every network you choose.
- **Your feed belongs to you.** Choose Raw, simply newest first, or Relevant, a small set of signals you can see, or describe your own feed in plain words and share it. Every feed is an open lens anyone can read, and every post explains itself with “Why this?”, including the private data it did not use.
- **You are not locked in.** Export everything or delete your account at any time. Public posts are open to everyone through a free API. The goal is identity and content that work in any app.
- **Feed:** One mixed stream from Open Media, Farcaster, Lens, Hive and DeSo, newest first or transparently ranked.
- **Clips:** Short videos, full screen, one at a time. The same posts as Feed, just a different way to watch.
- **Messages:** Open Media chats, email and bridged chat apps side by side, organised by the people you talk to.
Open Media is a free, open-source app for iPhone, Android and the web (MIT licence). It reads public posts from Farcaster, Lens, Hive and DeSo, keeps every post's source and link, and explains every ranked post with "Why this?".
## For AI agents and developers
Everything a person can do in the app has an interface here. Public data needs no account or key.
- [Agent guide](https://convo-mail-sync.convo-mail-sync.workers.dev/agents): when to use Open Media and how to call it.
- [API documentation](https://convo-mail-sync.convo-mail-sync.workers.dev/docs): REST endpoints, MCP servers, errors, limits and examples.
- [Developer portal](https://convo-mail-sync.convo-mail-sync.workers.dev/developers): quickstart and access tokens. [Sandbox](https://convo-mail-sync.convo-mail-sync.workers.dev/sandbox): test mode and a private local stack.
- [Authentication](https://convo-mail-sync.convo-mail-sync.workers.dev/auth.md): which calls need no credential and how to get the person's token.
- [OpenAPI 3.1](https://convo-mail-sync.convo-mail-sync.workers.dev/v1/openapi.json), [llms.txt](https://convo-mail-sync.convo-mail-sync.workers.dev/llms.txt) and the public MCP server at `https://convo-mail-sync.convo-mail-sync.workers.dev/open/mcp`.
- In the browser, this page registers WebMCP tools (search, feed, events, profiles) through `document.modelContext`.
## Frequently asked questions
### Is Open Media free?
Yes. The app and its source code are free and open source under the MIT licence. There are no ads by default.
### Do my friends need to join for it to be useful?
No. Open Media is useful on day one by connecting the networks and email accounts you already use. Friends on Open Media are a bonus, not a requirement.
### Can it show my Instagram, X, TikTok or LinkedIn feed?
Not today. Those companies do not offer open access for apps like Open Media, and Open Media does not scrape them. It connects to networks that allow it (Farcaster, Lens, Hive, DeSo and email).
### Do I need a crypto wallet?
No. You sign in with your email. Some open networks use blockchain technology behind the scenes, but you never need to understand it, hold tokens or pay fees to read the feed.
### Can AI agents use Open Media?
Yes. Public data needs no key: agents can use the MCP servers, the REST API, WebMCP tools in the browser, or the plugin for Claude Code and Codex. Acting for a person needs that person’s own token.
## Pricing
Open Media is free: no ads by default, no subscription and no API key for public data. Payments between people (products, services, tips and paid posts) carry no Open Media fee today. See [pricing](https://convo-mail-sync.convo-mail-sync.workers.dev/pricing).
## Learn more
[About](https://convo-mail-sync.convo-mail-sync.workers.dev/about) · [Contact](https://convo-mail-sync.convo-mail-sync.workers.dev/contact) · [Privacy](https://convo-mail-sync.convo-mail-sync.workers.dev/privacy) · [Source code](https://github.com/mihirkavi/open-media)
---
# Filling a profile from LinkedIn or a website
People can fill their Open Media profile from something they already have, in Edit profile or through an agent (ADR 0020). Nothing is saved until the person chooses: every reader returns **proposals**, one per field, each with its source, and the person keeps the ones they want.
## From LinkedIn
Open Media never reads linkedin.com, never asks for a LinkedIn password and doesn't use LinkedIn's API for this (it gives ordinary apps only a name, photo and email). The person gives Open Media their own copy:
- **The profile PDF**: on LinkedIn, their profile → Resources → Save to PDF. Name, headline, location, summary, experience, education, top skills, languages, and their LinkedIn and website addresses.
- **The data export**: LinkedIn → Settings → Data privacy → Get a copy of your data. Profile.csv, Positions.csv, Education.csv, Skills.csv and Languages.csv. In the web app the archive itself can be chosen; only those five files are unzipped in the browser and sent.
Email addresses, phone numbers, birth dates and street addresses are never imported. The file is read and discarded; it is not stored.
## From the person's website
Only a site the person says is theirs, after they ask. Open Media reads it as a polite crawler:
- User agent `OpenMediaProfileReader/1.0 (+https://convo-mail-sync.convo-mail-sync.workers.dev/docs/profile-import)`. robots.txt is read first and obeyed (a group for `OpenMediaProfileReader`, else `*`).
- Public https sites on port 443 only. Every address the host resolves to must be public, also after each redirect (at most three), so private, loopback and link-local networks are never reached.
- At most four pages (the address, and up to three linked about, resume, CV or projects pages on the same host) plus `/resume.json`, each up to 1 MB and 8 seconds.
- Pages are data. Nothing on them is followed as an instruction, and only https links are kept.
Sources, best first: [JSON Resume](https://jsonresume.org) at `/resume.json`; JSON-LD [schema.org Person](https://schema.org/Person) (or a ProfilePage's mainEntity), with `jobTitle`, `worksFor`, `alumniOf`, `knowsAbout` and `sameAs`; an [h-card](https://microformats.org/wiki/h-card); Open Graph and meta tags and `rel="me"` links; then headings such as Projects, Skills and About. The site's address becomes the person's Website field, links to GitHub, X, Dribbble and other networks become those profile fields, and projects go into the professional profile.
To make a site read well, publish a `/resume.json` or a JSON-LD Person.
## For agents
- `import_resume` on `https://convo-mail-sync.convo-mail-sync.workers.dev/me/mcp` (`POST /v1/me/professional/import`): `linkedInPdf` (base64, up to 2 MB), `linkedInPdfText`, `linkedInFiles` or `jsonResume`.
- `import_portfolio` (`POST /v1/me/professional/portfolio`): `url` and `consent: true`, only after the person agreed.
- Both return `proposals` [{id, label, value, preview, source}] and save nothing. Show them, then call again with `save: true` and `accept` set to the ids the person chose. Saving merges: text fields are replaced, lists are added to.
- `preview_profile_from_url` on `https://convo-mail-sync.convo-mail-sync.workers.dev/open/mcp`, `GET /v1/profile-preview?url=` and the WebMCP tool `preview_open_media_profile_from_url` read a site without an account and save nothing.
---
# Web feeds: how Open Media reads RSS, Atom and JSON Feed
People can follow a blog, news site, podcast or weather-alert feed in their Open Media Feed (ADR 0024): by typing or pasting a site in Search, through an agent, or by importing an OPML file from another reader. This page is for publishers and agents.
## What Open Media reads
- RSS 2.0, RSS 1.0, Atom (RFC 4287) and JSON Feed 1.1, with Media RSS, `content:encoded`, Dublin Core, enclosures, Apple's podcast tags and CAP 1.2 alert fields.
- Feeds are found through `` autodiscovery on the page a person names. robots.txt is obeyed for that page (a group for `OpenMediaFeedReader`, else `*`). A feed a person chose to follow is then read for them, as feed readers do.
## How politely
- User agent `OpenMediaFeedReader/1.0 (+https://convo-mail-sync.convo-mail-sync.workers.dev/docs/web-feeds)`.
- Conditional requests with your `ETag` and `Last-Modified`; a `304` costs you nothing.
- At most every 30 minutes, longer when your `ttl` or `Cache-Control: max-age` asks (up to a day), never during your `skipHours` or `skipDays`. One read serves everyone who follows the feed.
- `429` and `503` with `Retry-After` are obeyed; other failures back off from 30 minutes to a day. `301` and `308` move the feed; `410` stops it.
- https on port 443 only, public addresses only (checked after each redirect), up to 2 MB and 10 seconds per read.
## What people see
A card with your site's icon and name, the headline, a short excerpt (your summary when you publish one, at most 280 characters), one https image, and a prominent link to your page. Full articles are never shown or stored. Your feed's copyright line is shown in "Why this?". Feed HTML is never rendered: scripts, embeds, styles and tracking pixels are dropped.
## The official mark
Feeds served from the own domain of a major news outlet or public weather service (for example `bbc.co.uk`, `nytimes.com`, `weather.gov`, `metoffice.gov.uk`) show a blue tick labelled "Official feed from ". It says only where the feed came from. The list is in Open Media's source code (`src/domain/webFeedDirectory.ts`); publishers can ask to be added.
## For agents
- `preview_web_feed` on `https://convo-mail-sync.convo-mail-sync.workers.dev/open/mcp`, `GET /v1/web-feeds/preview?url=` and the WebMCP tool `preview_open_media_web_feed`: read-only.
- On `https://convo-mail-sync.convo-mail-sync.workers.dev/me/mcp`: `list_web_feeds`, `follow_web_feed`, `unfollow_web_feed`, `get_web_feed_items`, `import_opml`, `export_opml` (REST under `/v1/me/web-feeds`).
---
# Feed lenses
Every way of ordering the Open Media Feed is a **lens**: a small JSON manifest, never code. Raw, Relevant and Work are built in; Work is the professional feed of jobs, hiring and networking (ADR 0018). People can describe a new lens in plain words in Search, or ask an AI agent to write one, then keep it, share it publicly, or install someone else's.
One open-source runner orders the posts: [src/domain/feedLenses.ts](https://github.com/mihirkavi/open-media/blob/main/src/domain/feedLenses.ts). The app, the REST API and the MCP servers all use it, so an agent's preview matches the person's Feed. The design is [ADR 0017](https://github.com/mihirkavi/open-media/blob/main/docs/adrs/0017-feed-lenses.md); tuning, boosts and versions are [ADR 0021](https://github.com/mihirkavi/open-media/blob/main/docs/adrs/0021-your-own-feed-algorithm.md).
## The built-in lenses
### Relevant
Newer posts first, lifted when you follow the author or a post matches a topic you chose, with authors and networks spread out. Nothing else is used.
- Ranked by newness 50%, who you follow 30%, your topics 20%
- Spreads authors and networks out
```json
{
"format": "open-media.feed-lens/1",
"id": "relevant",
"name": "Relevant",
"version": 2,
"builtIn": true,
"author": "Open Media",
"description": "Newer posts first, lifted when you follow the author or a post matches a topic you chose, with authors and networks spread out. Nothing else is used.",
"permissions": [
"follows",
"interests"
],
"filters": {},
"order": "ranked",
"objectives": {
"recency": 0.5,
"follows": 0.3,
"interests": 0.2,
"engagement": 0,
"diversity": 0.3
},
"interests": []
}
```
### Raw
Every eligible post, newest first. Nothing is ranked or hidden by the lens. Raw is always available.
- Newest first
```json
{
"format": "open-media.feed-lens/1",
"id": "raw",
"name": "Raw",
"version": 1,
"builtIn": true,
"author": "Open Media",
"description": "Every eligible post, newest first. Nothing is ranked or hidden by the lens. Raw is always available.",
"permissions": [],
"filters": {},
"order": "newest",
"objectives": {
"recency": 1,
"follows": 0,
"interests": 0,
"engagement": 0,
"diversity": 0
},
"interests": []
}
```
### Work
Jobs, hiring, careers, launches and professional events, newer first and lifted when you follow the author or a post matches a topic you chose. Nothing else is used.
- About job, jobs, hiring, hire, career, careers, role, resume, interview, internship, recruiting, networking, startup, founder, conference, launch, launched, opentowork, remote, freelance
- Ranked by newness 45%, who you follow 32%, your topics 23%
- Spreads authors and networks out
```json
{
"format": "open-media.feed-lens/1",
"id": "work",
"name": "Work",
"version": 1,
"builtIn": true,
"author": "Open Media",
"description": "Jobs, hiring, careers, launches and professional events, newer first and lifted when you follow the author or a post matches a topic you chose. Nothing else is used.",
"permissions": [
"follows",
"interests"
],
"filters": {
"about": [
"job",
"jobs",
"hiring",
"hire",
"career",
"careers",
"role",
"resume",
"interview",
"internship",
"recruiting",
"networking",
"startup",
"founder",
"conference",
"launch",
"launched",
"opentowork",
"remote",
"freelance"
]
},
"order": "ranked",
"objectives": {
"recency": 0.5,
"follows": 0.35,
"interests": 0.25,
"engagement": 0,
"diversity": 0.3
},
"interests": []
}
```
Relevant's recency counts half as much every 12 hours, so older posts still appear in time order rather than all at the bottom.
## What a lens can and cannot read
- Always: each post's text, time, network and kind (video, image, product, service, event).
- Only when its manifest lists the permission: `follows` (who the person follows on Open Media), `interests` (topics the person or the lens chose), `public_engagement` (like and repost counts a network publishes).
- Never, for any lens: Private messages, Exact location, Sensitive-trait inference, KYC documents, Emotional-state prediction. These cannot be written in a manifest; unknown fields are refused.
## Writing a lens
```json
{
"format": "open-media.feed-lens/1",
"name": "Cooking videos",
"permissions": ["follows"],
"filters": { "kinds": ["video"], "about": ["cooking"], "mute": ["crypto"], "hideSources": ["hive"] },
"order": "ranked",
"objectives": { "recency": 0.6, "follows": 0.4, "interests": 0, "engagement": 0, "diversity": 0.3 },
"interests": []
}
```
Fields: `filters` keep posts (`sources`, `kinds`, `about`, `followedOnly`, `maxAgeHours`) and leave them out (`hideSources`, `hideKinds`, `mute`, `muteAuthors`). `order` is `newest` or `ranked`. `objectives` weigh recency, follows, interests, engagement and discovery (normalized), and `diversity` spreads authors out. The full field list is in `GET https://convo-mail-sync.convo-mail-sync.workers.dev/v1/lenses`.
## Your own algorithm: boosts, tuning and versions
Format `open-media.feed-lens/2` adds two things. A lens that uses neither is still written as `open-media.feed-lens/1`.
- `boosts`: up to 24 leanings toward or away from one network, kind, topic or person, without hiding anything. Each is `{ "source" | "kind" | "topic" | "author": …, "weight": -1 to 1 }`, and a matching post's score is multiplied by 1 + weight/2. All of a post's boosts together stay between ×0.25 and ×2.
- `objectives.discovery`: lifts authors the person does not follow yet. Needs `follows`.
```json
{
"format": "open-media.feed-lens/2",
"id": "my-relevant",
"name": "My Relevant",
"version": 2,
"description": "Your own copy of Relevant, tuned in your own words.",
"permissions": [
"follows",
"interests"
],
"filters": {},
"order": "ranked",
"objectives": {
"recency": 0.5,
"follows": 0.3,
"interests": 0.2,
"engagement": 0,
"diversity": 0.3
},
"interests": [],
"boosts": [
{
"weight": -0.5,
"source": "hive"
},
{
"weight": 0.5,
"kind": "video"
},
{
"weight": 1,
"topic": "design"
}
],
"forkedFrom": "relevant"
}
```
People tune the lens they use in plain words: "less hive", "a lot more videos", "more about design", "a bit less from @bot", "more from people I follow", "more new voices", "mute crypto", "show hive again", "chronological". Tuning Raw, Relevant or Work makes the person's own copy ("My Relevant"); the built-ins never change. The person's account numbers every change, keeps the last 50 versions with whether the person or an agent made them, and can go back. Anyone can audit how a shared lens changed while it was shared. Installed copies never change when the author changes the original.
"Why this?" shows each post's score under the lens's own weights: points per objective, and each boost that matched with its multiplier.
## For agents
Public, no key (`https://convo-mail-sync.convo-mail-sync.workers.dev/open/mcp` or REST):
- `list_feed_lenses` / `GET https://convo-mail-sync.convo-mail-sync.workers.dev/v1/lenses?q=`: the built-in and shared lenses, with rules in words.
- `get_feed_lens` / `GET https://convo-mail-sync.convo-mail-sync.workers.dev/v1/lenses/{id}`.
- `draft_feed_lens` / `POST https://convo-mail-sync.convo-mail-sync.workers.dev/v1/lenses/draft` `{"request": "only videos about cooking, no crypto"}`: plain words to a manifest, with what was and was not understood.
- `preview_feed_lens` / `POST https://convo-mail-sync.convo-mail-sync.workers.dev/v1/lenses/preview` `{"lens": {…}}` or `{"request": "…"}`: the public Feed through that lens, each post with its "why".
- `get_feed` with `lens` / `GET https://convo-mail-sync.convo-mail-sync.workers.dev/v1/feed?lens=relevant`.
- `draft_feed_lens` with `base` / `POST https://convo-mail-sync.convo-mail-sync.workers.dev/v1/lenses/draft` `{"base": "relevant", "request": "less hive, more videos"}`: the change, the rules that changed, nothing saved.
- `get_feed_lens_history` / `GET https://convo-mail-sync.convo-mail-sync.workers.dev/v1/lenses/{id}/history`: how a shared lens changed.
The person's account (`https://convo-mail-sync.convo-mail-sync.workers.dev/me/mcp`, bearer token):
- `list_my_feed_lenses`, `save_feed_lens` (`visibility`: private or public), `install_feed_lens` (copy a shared lens), `delete_feed_lens`, and `get_my_feed` (the Feed through a lens with the person's follows; each post's `why.scoring` shows its score).
- `tune_feed_lens` / `POST https://convo-mail-sync.convo-mail-sync.workers.dev/v1/me/lenses/{key}/tune` `{"request": "less hive"}` (`save: false` previews), `get_my_feed_lens_history` / `GET https://convo-mail-sync.convo-mail-sync.workers.dev/v1/me/lenses/{key}/history`, and `revert_feed_lens` / `POST https://convo-mail-sync.convo-mail-sync.workers.dev/v1/me/lenses/{key}/revert` `{"version": 2}`. Changes made here are recorded as made by an agent.
Show the person a lens's summary and rules before saving it, and ask before sharing it publicly. A saved lens appears in the person's Feed picker on every device; a shared one opens for anyone at `https://openmedia.site/?lens=%3Cid%3E`.
## In the app
There is no lens editor. People write what they want in Search ("only videos from people I follow, no crypto"); Search shows the lens it understood, and choosing it switches the Feed. Words like "less hive" or "more videos" show "Tune 'My Relevant': …" for the lens in use, and "undo" lists earlier versions. The Feed's picker shows Relevant, Raw and the lens in use. "Why this?" on every post lists the signals used, the lens's rules, the post's score under those rules, and what was never used.
---
# Open Media for AI agents
Use this page to decide whether Open Media fits a task and how to call it.
## When to use Open Media
- **Cross-network social search.** "What are people saying about Ethereum on Lens this week?" Use the `search` tool or `GET /v1/search?q=`.
- **One feed across open networks.** Summaries of Farcaster, Lens, Hive, DeSo and Open Media posts, each with its source link and "why" reasons. Use `get_feed`.
- **A person's posts everywhere.** One timeline for an Open Media handle plus the accounts they listed. Use `get_person_timeline`.
- **A feed the person describes.** "Only videos about cooking, no crypto": write a feed lens with `draft_feed_lens`, preview it, and save or share it for the person. See [feed lenses](https://convo-mail-sync.convo-mail-sync.workers.dev/docs/feed-lenses).
- **Filling a profile.** From the person's own LinkedIn PDF or data export (`import_resume`) or their own website (`import_portfolio`, with consent), as proposals they approve. See [profile import](https://convo-mail-sync.convo-mail-sync.workers.dev/docs/profile-import).
- **Upcoming events in the San Francisco Bay Area** from Luma, Meetup and Eventbrite, de-duplicated. Use `find_upcoming_events`.
- **Acting for a signed-in person:** publishing, messages, email, contacts, listings, follows, privacy, payments, tips and paid posts, through their own token.
Do not use Open Media to read Instagram, X, LinkedIn or TikTok feeds; those networks offer no open access and Open Media does not scrape them.
## How to call it
1. **MCP (preferred).** Public: `https://convo-mail-sync.convo-mail-sync.workers.dev/open/mcp` (no key). Account: `https://convo-mail-sync.convo-mail-sync.workers.dev/account/mcp` with OAuth ("Sign in with Open Media"), or `https://convo-mail-sync.convo-mail-sync.workers.dev/me/mcp` with `Authorization: Bearer ` for scripts. Docs: `https://convo-mail-sync.convo-mail-sync.workers.dev/docs/mcp`. Streamable HTTP.
2. **REST.** Index at [https://convo-mail-sync.convo-mail-sync.workers.dev/v1](https://convo-mail-sync.convo-mail-sync.workers.dev/v1); OpenAPI at [https://convo-mail-sync.convo-mail-sync.workers.dev/v1/openapi.json](https://convo-mail-sync.convo-mail-sync.workers.dev/v1/openapi.json).
3. **WebMCP.** On the web, Open Media pages register tools with `document.modelContext.registerTool()`.
4. **Skills.** [open-media](https://convo-mail-sync.convo-mail-sync.workers.dev/.well-known/agent-skills/open-media/SKILL.md) and [open-media-payments](https://convo-mail-sync.convo-mail-sync.workers.dev/.well-known/agent-skills/open-media-payments/SKILL.md), also packaged as a plugin for Claude Code and Codex in the [repository](https://github.com/mihirkavi/open-media/tree/main/agent-plugin).
## Rules for agents
- Agents identify as agents and never pose as people.
- Confirm the exact text with the person before publishing, sending or deleting anything.
- Payments start only after the person confirms the exact amount; money moves only when they finish on Stripe's page or approve the transfer in their own wallet.
- Messages, email and contacts are private to the person and are never public.
- Keep each post's network and link when you quote or summarise it.
---
# Open Media API documentation
Base URL: `https://convo-mail-sync.convo-mail-sync.workers.dev`. All responses are JSON unless stated. The machine-readable description is [OpenAPI 3.1](https://convo-mail-sync.convo-mail-sync.workers.dev/v1/openapi.json); the [API catalog](https://convo-mail-sync.convo-mail-sync.workers.dev/.well-known/api-catalog) follows RFC 9727.
## Quick examples
```bash
curl "https://convo-mail-sync.convo-mail-sync.workers.dev/v1/feed?sources=open-media,farcaster&mode=raw"
curl "https://convo-mail-sync.convo-mail-sync.workers.dev/v1/search?q=videos%20about%20cooking%20today"
curl -H "Authorization: Bearer $OPEN_MEDIA_TOKEN" "https://convo-mail-sync.convo-mail-sync.workers.dev/v1/me"
```
## MCP servers
- `https://convo-mail-sync.convo-mail-sync.workers.dev/open/mcp`: public tools, no key.
- `https://convo-mail-sync.convo-mail-sync.workers.dev/account/mcp`: the person's account over OAuth 2.1 (the host signs them in with their email code once; scope `account`). The same tools as /me/mcp.
- `https://convo-mail-sync.convo-mail-sync.workers.dev/me/mcp`: the person's account, bearer token required. Money-moving tools preview first and need explicit confirmation.
- `https://convo-mail-sync.convo-mail-sync.workers.dev/docs/mcp`: search and read this documentation.
- `https://convo-mail-sync.convo-mail-sync.workers.dev/mcp`: Open Media Events, OAuth 2.1 (PKCE S256, client ID metadata documents).
## Public endpoints (no key)
- `GET /v1/feed`: The mixed feed: Open Media, Farcaster, Lens, Hive and DeSo through a feed lens (raw, relevant, work or a shared one), each post with its “Why this?” reasons.
- `GET /v1/lenses`: Feed lenses: the built-in Raw, Relevant and Work and lenses people shared, each with its rules in plain words and what it may read.
- `GET /v1/lenses/{id}`: One feed lens and its manifest.
- `POST /v1/lenses/draft`: Write a feed lens from plain words, with what was and was not understood.
- `POST /v1/lenses/preview`: The public feed through a lens (an id, a manifest or plain words); nothing is saved.
- `GET /v1/search?q=`: Plain-language search across public posts on every network, plus matching settings.
- `GET /v1/posts`: Open Media public posts, newest first, paginated.
- `GET /v1/posts/{id}`: One public post.
- `GET /v1/profiles/{handle}`: A public profile.
- `GET /v1/profiles/{handle}/posts`: A profile’s public posts.
- `GET /v1/profiles/{handle}/resume`: A person’s public professional profile as a resume page (JSON Resume “even” theme); add .json for JSON Resume or .yaml for RenderCV.
- `GET /v1/jobs?q=`: Open job posts on Open Media with pay, place and the employer’s apply link. Open Media never applies for anyone.
- `GET /v1/profile-preview?url=`: What a public https website says about its owner (name, work, skills, projects, links), with sources. Read-only; obeys robots.txt.
- `GET /v1/events/upcoming`: Upcoming public events from Luma, Meetup and Eventbrite in the San Francisco Bay Area, shown once even when listed on several platforms, with official registration links.
- `GET /v1/people/{network}/{handle}`: One person’s posts in one timeline: an Open Media profile plus the accounts they listed, or one Farcaster, Lens, Hive or DeSo account.
- `GET /v1/networks`: Every network and connector, with exactly which capabilities work today.
- `GET /v1/settings?q=`: The searchable settings index, so an agent can tell a person where any control lives.
- `GET /v1/about`: Mission, principles, promises, roadmap and honest status.
- `GET /v1/listings/{postId}/checks`: What was checked on a listing: claims, outcomes, how many verified people agreed and the pages they cited.
- `GET /v1/transparency`: Monthly counts of listing checks, reports and decisions, with no personal data.
## Account endpoints (bearer token)
- `GET /v1/me`: Your profile.
- `POST /v1/me/posts`: Publish a public post.
- `DELETE /v1/me/posts/{id}`: Delete one of your posts.
- `POST /v1/posts/{id}/report`: Report a post for review.
- `GET /v1/me/conversations`: Your Open Media conversations with recent messages.
- `POST /v1/me/conversations`: Start a conversation with a handle.
- `POST /v1/me/conversations/{id}/messages`: Send a message.
- `GET /v1/me/conversations/{id}/messages`: Messages in one conversation, newest last (limit, before).
- `POST /v1/me/media/videos`: Upload a video (raw MP4, MOV or WebM, at most 100 MB) to attach to a post.
- `POST /v1/me/realtime-token`: Your own short-lived session for live message updates through Supabase Realtime.
- `GET /v1/connected/me`: Every /v1/me route again, for apps that signed you in with “Sign in with Open Media” (OAuth); see ADR 0041.
- `GET /v1/me/export`: Export a readable copy of your data.
- `POST /v1/me/blocks`: Block or unblock someone by handle.
- `POST /v1/me/conversations/{id}/report`: Report unwanted contact in a conversation.
- `DELETE /v1/me`: Delete your account; needs the confirmation “delete my account”.
- `GET /v1/me/contacts`: Your contacts, private to you and encrypted on the server, with which accounts each is linked to and why.
- `PUT /v1/me/contacts`: Create or replace contact cards by id.
- `DELETE /v1/me/contacts/{id}`: Delete a contact card.
- `PUT /v1/me/linked-accounts`: Set the open-network accounts shown on your public profile.
- `POST /v1/me/listings`: Offer a product, service, event or job as a public post. It goes live at once and is checked in the background.
- `GET /v1/me/profile-fields`: Your profile fields (contact details, accounts on other networks), each with who may see it.
- `PUT /v1/me/profile-fields`: Replace your profile fields and who may see each one: everyone, connections or only me.
- `GET /v1/me/professional`: Your professional profile, and the same data as a JSON Resume document.
- `PUT /v1/me/professional`: Replace your professional profile: headline, experience, education, skills, links, open to work or hiring. It is public.
- `POST /v1/me/professional/import`: Fill your profile from LinkedIn’s profile PDF, its data-export files or a JSON Resume: proposals with sources, saved only the ones you choose.
- `POST /v1/me/professional/portfolio`: Fill your profile from your own website (consent: true): proposals from JSON Resume, JSON-LD, h-card and Open Graph, saved only the ones you choose.
- `POST /v1/me/career/tailor`: Draft your profile and a cover note for one job from your own profile only, with anything unsupported removed and listed.
- `POST /v1/me/career/application`: Draft the message to apply for a job with. Nothing is sent.
- `GET /v1/verification-tasks/next`: For human-verified people: a listing claim to check; answer with POST /v1/verification-tasks/{taskId} and cited quotes.
- `GET /v1/operator/review-queue`: For Open Media operators: held listings, hidden posts and appeals.
- `PATCH /v1/me/listings/{postId}`: Change a listing’s availability, price or place.
- `PUT /v1/me/listings/{postId}/rating`: Rate a listing 1–5 stars (verified people who show their legal name only); DELETE withdraws it.
- `GET /v1/me/identity`: Your identity tier, blue tick, the name others see, public or private, and verification status.
- `PUT /v1/me/identity`: Choose the name others see and whether your account is private.
- `POST /v1/me/verification`: Start identity verification with Stripe Identity (a link you open yourself).
- `GET /v1/me/payments/setup`: Your card payouts, linked wallets, tips setting, fees, and whether this server runs in test mode.
- `POST /v1/me/payments/payouts`: Set up getting paid by card with Stripe (a link you open yourself).
- `PUT /v1/me/payments/tips`: Turn tips on your posts on or off.
- `GET /v1/me/payments`: Payments you sent and received.
- `POST /v1/me/payments`: Start paying for a listing, a tip or a paid post: a Stripe page or a transfer for your own wallet. Nothing is paid until Stripe or the network confirms it.
- `GET /v1/me/payments/{id}`: One of your payments.
- `POST /v1/me/payments/{id}/transaction`: Report the USDC transaction that paid; Open Media checks it on the network.
- `POST /v1/me/wallets`: Link a wallet with a signature from it.
- `DELETE /v1/me/wallets/{id}`: Unlink a wallet.
- `GET /v1/me/listings/{postId}/payment-options`: How a listing can be paid for.
- `GET /v1/me/posts/{id}/payment-options`: How a post can be tipped or unlocked.
- `POST /v1/me/paid-posts`: Publish a post with a free preview and a paid part.
- `GET /v1/me/posts/{id}/paid`: The paid part of a post you wrote or paid for.
- `GET /v1/me/follows`: Who you follow, your followers, and follow requests waiting for you.
- `GET /v1/me/lenses`: Your feed lenses.
- `POST /v1/me/lenses`: Save a feed lens, or share it publicly.
- `POST /v1/me/lenses/install`: Install a shared feed lens (a copy that is yours).
- `DELETE /v1/me/lenses/{key}`: Remove one of your feed lenses.
- `GET /v1/me/feed`: Your feed through a lens, using who you follow when the lens asks for it.
- `POST /v1/me/follows`: Follow someone; private accounts get a request.
- `DELETE /v1/me/follows/{handle}`: Unfollow, or withdraw a request.
- `POST /v1/me/follow-requests/{id}`: Accept or decline a follow request.
- `DELETE /v1/me/followers/{id}`: Remove a follower.
- `GET /v1/me/email`: Your stored email from every connected mailbox, newest first.
- `GET /v1/mail-accounts`: Your connected mailboxes.
- `POST /v1/mail-accounts`: Connect an IMAP or POP3 mailbox, with SMTP for sending.
- `POST /v1/mail-accounts/{id}/sync`: Fetch new mail for a mailbox.
- `POST /v1/mail-accounts/{id}/send`: Send an email.
- `DELETE /v1/mail-accounts/{id}`: Remove a mailbox and its stored mail.
- `GET /v1/bridges`: Chat networks this server bridges and which you have connected.
- `GET /v1/bridges/conversations`: Your bridged chats (WhatsApp, Signal and others).
- `POST /v1/bridges/rooms/{id}/messages`: Reply in a bridged chat.
- `GET /v1/bridges/{network}/flows`: How a chat network can be connected.
- `POST /v1/bridges/{network}/login/start`: Start connecting a chat network (then login/step, login/cancel, logout).
- `GET /v1/cross-posting/status`: Which networks this server helps cross-post to. Cross-posting itself is signed on your device.
- `POST /v1/search/assist`: A short AI summary, with citations, of public posts you pass in. No account needed; signed in, your own AI key from Settings → Open Media AI writes it.
- `POST /v1/translate`: Translate up to 20 texts into English (or another language), detecting each one’s language. Public text is cached by its hash; with private: true and your token, messages and email are translated without being stored.
## Plain-language questions (NLWeb)
`POST https://convo-mail-sync.convo-mail-sync.workers.dev/ask` follows NLWeb v0.55: send `{"query": {"text": "…"}}` and get schema.org items (`TechArticle` from these docs, `SocialMediaPosting` from every open network) under `results`, with `_meta.response_type` `answer` or `failure` (`INVALID_QUERY`, `NO_RESULTS`). Add `"prefer": {"streaming": true}` and `Accept: text/event-stream` for `start`, `result` and `complete` events. The [schema map](https://convo-mail-sync.convo-mail-sync.workers.dev/schemamap.xml) lists each page's type, and [`/feeds/posts.jsonl`](https://convo-mail-sync.convo-mail-sync.workers.dev/feeds/posts.jsonl) carries the newest public Open Media posts as JSON Lines.
## Agent registration
Agents may register at `POST https://convo-mail-sync.convo-mail-sync.workers.dev/agent/identity` (`{"type": "anonymous"}`) and exchange the returned assertion at `POST https://convo-mail-sync.convo-mail-sync.workers.dev/oauth/token` with `grant_type=urn:ietf:params:oauth:grant-type:jwt-bearer`. The hour-long token has the `public:read` scope and its own rate-limit bucket; it never opens anyone's account. See [authentication](https://convo-mail-sync.convo-mail-sync.workers.dev/auth.md).
## Errors
Errors are JSON: `{"error": {"code": "bad_request", "message": "…"}}`. Codes include `bad_request` (400), `unauthorized` (401, with a `WWW-Authenticate` header naming the protected-resource metadata), `refused` (403 or 409), `not_found` (404), `rate_limited` (429, with `Retry-After`), `not_configured` (503) and `upstream_unavailable` (502).
## Rate limits
Public and agent routes allow about 120 requests per minute per client IP, or per registered agent when it sends its agent token. Responses carry `RateLimit-Policy`; a 429 carries `Retry-After` in seconds.
## Idempotency
Send an `Idempotency-Key` header (a UUID) on `POST /v1/me/posts`, `POST /v1/me/listings`, `POST /v1/me/paid-posts` and `POST /v1/me/payments`. Retrying with the same key returns the same post or payment instead of creating a second one.
## Pagination
Lists use opaque cursors: pass `nextCursor` (or follow `next`) from one page to get the next.
## Versioning and deprecation
The API is versioned in the path (`/v1`). Fields may be added without notice; nothing in `/v1` is removed or changed incompatibly without at least 90 days' notice in this document, a `Deprecation` header on the affected responses and a `Sunset` header with the removal date.
## Sandbox
Payments run in test mode (Stripe test cards and USDC on Base Sepolia) until the operator turns on live payments; `GET /v1/me/payments/setup` says which mode is active. For a full private sandbox, run the open-source stack locally with `npm run local` from the [repository](https://github.com/mihirkavi/open-media).
---
# Open Media developer portal
Build on Open Media without an account for public data, or act for a person with their own token.
## Quickstart
1. Read the public feed: `curl "https://convo-mail-sync.convo-mail-sync.workers.dev/v1/feed"`. No key, no signup.
2. Connect an MCP client to `https://convo-mail-sync.convo-mail-sync.workers.dev/open/mcp` (Streamable HTTP).
3. To act for a person, sign them in: `POST https://convo-mail-sync.convo-mail-sync.workers.dev/v1/auth/email-code` with their email, ask them for the code Open Media emails them, then `POST https://convo-mail-sync.convo-mail-sync.workers.dev/v1/auth/verify` returns their access token ([details](https://convo-mail-sync.convo-mail-sync.workers.dev/auth.md)). Send it as `Authorization: Bearer `.
4. Install the Open Media plugin for Claude Code or Codex from the [repository](https://github.com/mihirkavi/open-media/tree/main/agent-plugin).
5. For your agent's own rate limit, register it: `POST https://convo-mail-sync.convo-mail-sync.workers.dev/agent/identity` with `{"type": "anonymous"}`, then trade the assertion at `/oauth/token` ([how](https://convo-mail-sync.convo-mail-sync.workers.dev/auth.md)).
## SDKs and command line
The repository includes a TypeScript SDK (`packages/sdk`, `open-media-sdk`), a command line (`packages/cli`, `open-media`) and a Python client (`packages/python`, `open-media`). They are not on npm or PyPI yet; build them from the [repository](https://github.com/mihirkavi/open-media/tree/main/packages). Each retries 429s after `Retry-After` and sends an `Idempotency-Key` on every write.
```ts
import { OpenMedia } from 'open-media-sdk';
const feed = await new OpenMedia().feed({ sources: ['farcaster', 'lens'] });
```
The command line covers the whole platform: every tool on the MCP servers is a command, with flags generated from its input schema and read live from `tools/list`, so new tools appear without an update.
```bash
open-media login # in the browser
open-media tools --search post
open-media get-feed --sources lens
open-media publish-post "Hi" --yes
open-media api GET /v1/me/follows
source <(open-media completion zsh)
```
`open-media login` registers the CLI as the public OAuth client “Open Media CLI” and listens on a random `127.0.0.1` port for the redirect, so it shows in Sign-in and security → Connected apps and `open-media logout` revokes it. On a machine without a browser, `open-media login you@example.com` signs in with an emailed code. Every tool that changes something asks first (or takes `--yes`); `--json` prints JSON; exit codes are 0 done, 1 the API refused, 2 the command was wrong.
## Access tokens
There are no API keys to request and no sales process. Public data is free and keyless; account access uses the person's own token, so an integration can never do more than that person can. Tokens expire after about an hour.
## Commerce on ONDC (India)
Open Media is building an ONDC seller app (Beckn, retail 1.2.0), described at [https://convo-mail-sync.convo-mail-sync.workers.dev/ondc](https://convo-mail-sync.convo-mail-sync.workers.dev/ondc). Sellers in India set up their store with `GET`/`PUT https://convo-mail-sync.convo-mail-sync.workers.dev/v1/me/ondc` or the `get_ondc_store` and `set_ondc_store` tools on `/me/mcp`. Their public INR products are then offered to ONDC buyer apps through signed `search` and `select` callbacks. Open Media is not yet registered on the ONDC network, and orders through ONDC come in a later phase.
## Sandbox and test mode
- Payments are in test mode (Stripe test cards, USDC on Base Sepolia) until live payments are approved; no real money moves.
- Run the whole stack locally with `npm run local` (database, auth, API and web app) for a private sandbox with test accounts.
## Resources
- [API documentation](https://convo-mail-sync.convo-mail-sync.workers.dev/docs) and [OpenAPI 3.1](https://convo-mail-sync.convo-mail-sync.workers.dev/v1/openapi.json)
- [Agent guide](https://convo-mail-sync.convo-mail-sync.workers.dev/agents) and [authentication](https://convo-mail-sync.convo-mail-sync.workers.dev/auth.md)
- [Skills index](https://convo-mail-sync.convo-mail-sync.workers.dev/.well-known/agent-skills/index.json) and [MCP server card](https://convo-mail-sync.convo-mail-sync.workers.dev/.well-known/mcp/server-card.json)
- [Source code (MIT)](https://github.com/mihirkavi/open-media)
---
# Open Media sandbox and test mode
Use these to build and test an integration without touching live money or other people's data.
## Test mode for payments
Every payment on this server runs in test mode until live payments are approved: cards use Stripe's test mode and USDC uses the Base Sepolia test network, so no real money moves. `GET https://convo-mail-sync.convo-mail-sync.workers.dev/v1/me/payments/setup` returns `available.live: false` while test mode is on. Use Stripe's published test cards and test USDC from a Base Sepolia faucet.
## Read-only exploration
All public endpoints are read-only and need no key, so an agent can explore safely: `GET https://convo-mail-sync.convo-mail-sync.workers.dev/v1/feed`, `GET https://convo-mail-sync.convo-mail-sync.workers.dev/v1/search?q=`, `GET https://convo-mail-sync.convo-mail-sync.workers.dev/v1/events/upcoming`, and the tools on `https://convo-mail-sync.convo-mail-sync.workers.dev/open/mcp`.
## Confirmation before writes
Account tools that publish, send or pay first return a preview. Payments start only when called again with `confirm: true` and the exact amount, and money moves only when the person finishes on Stripe's page or in their own wallet.
## A private sandbox on your machine
The whole stack is open source. Clone https://github.com/mihirkavi/open-media and run `npm run local`: it starts the database, auth, this API and the web app on your computer with test accounts and a local inbox, so you can create accounts, post, message and pay with test data that never leaves your machine.
See the [developer portal](https://convo-mail-sync.convo-mail-sync.workers.dev/developers) and [API documentation](https://convo-mail-sync.convo-mail-sync.workers.dev/docs).
---
# About Open Media
Build the open communication layer for humanity, where people can communicate across networks, control how information reaches them, and keep ownership of their identity, relationships and content, whichever app they use.
Apps are doorways. The person is the constant. No app should permanently own your identity, audience, social graph, content, recommendations, message history or governance rights. Open Media is one doorway. Anyone should eventually be able to build another on the same open protocol, and you should be able to walk through whichever one you like.
Open Media is an open-source project (MIT licence) developed in the open at [https://github.com/mihirkavi/open-media](https://github.com/mihirkavi/open-media). It ships one app for iPhone, Android and the web, a public API, MCP servers for AI agents, and the database rules that protect people's data.
## What it is today
- **Everything together:** One place for your social world. Posts from several networks in one feed, and every conversation, chat or email, in one inbox organised by person rather than by app. One post goes to every network you choose.
- **Your feed belongs to you:** No secret algorithm. Choose Raw, simply newest first, or Relevant, a small set of signals you can see, or describe your own feed in plain words and share it. Every feed is an open lens anyone can read, and every post explains itself with “Why this?”, including the private data it did not use.
- **You are not locked in:** Your identity, audience and content move with you. Export everything or delete your account at any time. Public posts are open to everyone through a free API. The goal is identity and content that work in any app.
## Honest status
- Open Media is an early public beta, built in the open.
- It cannot read or post to Instagram, X, LinkedIn or TikTok feeds; those companies offer no open access and Open Media does not scrape them.
- Chat bridges are opt-in, run on a local setup today, and are not approved by the networks they connect to.
- Messages between Open Media users are protected by strict database rules but are not yet end-to-end encrypted.
## How it is built
The app is built with Expo and React Native. Data lives in Supabase (Postgres with row-level security), and this API runs on Cloudflare Workers. Every decision is recorded as an architecture decision record in the repository, and every change is tested before it ships.
See also: [contact](https://convo-mail-sync.convo-mail-sync.workers.dev/contact), [privacy](https://convo-mail-sync.convo-mail-sync.workers.dev/privacy) and [pricing](https://convo-mail-sync.convo-mail-sync.workers.dev/pricing).
---
# Contact Open Media
Open Media is developed in public, so the best way to reach the project is through its repository.
## Questions, ideas and bugs
Open an issue at [https://github.com/mihirkavi/open-media/issues](https://github.com/mihirkavi/open-media/issues). Describe what you expected, what happened, and the device or client you used. Issues are public, so never include passwords, tokens, messages or other private data.
## Security reports
Report vulnerabilities privately through GitHub: open the repository's Security tab and choose "Report a vulnerability". Please include steps to reproduce and give the project reasonable time to fix the problem before disclosing it. The scope is described in [SECURITY.md](https://github.com/mihirkavi/open-media/blob/main/SECURITY.md).
## Reporting content or people
Inside the app, use "Report" on a post or a conversation, or block the person. Reports are reviewed, and posts reported by several people are hidden automatically.
## For agents and integrations
Agents should start with [the agent guide](https://convo-mail-sync.convo-mail-sync.workers.dev/agents) and [the API documentation](https://convo-mail-sync.convo-mail-sync.workers.dev/docs). Problems with the API or MCP servers can be reported as GitHub issues with the request and response (never a token).
---
# Open Media privacy
This page describes how Open Media handles data, based on how the app and this API are built. The source code is public, so every statement here can be checked in the [repository](https://github.com/mihirkavi/open-media).
## Public by design
- Posts and profiles on Open Media are public unless a person makes their account private, in which case only followers they approve see their posts, including through this API and through agents.
- Public posts can be read by anyone, with or without an account, through the app and this API.
## Private by design
- Messages between Open Media users, connected email, bridged chats and contacts are never public. Contacts are encrypted on the server and readable only by their owner.
- Identity verification uses Stripe Identity; Stripe keeps the document and selfie, and Open Media keeps only the result.
- Payments go through Stripe or the person's own wallet. Open Media never stores card numbers, bank details, seed phrases or private keys.
- The feed is never ranked on private messages, ID documents, precise location or inferred sensitive traits, and every ranked post explains itself with "Why this?".
## Your controls
- Export all your data or delete your account from your profile at any time.
- Make your account private, choose which name others see, block and report people.
## This API
Public API requests are rate limited per IP address. Account requests act only as the person whose token is sent, and the database refuses everything else. No advertising or tracking cookies are set by this API.
Questions: see [contact](https://convo-mail-sync.convo-mail-sync.workers.dev/contact).
---
# Open Media terms of use
Open Media is an open-source project in public beta. These terms describe how it may be used, through the app, this API, the MCP servers and the agent plugins. The source code is public under the MIT License in the [repository](https://github.com/mihirkavi/open-media).
## Your content and your account
- What you post, send and save stays yours. You can export it (Profile → Export my data, or `https://convo-mail-sync.convo-mail-sync.workers.dev/v1/me/export`) and delete your account at any time.
- Posts and profiles are public unless your account is private. Messages, email, chats and contacts are private to you; see [privacy](https://convo-mail-sync.convo-mail-sync.workers.dev/privacy).
## What is not allowed
- Spam, harassment, impersonation, or anything illegal.
- Listings that break the [listing rules](https://convo-mail-sync.convo-mail-sync.workers.dev/policies/listings).
- Scraping, overloading or probing the service beyond the published API and its rate limits, or trying to reach data that isn't yours.
Content or accounts that break these rules may be hidden or suspended; you'll be told why and can reply to appeal.
## Agents and apps acting for you
- When you connect an AI app (for example with "Sign in with Open Media"), it acts as you, within what your account can do and the same rules as the app.
- Agents are instructed to ask before they publish, send, delete, pay or change settings. You stay responsible for what you approve, and you can disconnect an app at any time by signing out.
## No warranty
Open Media is provided as is, without warranty of any kind, as described in the MIT License. Features in beta may change or stop. Payments are between buyers and sellers through Stripe or their own wallets; Open Media never holds money.
## Changes and contact
These terms may change as the project grows; the date above shows the latest version. Questions: see [contact](https://convo-mail-sync.convo-mail-sync.workers.dev/contact).
---
# Listing rules
Products, services, apps and events on Open Media go live as soon as you post them. Each listing is then checked automatically, in the open, by the rules below ([ADR 0016](https://github.com/mihirkavi/open-media/blob/main/docs/adrs/0016-marketplace-trust-and-community-verification.md)).
## What happens after you post
- **Clear:** everyone sees it.
- **Closer look:** everyone still sees it. Verified people's agents check what it claims, or a person at Open Media looks.
- **Held:** only you see it. Open Media sends you a message in Messages with the reason and how to fix it. Post it again with the fix and the new listing replaces the held one. Reply to the message if you think it's a mistake, and a person will look.
Nothing is deleted by these checks. A held listing stays yours.
## Not allowed (held)
- Weapons and ammunition
- Illegal or recreational drugs
- Fake documents, stolen data, and breaking into other people’s accounts
- Counterfeits and replicas
- Get-rich offers and unlicensed financial products
- Adult services
- Links that download files directly, links to bare IP addresses, and links that use a brand's name on a site the brand doesn't own
- Links that Google Web Risk lists as malware, phishing or unwanted software
## A closer look (still live)
- Prescription medicines and supplements with health claims
- Alcohol, tobacco and vapes
- Live animals
- Gambling
- Listings aimed at children
- Short links (bit.ly and similar) and links without https
- Listings that call themselves "official" for a brand
- Paid listings from accounts less than a week old, and paid listings posted by agents that don't sign their requests
- Anything an automatic content check (Llama Guard) flags. The model can only ask for a closer look; it can never hold or remove a listing.
## Apps and software
List apps and software as a link to their official page: the App Store, Google Play, GitHub, your own website and similar. Open Media never hosts the files.
## Reports
Reports are signals, not votes. Each person counts once. Reports from verified people, and from people whose past reports were upheld, count for more. Brand-new accounts and groups of accounts that appear together count for less. Scams and child safety count for more than "something else".
## Checked by people
Verified people can let their own agents check listings' claims, such as "is this event on the organizer's official page?". Verifiers are assigned at random, never check their own or their friends' listings, can't see each other's answers, and cite pages anyone can open. When at least three agree and their evidence checks out, the listing shows "Checked by N people", and "Why this?" lists what was checked.
## Large sellers
Under the US INFORM Consumers Act, sellers with 200 or more sales and $5,000 or more in a year confirm their details, which come from their Stripe payout account. Sellers with $20,000 or more a year have their name and contact shown on their listings. Sales pause if details aren't confirmed within 10 days.
## Contact
Rights holders and anyone reporting illegal content can use the report menu on any listing, or email legal@openmedia.site.
---
# Open Media pricing
## Free
- **The app** on iPhone, Android and the web: free, no subscription, no ads by default.
- **The public API and MCP servers:** free, no API key, no signup. About 120 requests per minute per client.
- **The account API and account MCP server:** free, using the person's own access token.
## Payments between people
People can sell products and services, tip creators and sell paid posts. Open Media's fee is 0% today, shown before every payment. Card payments carry Stripe's processing fee (about 2.9% + 30¢ in the US), paid by the seller; USDC payments carry only the network fee shown by the payer's wallet. Payments run in test mode until live payments are approved.
## Limits
- Posts up to 2,000 characters; paid parts up to 10,000 characters; videos up to 3 minutes.
- Tips from 1 to 500 US dollars.
See the [developer portal](https://convo-mail-sync.convo-mail-sync.workers.dev/developers) to get started.
---
# Agent authentication on Open Media
How an agent gets access to Open Media, and exactly which credentials exist. This file lives at `/auth.md`, the discovery path from the WorkOS auth.md spec. Open Media implements its anonymous registration; this file says plainly what it does not implement.
## Discover
- Public data needs no credential at all: `https://convo-mail-sync.convo-mail-sync.workers.dev/open/mcp`, `GET /v1/feed`, `GET /v1/search`, `GET /v1/posts`, `GET /v1/profiles/{handle}`, `GET /v1/events/upcoming` and every discovery file.
- Protected-resource metadata (RFC 9728): [https://convo-mail-sync.convo-mail-sync.workers.dev/.well-known/oauth-protected-resource](https://convo-mail-sync.convo-mail-sync.workers.dev/.well-known/oauth-protected-resource).
- Authorization-server metadata (RFC 8414), including the `agent_auth` block with `identity_endpoint` and `identity_types_supported`: [https://convo-mail-sync.convo-mail-sync.workers.dev/.well-known/oauth-authorization-server](https://convo-mail-sync.convo-mail-sync.workers.dev/.well-known/oauth-authorization-server).
- A protected route called without a valid credential returns 401 with `WWW-Authenticate: Bearer resource_metadata="https://convo-mail-sync.convo-mail-sync.workers.dev/.well-known/oauth-protected-resource"`.
## Pick a method
- **No credential:** everything public. Start here.
- **Anonymous agent registration** (`agent_auth`, type `anonymous`): an agent gets its own identity and an access token with the `public:read` scope, so its requests are counted in its own rate-limit bucket instead of sharing one with its IP address. It never grants access to anyone's account.
- **Sign in with Open Media (OAuth 2.1, for MCP hosts):** connect `https://convo-mail-sync.convo-mail-sync.workers.dev/account/mcp`. The host discovers `https://convo-mail-sync.convo-mail-sync.workers.dev/.well-known/oauth-protected-resource`, registers itself (client ID metadata document, or dynamic registration) and sends the person to `https://convo-mail-sync.convo-mail-sync.workers.dev/authorize`, where they enter their email, the code Open Media emails them, and approve. The host never sees their session; refreshing its token renews it.
- **Sign the person in with an email code (bearer):** for the account API (`/v1/me/...`) and the account MCP server (`/me/mcp`). Open Media emails the person a code from security@openmedia.site; they tell you the code; you get their access token. See "Sign a person in" below. People can also copy a token from the app (Settings, then Developers and agents). Either way it acts only as them.
- **OAuth 2.1 with PKCE (S256):** Open Media Events at `https://convo-mail-sync.convo-mail-sync.workers.dev/mcp`, scopes `events:read` and `events:write`, with client ID metadata documents or Dynamic Client Registration at `https://convo-mail-sync.convo-mail-sync.workers.dev/oauth/register`.
## Sign a person in
Works for existing accounts and creates new ones. Nothing happens without the code from the person's inbox.
```
POST https://convo-mail-sync.convo-mail-sync.workers.dev/v1/auth/email-code
Content-Type: application/json
{"email": "person@example.com"}
```
Tell the person a code is on its way, ask them for it, then:
```
POST https://convo-mail-sync.convo-mail-sync.workers.dev/v1/auth/verify
Content-Type: application/json
{"email": "person@example.com", "code": "12345678"}
```
The response holds `access_token` (send it as `Authorization: Bearer …`; it lasts `expires_in` seconds, an hour), `refresh_token` and `user`. Renew with `POST https://convo-mail-sync.convo-mail-sync.workers.dev/v1/auth/refresh` and `{"refresh_token": "…"}`; end the session with `POST https://convo-mail-sync.convo-mail-sync.workers.dev/v1/auth/sign-out`. A new account has no profile yet (`GET /v1/me` answers `no_profile`): ask the person for a name and handle and send them to `PUT https://convo-mail-sync.convo-mail-sync.workers.dev/v1/me/profile` as `{"displayName": "…", "handle": "…"}`. The same steps are MCP tools on `https://convo-mail-sync.convo-mail-sync.workers.dev/open/mcp` (`request_sign_in_code`, `sign_in_with_code`, `refresh_sign_in`) and `set_up_profile` on `/me/mcp`; the CLI does it with `open-media login you@example.com` (plain `open-media login` signs in through the browser instead). Keep both tokens private, as you would a password. Errors: `invalid_code` (400, ask for a new code), `rate_limited` (429 with `Retry-After`).
## Register an agent identity
```
POST https://convo-mail-sync.convo-mail-sync.workers.dev/agent/identity
Content-Type: application/json
{"type": "anonymous", "name": "my-agent"}
```
The response holds `registration_id`, `identity_assertion` (valid for 30 days), `assertion_expires`, `pre_claim_scopes` (`public:read`) and `post_claim_scopes` (empty). Only the `anonymous` type is supported: `service_auth` and `identity_assertion` (ID-JAG) registration return `unsupported_identity_type`.
## Claim
There is no claim ceremony and no `claim_endpoint`: an anonymous agent identity is never linked to a person. To act for a person, sign them in with an email code (above).
## Exchange
```
POST https://convo-mail-sync.convo-mail-sync.workers.dev/oauth/token
Content-Type: application/x-www-form-urlencoded
grant_type=urn:ietf:params:oauth:grant-type:jwt-bearer&assertion=
```
The response is `{"access_token": "…", "token_type": "Bearer", "expires_in": 3600, "scope": "public:read"}`. Exchange the same assertion again when the access token expires. OAuth clients for Open Media Events exchange authorization codes and refresh tokens at the same endpoint.
## Use the access_token
```
Authorization: Bearer
```
Agent tokens work on every public route and the public MCP server. Account routes need the person's own token and answer 401 to an agent token.
## Errors
- `400 invalid_grant`: the identity assertion is invalid or expired. Register again.
- `400 unsupported_identity_type`: only `{"type": "anonymous"}` is accepted.
- `401 unauthorized` with `WWW-Authenticate`: missing, expired or invalid token on a protected route.
- `429 rate_limited` with `Retry-After`: back off for the stated seconds.
## Revocation
Agent identity assertions expire after 30 days and access tokens after an hour; there is no `events_endpoint` for revocation events. Account tokens end when they expire or the person signs out. OAuth tokens for Open Media Events are revoked at `https://convo-mail-sync.convo-mail-sync.workers.dev/oauth/token`, the advertised revocation endpoint.