Skip to content

Payperwork

Stores short-lived key-value values behind unguessable IDs and proxies chat completions to hosted language models, with each request paid in USDC.
Payperwork: data, price, alternatives
At a glancechecked Nov 1, 2026

not read yet

Use

For
Developers and AI agents that need to pay per call for temporary data handoffs or model inference over x402.
How it runs
API
Used for
  • pass short-lived values between agents through temporary boxes
  • wait on a box until another agent posts a value
  • send chat completions to frontier models, paid per call
Worth knowingcomputed from what we read · each with its source
How a program reaches itfound, not claimed · read Nov 1, 2026
  • MCP serverapp.payperwork/aiverified in the MCP registry
  • Stateanswers, 2 toolschecked 2026-11-01
  • Address to connectpayperwork.app/ai/mcp

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 Databy use, among tools still maintained

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

Compare Payperwork with

Pick up to two.

All 10 alternatives to Payperwork →

All Data 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 Payperwork for?

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

    Stores short-lived key-value values behind unguessable IDs and proxies chat completions to hosted language models, with each request paid in USDC. It is listed in the Atlas under Data.

  • Who is Payperwork for?

    Developers and AI agents that need to pay per call for temporary data handoffs or model inference over x402.

  • What are alternatives to Payperwork?

    In Data, by use: Hugging Face, Notion, Ultimaps, TariffMonkee, Geonode.

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