_ registry / mcp streamable-http · checked 4h ago

subpay-document-reader

https://subpay.ai

Registry code: cda6b6603af3401a

api record

Reads construction pay applications — the AIA G702 Application and Certificate for Payment with its G703 Continuation Sheet, including Procore and Textura versions — and change orders, from PDF into structured JSON with arithmetic checks. Call extract_document with the PDF base64-encoded; it costs $0.04 per page (up to 25 pages) in USDC per successful read over x402 (Base or Solana) — the payment request quotes the exact amount for your document — and failed reads are not charged. First 3 reads a day are free (documents up to 10 pages, no payment needed); after that, the usual price. Output…

endpoint
https://subpay.ai/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is subpay-document-reader live?
Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
Is subpay-document-reader free to use?
Not measured yet.
What tools does subpay-document-reader have?
3 tools: about, request_capability, extract_document.
Is subpay-document-reader safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.6%· all time 99.6%

latency
783ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 234 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • extract figures from construction pay applications
  • read change order pdfs into structured data
takes → gives
documents → data
tools
2 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • about reads unknown never probed

    Free. What extract_document reads, its price, payment networks, and terms.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • request_capability unknown never probed

    Free. Tell Subpay about a construction document or field extract_document doesn't support yet (e.g. lien waivers, invoices), and the most you'd pay per read. Used to decide what to build next. No personal information, please.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "documentType"
      ],
      "properties": {
        "notes": {
          "type": "string",
          "maxLength": 2000,
          "description": "Anything else. Please don't include personal information."
        },
        "documentType": {
          "type": "string",
          "maxLength": 120,
          "minLength": 2,
          "description": "The document you want read, e.g. 'conditional lien waiver', 'subcontractor invoice', 'schedule of values'."
        },
        "fieldsNeeded": {
          "type": "string",
          "maxLength": 1000,
          "description": "The fields you need extracted from it."
        },
        "monthlyVolume": {
          "type": "integer",
          "maximum": 10000000,
          "minimum": 0,
          "description": "Roughly how many per month."
        },
        "maxPricePerReadUsd": {
          "type": "number",
          "maximum": 1000,
          "minimum": 0,
          "description": "The most you would pay per read, in US dollars."
        }
      }
    }
    arguments 37 lines
  • extract_document reads unknown never probed

    Reads construction pay applications — the AIA G702 Application and Certificate for Payment with its G703 Continuation Sheet, including Procore and Textura versions — and change orders, from PDF into structured JSON with arithmetic checks. Returns gross this period, retainage held and released, completed to date, contract sum, balance to finish and payment due for pay apps; for change orders, whether it is the subcontractor's request or the GC's executed change order, plus number, amount and date. $0.04 per page (up to 25 pages) in USDC per successful read via x402, quoted before you pay; failed reads are free. First 3 reads a day are free (documents up to 10 pages, no payment needed); after that, the usual price.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "document"
      ],
      "properties": {
        "gc": {
          "type": "string",
          "description": "General contractor name."
        },
        "document": {
          "type": "string",
          "description": "The PDF, base64-encoded (a data: URL prefix is fine). Max about 3 MB and 25 pages."
        },
        "fileName": {
          "type": "string",
          "description": "Original file name, if known."
        },
        "subcontractor": {
          "type": "string",
          "description": "Subcontractor company name — helps tell an RCO from a GC change order."
        }
      }
    }
    arguments 25 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id cda6b6603af3401a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/cda6b6603af3401a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/cda6b6603af3401a/badge.svg)](https://brick.blue/agent/cda6b6603af3401a?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.