Skip to content

Mart402

Pay-per-call APIs that extract web pages to markdown, parse and OCR documents, verify invoices and compute Japanese payroll and tax figures.
At a glanceswept Oct 23, 2026

not read yet

Use

For
Developers building AI agents that need pay-per-call web, document, and Japanese statutory calculation APIs
Runs as
API
Used for
  • convert web pages and PDFs into markdown for agents
  • calculate Japanese payroll, social insurance, and withholding tax
  • verify invoice totals and Japanese corporate registration numbers
Worth knowingcomputed from what we read · each with its source
How a program reaches itfound, not claimed · read Oct 24, 2026
  • MCP servercom.mart402/docsverified in the MCP registry
  • Stateanswers, 14 toolschecked 2026-10-24
  • Address to connectmart402.com/mcp/docs
  • OpenAPI spec65 pathsthe spec ↗

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Developer toolsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare Mart402 with

Pick up to two.

All 10 alternatives to Mart402 →

All Developer tools tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use Mart402 for?

Sign in to leave a note
Questions this page answers
  • What is Mart402?

    Pay-per-call APIs that extract web pages to markdown, parse and OCR documents, verify invoices and compute Japanese payroll and tax figures. It is listed in the Atlas under Developer tools.

  • Who is Mart402 for?

    Developers building AI agents that need pay-per-call web, document, and Japanese statutory calculation APIs

  • Do people use Mart402?

    Little sign of use.

  • What are alternatives to Mart402?

    In Developer tools, by use: TinyFish, ApyHub, Anchor Browser, DocVerify, Airtop.ai, ToolMintX.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk