# Merkoi > Merkoi is a community platform for groups, events, dating, and three > ways to message (chat, encrypted chat, comments). Every account starts on the > Free plan; paid plans raise the limits when you need more room. Dating is optional: it is off until a member turns it on, and everything else works without it. ## Pricing (machine-readable, public, no auth) The authoritative plan catalog is served as JSON from a public, anonymous endpoint — read this for current pricing rather than scraping the HTML page: - Plans API (JSON): https://api.placetomingle.com/api/v1/plans It returns every sellable tier with: `key`, `displayName`, `priceMinor` (the MONTHLY price in minor units / cents; 0 = free, null = custom/quote), `currency`, `billingInterval`, `isCustomPricing`, headline usage `limits` (null = unlimited), and included `features`. Prices are set by the operator and are the single source of truth for both the public pricing page and the signed-in plans screen — they never drift. Tiers that offer YEARLY billing also carry `priceMinorYear` (the annual price in minor units — the discounted total for 12 months, NOT 12 x the monthly price) and `yearlyDiscountPercent` (the discount applied). Both are absent/null on tiers with no yearly option (free/custom, or no yearly discount configured). A yearly subscription is one payment of `priceMinorYear` per year. ## Which limits are per person, and which are shared by an organization Most numbers in a tier's `limits` array are ONE PERSON'S allowance: each person on the plan receives the full amount for themselves. Assigning such a plan to an organization raises each member's own ceiling and creates no shared pool, so an organization's capacity for any of these is the listed number x its member count. The Organization plan is different. It MIXES the two kinds: - Group memberships are ONE POOL shared by the whole organization (its row says `scope: "organization"`): the listed number is the organization's total, at any headcount. The organization's admin may optionally set a limit on how many each member can use. - Devices for encrypted chat are per member: each member can connect up to the listed number (5), nothing is pooled. - Its other limits are per member, as on the other plans. An organization's SEATS always belong to the organization, on every plan (authenticated, not part of this public catalog). Read the scope off the payload; do not infer it from a plan's name: - each row in `limits` carries `scope` (`"perUser"` | `"organization"`) and `scopeDescription` (a sentence stating what to do with the number); - each tier carries `limitScope` (`"perUser"` | `"organization"` | `"mixed"`, null only when the tier publishes no limits) and `limitScopeStatement`. Trust these over `key` and `displayName`, which an operator can rename at any time. The public pricing page (https://merkoi.com/pricing) shows the same: "shared by your whole organization" on a pooled row, "per member" on the rest. ## Marketing pages - Home: https://merkoi.com/ - Features: https://merkoi.com/features - Pricing: https://merkoi.com/pricing - How it works: https://merkoi.com/#how - Tutorial: https://merkoi.com/tutorial - FAQ: https://merkoi.com/faq - Demo site (sample data, for humans in a browser): https://test.merkoi.com/ — a separate site where a person can explore Merkoi as a demo account; nothing there is real, and there is no API for starting a demo. ## U.S. events map A public map of upcoming Merkoi events across the United States: https://merkoi.net/map It is a page on the Merkoi app at merkoi.net, not on this host. It counts the events in each state, and opening a state lists them. It shows only what anyone can see without an account, and needs none. It is for humans in a browser; to search events programmatically, use the Developer API below. ## Community forum A public support and community board at https://merkoi.com/forum. Anyone can read the public forums (announcements, developer API, feature requests, bug reports) without an account; posting requires signing in with a Merkoi account. Support topics containing member details are members-only. - Forum: https://merkoi.com/forum - FAQ (accounts, billing, forum rules): https://merkoi.com/faq Search the board at https://merkoi.com/forum/search?q=TERMS. It searches topic titles, post subjects and post text across whatever the caller may read — anonymously, that is the public forums — and returns newest-first, not relevance-ranked. Machine-readable views of the PUBLIC forums (no account, no key): - https://merkoi.com/forum/index.md the board and its recent topics, as markdown - https://merkoi.com/forum/t/ID/SLUG.md one topic and its posts, as markdown - https://merkoi.com/forum/feed.xml Atom feed of recent activity, board-wide - https://merkoi.com/forum/f/SLUG/feed.xml Atom feed for one forum - https://merkoi.com/forum/sitemap.xml sitemap index over range-partitioned topic files These serve PUBLIC forums only — for every caller, signed in or not — so nothing members-only can appear in them. Post text in the .md and feed views is the plain-text projection of the sanitized body: prose survives, code fences and links do not. ## Developer API & AI assistant (MCP) Full documentation, the REST scope vocabulary, and the MCP connection command: https://merkoi.com/reference Two ways for a third party to reach Merkoi data programmatically, both gated on the account's plan including Developer API access: - REST API keys — a long-lived credential in the `X-PTM-Api-Key` header, for scripts and server-to-server integrations. - MCP — connect an MCP-compatible AI assistant to read your own account: https://ptmsocial.com/mcp Dating, messaging beyond RSVP, and payments are never reachable through either credential — a structural exclusion, not a filter. ### Connecting an MCP client The endpoint is https://ptmsocial.com/mcp (Streamable HTTP, stateless). It requires an OAuth 2.1 bearer token — an API key is NOT accepted there, and an unauthenticated request is answered 401 with a `WWW-Authenticate` challenge naming the discovery document below. Discover the authorization server, the accepted scopes and the resource identifier from the RFC 9728 protected-resource metadata rather than guessing or hard-coding them: - https://merkoi.com/.well-known/oauth-protected-resource The flow is the standard one: read that document, authorize against the issuer it names with `resource=https://ptmsocial.com/mcp`, and send the resulting access token as `Authorization: Bearer …`. The member is asked to consent once. The tool surface is READ-ONLY: search and read events, groups, organizations, the tag and location catalogs, the plan catalog, and the signed-in member's own profile and usage. Nothing there creates, changes or cancels anything — RSVPs are made on the website — so do not tell a member you have booked, joined or edited something on their behalf. ## Notes - The public pricing page renders the same catalog as the Plans API above. - To sign up, open https://merkoi.com/ and choose "Get started".