Research Markdown for humans and agents

Bring a paper in. Leave with a package you can actually work with.

Mdtero parses the paper, keeps the figures, and hands back clean Markdown your next reading, translation, or review step can reuse.

Start in Account ⬇ Download ZIP build See demo package

Tomorrow's shortest path: start in Account for agent setup. Reach for the ZIP build only when you need local page capture.

Agent Install

Connect Mdtero to the agent you already use

Setup lives in Account. Once you create a key, Mdtero prepares the handoff message for the agent you already use.

Supported platforms

OpenClaw

Best for longer research runs with the official ClawHub install plus your own OpenClaw node.

Claude Code

Best when Mdtero should stay inside your editor loop.

Codex

Best for terminal-native Codex workflows.

Gemini CLI

Best for CLI-first Gemini workflows.

Open Account, create a key, choose your agent, and copy the prepared install message.

Open Account

Markdown Clean structure for reading and prompting

Figures Downloaded and linked for reuse

Translation Aligned with the same paper structure

Bundle Ready for your next agent step

Start here

Two entry points. One output format.

Most people should start in Account and connect Mdtero to the agent they already use. Reach for the extension only when a live paper page needs local capture.

Agent

Agent Handoff

Create one key, copy one install message, and keep the handoff inside your normal agent workflow.

Open Account

Extension

Browser Extension

Best when you are already on a supported paper page and want a local capture path without extra setup.

Open Edge listing

Workflow

A paper goes in. A reusable research package comes out.

Capture the paper you actually want

Start from a DOI, a supported paper page, arXiv, or a local retrieval helper and keep the acquisition path explicit.

Turn papers into a structured research package

Get Markdown, figures, downloadable artifacts, and machine-usable task results instead of a fragile one-off scrape.

Translate, organize, and preserve evidence

Use translation only when needed, while keeping the package auditable and ready for downstream review or synthesis.

Hand it off to your next agent step

Move straight into summarization, review drafting, weekly discovery loops, or your own research automation.

Use Cases

Three agent-ready research jobs

Discovery, translation reading, and review writing can all start from the same paper package.

Weekly Discovery

Pair Semantic Scholar discovery with a reproducible capture loop

Use Semantic Scholar to surface new papers, then feed the shortlisted links into Mdtero so each candidate becomes a consistent package for screening and note taking.

Every Friday, collect this week's promising papers from Semantic Scholar, send the selected links through Mdtero, and return a shortlist with package links and one-line relevance notes.

Translation

Translate a paper without losing its research structure

Run Mdtero's built-in translation on top of the parsed package and get a cleaner target-language Markdown copy that keeps the same sections, figures, and references.

Parse this paper with Mdtero, run the built-in Chinese translation, and return the translated Markdown with the same section, figure, and reference anchors preserved.

Literature Review

Draft a literature review from evidence-preserving packages

Once a set of papers is normalized into the same package format, your agent can compare claims, extract methods, and draft a review without fighting format drift.

Compare these Mdtero packages, group them by method and evidence type, then draft a literature review outline with citations back to each paper package.

Pricing

Pricing that stays simple once the paper count starts climbing

Free

Start with the core workflow.

30 parses / mo
3 translations / mo
Source file downloads

Standard

$3.9 / month

The best default for steady weekly reading and light translation work.

120 parses / mo
30 translations / mo
Priority processing

Pro

$7.9 / month

More breathing room for heavier review, comparison, and synthesis work.

300 parses / mo
100 translations / mo
Priority processing

Translation Add-on

$2 / pack

Add this when you only need more translations without changing plans.

20 translations / pack
Translation only
Best for topping up after plan quota

API pay-as-you-go stays available for flexible product and automation use, but plans remain the default path for most researchers.

FAQ

What researchers usually ask before they commit a workflow to it

What is supported right now?

Today Mdtero already supports supported paper-page capture, DOI-led parsing, arXiv-friendly flows, translation, and agent/API handoff on the same product surface.

Do I have to change my whole research workflow to use it?

No. Mdtero is designed as a preprocessing layer that fits into your current reading, note-taking, API, and agent workflows.

Is translation mandatory?

No. Translation is optional. The core product is the structured package that makes the next research step easier.

How does payment work at launch?

Plans cover routine usage first with included monthly quota. Translation add-ons top up extra translation volume, balance remains available for flexible use, and API pay-as-you-go is there for product or automation workflows.

I'm new here — what is an .md file?

An .md file is a Markdown file: plain text with lightweight formatting for headings, lists, tables, links, and images. Mdtero uses it because both humans and agents can read it cleanly. If you want the easiest viewer, open it in Typora; VS Code and many note apps also work well.

My OpenClaw runs on a server and cannot use a campus IP. What should I do?

Use a split workflow. Keep Elsevier or ScienceDirect acquisition on a machine that really has the right local network conditions — usually your own computer with the Mdtero local helper or browser extension. Then send the resulting Markdown or bundle to your server-hosted OpenClaw.