marfa.so valid

Marfa

Marfa is a server you run yourself that holds one person's data in one place, in types every app understands, so the apps, scripts and AI agents they allow can read and write it through one HTTP API.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T13:17:25.878Z. Cached copy · Source on marfa.so

# Marfa

> Marfa is a server you run yourself that holds one person's data in one place, in types every app understands, so the apps, scripts and AI agents they allow can read and write it through one HTTP API.

These docs cover what Marfa is, running an instance, building apps, connectors and agents on it, and the API. Each written page below links to its Markdown copy, and the same address without `.md` is the HTML. A request for a page's address with `Accept: text/markdown` gets the Markdown copy too. `https://docs.marfa.so/docs-map.md` is this index with HTML links.

`https://docs.marfa.so/llms-full.txt` holds the written pages in one file. It leaves out the API operations and the changelog. The changelog is long, and an operation's Markdown copy holds only its title and description, so each API operation links to its HTML page, which holds its full request and response. The API description with every operation is `openapi.json` in https://github.com/withmarfa/marfa. The changelog's Markdown copy is `https://docs.marfa.so/changelog.md`. The docs MCP server at `https://docs.marfa.so/mcp` searches every page, including the operations and the changelog, and its `docs_fetch` tool reads one page.

## Overview

### Get started

- [Overview](https://docs.marfa.so/overview.md): Marfa is a shared data layer for your apps, and you run it yourself.
- [Introduction](https://docs.marfa.so/introduction.md): What Marfa is, what you can do with it, what it isn't, and where it runs.
- [Quickstart](https://docs.marfa.so/quickstart.md): Start Marfa on your own computer, claim it, make a key, and write and change your first note.

### Concepts

- [How Marfa works](https://docs.marfa.so/how-marfa-works.md): The parts of Marfa and how they fit together, from the instance that holds your data to the apps, devices and connectors that reach it.
- [Items and types](https://docs.marfa.so/items-and-types.md): An item is one record, such as a note or a task, and its type says what the item holds. Everything else in Marfa builds on these two ideas.
- [Properties, metadata and edges](https://docs.marfa.so/properties-metadata-and-edges.md): An item's data lives in four places, properties, tags, extensions and edges, and each suits a different kind of information.
- [Versions](https://docs.marfa.so/versions.md): How an item's version counts its changes, so that two apps writing the same item never silently overwrite each other.
- [Files](https://docs.marfa.so/files.md): How Marfa keeps a file's bytes once, however many items name them, who may read them, and where the copies live.
- [Access](https://docs.marfa.so/access.md): Who can act on an instance, and how a key or an app is limited to the data and operations it needs.
- [Events and webhooks](https://docs.marfa.so/events.md): How an app learns what changed in an instance, by reading the event stream or by receiving webhooks.
- [Devices](https://docs.marfa.so/devices.md): How an app keeps a copy of your data on a phone or
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=marfa.so · GET /v1/domain/marfa.so · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for marfa.so:
1. POST https://agentwebmap.com/v1/sites/marfa.so/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://marfa.so/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/marfa.so/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/marfa.so).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.