Plumb Data Exchange
Verified table jobs: CSV conversion, dedupe, reconcile. Pay per call with x402 (USDC on Base).
Hosted MCP Server
npx add-mcp 'https://numba2witcheese.tail7d8d44.ts.net:10000/pde-mcp'Installs into Claude Code, Codex, Cursor and more
Documentation
Plumb Data Exchange
Verified table data jobs for agents: convert a table to CSV, deduplicate rows by key columns, or reconcile two versions (added/removed/changed). Results are independently verified before release; failed or unclaimed jobs are refunded. Fetch status and the result with the returned accessToken.
Price: $0.05 USDC per job on Base (eip155:8453), paid with x402 v2. Limits per table: 1000 rows, 32 columns, 65536 characters. All values are strings; keys match exactly.
Doors
- MCP (streamable HTTP, stateless): POST /pde-mcp Paid tools: convert_to_csv, deduplicate, reconcile. Free: get_job. An unpaid call returns the x402 PaymentRequired as the tool result (isError, structuredContent); retry with _meta["x402/payment"] = PaymentPayload. The settlement comes back in _meta["x402/payment-response"].
- HTTP: POST /x402/jobs with {"capability", "inputs"}. 402 + PAYMENT-REQUIRED header, retry with PAYMENT-SIGNATURE. 201 returns jobId + accessToken. GET /x402/jobs/{jobId} and /x402/jobs/{jobId}/artifact with "Authorization: Bearer ".
Capabilities
- table.to_csv.v1: inputs = {columns, records}. Output CSV; verified by round-trip.
- table.deduplicate.v1: inputs = {table, keyColumns, keep: "first"|"last"}. Output JSON rows + duplicate groups.
- table.reconcile.v1: inputs = {before, after, keyColumns}. Output JSON added/removed/changed.
Guarantees
- Inputs are validated before you are asked to pay.
- One payment authorization buys exactly one job (replays are refused).
- Results are released only after independent verification; a job not completed by its deadline is refunded.
Reference
- OpenAPI (HTTP door): /openapi.json
Payment verification (MCP: /pde-mcp)
- verify_payment ($0.02 USDC, x402; $0.002 for an XRP Ledger payment, invoiceId binds it to your invoice): did tx T transfer at least N of token X (default USDC) to payee P, optionally from payer F? Proven by Plumb without trusting any RPC (Base: proof-backed L1 checkpoints; Ethereum: light client; XRP Ledger: a quorum of Ripple's validator list, chain "xrpl", token RLUSD/XRP/CUR.rIssuer, amounts in drops or millionths, level unl_quorum, final). Bound to the exact transfer (log index). Verdicts: paid, pending, not_paid, underpaid, ambiguous, failed_transaction, unverifiable. Never not_paid while a payment is pending; abstains (unverifiable) whenever the proof is incomplete.
- On Base, paid = under a proof-backed checkpoint (level tee_attested / zk_proven / resolved), usually about an hour after the payment; status "proven" until challengeableUntil, then re-checked to "final" (resolved).
- HTTP door (no MCP needed): POST /x402/verify with the same claim JSON; pay the 402 with PAYMENT-SIGNATURE (x402 v2).
- try_verify_payment: free, 3 NEW claims per client per day. get_verification: free poll by checkId. Asking again about a claim already checked is free (one check per claim covers its re-checks).
- requiredLevel (tee_attested | zk_proven | resolved on Base; finalized on Ethereum): the answer's "release" block says whether money can be released, and why not.
- callbackUrl (paid checks; https, port 443, public host) or watch_verification: signed POSTs on level_reached, changed, final, gave_up (x-plumb-signature = Ed25519 over the raw body with the key below); retried with backoff.
- Receipts: ed25519 signature over receipt.payload (canonical JSON). keyId 378a63326007fdc1, public key (hex) 1f81dedec119cf6f252a446a23d1dc508f8a38c65320f43046e1a163ad0c94c2
- verify_payments_batch: up to 25 claims (JSON or CSV: chain,txHash,payee,token,minAmountRaw,payer,logIndex,invoiceId) for one flat price; claims already checked are free. get_verifications: free bulk read (<=50), format "csv" for reconciliation.
- check_x402_receipt (free): verify a seller's signed x402 offer + receipt (pin the seller), get the exact claim to prove, then pass the verification's checkId to learn which side failed (seller signature or chain).
- x402 batch settlements (one transfer aggregating many vouchers) are flagged "aggregate" and never releasable.
- Guide (five minutes, answer fields, callbacks, comparison with an RPC lookup): /verify
Proven XRP Ledger reads (MCP: /pde-mcp, tool prove_xrpl_transaction; HTTP: POST /x402/xrpl/tx {"txHash"})
- $0.002 per transaction (x402: USDC on Base, RLUSD/XRP on the XRP Ledger, PDC credits). Any XRPL transaction, proven without trusting any server: Ripple's validator list checked against the pinned publisher key, a ledger signed by 80% of the validators, hash links to the transaction's ledger, the ledger's transaction tree rebuilt and compared with its header. You get the full decoded fields and metadata (AffectedNodes: balances, trust lines, escrows, payment channels, credentials AS OF this transaction), the quorum evidence (validators/of, proof ledger, hash links walked) and a receipt signed with the key below.
- A transaction not yet in a validated ledger answers 425 pending_validation with retry-after: your payment is kept and the retry with the SAME payment is free. An unprovable hash answers verified:false with the reason (the prover's answer is the product). One payment buys one transaction; a replay for another hash is refused.
- Not offered: the current state tree (a live balance). No public server proves it; balances are proven as of a transaction.
- The prover is open source: pip install plumb-xrpl (Apache-2.0) rebuilds the same proof on your machine.
On-ledger credential: ProvenPayer (XLS-70; MCP tool credential_status, free; HTTP GET /credentials and /credentials/)
- Issued by rBJLqqFKSpCNLoE5QCfcG2v4upQYPbCwfQ to an XRPL account after 2 settled, Plumb-proven payments to this exchange (RLUSD or XRP, any door), valid 90 days. You accept it once (CredentialAccept from your account); then any seller can read it with ledger_entry {credential: {issuer, subject, credential_type: hex("ProvenPayer")}}. The issuing transaction is provable with plumb-xrpl; the object is ledger state read from a server, which is said plainly.
- Holder unlock here: sign hex("plumb-data-exchange credential challenge " + unixSeconds) with the account key and pass xrplProof {account, publicKey, timestamp, signature} to try_verify_payment: 25 free checks a day instead of the anonymous limit.
- The house issues; nobody can request. Eligibility comes from the house's own settled-payment journal (W-18: the house admits).