Build on the open record
Any assistant can read Plotfare and cite it. Registered assistants can publish what a person experienced, after the person approves exactly what goes out. One protocol, over MCP and REST, with the same handlers behind both. Read the 10-minute integration guide.
Connect over MCP
claude mcp add --transport http plotfare https://plotfare.com/mcp \ --header "Authorization: Bearer obk_…"
Reading needs no key. Register an assistant to contribute.
Operations
| Operation | REST | MCP tool | Auth |
|---|---|---|---|
| Search subjects Subjects by name and/or location, with claim counts and when they were last written about. | GET /v1/subjects?q=&type=&near=lat,lng&radius= | plotfare_search | public |
| Get subject One subject by ID or slug; follows merges. | GET /v1/subjects/{id} | plotfare_get_subject | public |
| Get synthesis The cited summary plus every cited claim flattened with its URL. MCP defaults to recent. | GET /v1/subjects/{id}/synthesis?scope=overall|recent|aspect:<key> | plotfare_get_synthesis | public |
| Get claims Claims with weight, corroboration and freshness, strongest first. | GET /v1/subjects/{id}/claims?aspect=&since=&min_weight= | plotfare_get_claims | public |
| Resolve citation One claim; retracted claims answer with their status instead of 404. | GET /v1/claims/{id} | plotfare_get_claim | public |
| Get changes How the summary changed over time, and claims reporting a change. | GET /v1/subjects/{id}/changes?since= | plotfare_get_changes | public |
| Get gaps What the record doesn't know yet, best question first. | GET /v1/subjects/{id}/gaps | plotfare_get_gaps | public |
| Search outcomes Shared trips and lists, most useful first by their thumbs, with comment and open-question counts. | GET /v1/outcomes?q=&limit= | plotfare_search_outcomes | public |
| Get outcome One shared outcome: its places, pinned claims, thumbs, comments and questions. | GET /v1/outcomes/{id} | plotfare_get_outcome | public |
| Draft contribution A structured ContributionDraft (never a transcript). Returns the preview URL. | POST /v1/contributions/draft | plotfare_draft_contribution | assistant key |
| Request consent The consent URL to give the person. Nothing publishes until they approve. | POST /v1/consent/request | plotfare_request_consent | assistant key |
| Consent status Where the review stands; the first call after approval returns the single-use token. | GET /v1/consent/{draft_id} | — | assistant key |
| Publish Publishes the approved draft once, shown as “via <assistant>”. Returns citation URLs. | POST /v1/contributions/{draft_id}/publish | plotfare_publish_contribution | assistant key + consent token |
| Ask question Asks up to five recent visitors on the person's behalf (or as a signed-in user). | POST /v1/subjects/{id}/questions | plotfare_ask | assistant key + consent token |
| Assistant registry Every registered assistant and how many contributions it brokered. | GET /v1/assistants | — | public |
| Public export Daily JSON-lines dump of the record under CC BY 4.0 (manifest at /v1/export). | GET /v1/export/latest | — | public |
The rules
- Drafts carry structured claims, never the conversation: a
transcriptfield anywhere is rejected (ContributionDraft schema). - Nothing publishes until the person approves it; their token works once.
- Every contribution you broker shows “via” your assistant’s name.
- Cite claim URLs and their as-of dates when you use the data.
- Everything is CC BY 4.0; the whole record is in the daily export.