Source / evidence / Markdown
Context an agent can use without losing the source.
GetMD turns approved source material into bounded Markdown with visible provenance, quality outcomes, and stable interfaces.
One accountable lifecycle
Submit a source, create a durable job, inspect quality and warnings, then retrieve a retained output. The same lifecycle is available on the web, API, CLI, and MCP.
Capability truth, not marketing guesses
3 source contracts and 6 output profiles are published from the live registry.
Authority stays explicit
OAuth grants expose only approved tools. Organization ownership is enforced below the transport, signed links expire, and local paths remain local.
Built for bounded automation
Idempotent creation, durable identifiers, retry guidance, cursor pagination, cancellation, deletion, and machine-readable errors make failures inspectable.
Genuine questions
Frequently asked
Does GetMD give an agent access to local files?
Hosted MCP does not accept local paths. Local file access is available only through the local stdio bridge and an explicit allowed root.
Does a succeeded job mean every claim is true?
No. Success means the pipeline completed. Consumers must also inspect warnings, quality disposition, provenance, and known limitations.
Can I discover support programmatically?
Yes. The v1 capabilities endpoint returns current source types, profiles, formats, languages, and hard limits.