SameDayDesk x402 and MPP Data Gateway

Optional bounded batch extraction

EXTRACT_BATCH_ENABLED=1 adds POST /extract/batch and MCP extract_batch at an introductory 0.01 USDC per admitted batch of 1–5 public HTTPS URLs. The default is off: 25 paid HTTP operations and 22 MCP tools; enabled: 26 and 23. This price is not a measured margin guarantee. Use one server process and persistent COMMERCE_DATA_DIR; unknown settlement is quarantined, not automatically charged again. Bounded partial output does not promise every source or requested field.

The new MCP tool projects the existing HTTP payment and durable replay handler. Its challenge resource is https://agents.samedaydesk.com/extract/batch, not mcp://: first call without payment, then reuse the returned HTTP resource and exact arguments with _meta["x402/payment"]. MPP callers may use the unmodified www-authenticate challenge in result _meta["samedaydesk/http"].headers and send its credential as HTTP Authorization. That metadata also carries the HTTP status and receipt headers. Never translate an MCP-resource credential. Existing MCP tools retain their existing native MCP payment boundary.

The signed statement declares 25 standard route capabilities in either flag state (Circle is separate); it does not claim that a disabled route is available or authorize payment. Live discovery excludes disabled batch extraction.

Every paid HTTP response advertises /.well-known/agent-payment-evidence.json through the standard HTTP describedby link relation. The bounded free manifest joins each exact method and route to its seller-declared read-only effect, recursively guaranteed JSON paths, response-schema digest, exact replay binding, receipt behavior, and the existing signed deployment statement. It does not change x402 or MPP terms and is not authorization to spend; buyers must still verify the live challenge, paid output, receipt, and settlement.

Twenty pay-per-call tools for deterministic agent-work opportunity preflight, machine-service discoverability, payment-offer preflight, Morpho borrower and market decisions, protection plans, URL extraction, Markdown reading, repository security scans, company and wallet enrichment, structured data generation, transaction receipt evidence, delegated-signer policy conformance, settlement proof, and AI-search readiness audits.

• Product page: https://samedaydesk.com/x402
• Smithery: https://smithery.ai/servers/epistemedeus/x402-data-gateway
• Remote MCP: https://agents.samedaydesk.com/mcp
• Agent Plugins 1.0 local package: plugins/samedaydesk-x402 (not marketplace-listed)
• Claude Code marketplace: .claude-plugin/marketplace.json plus plugins/samedaydesk-extract (samedaydesk-extract@samedaydesk-claude; not an Anthropic official directory listing)
• Goose native config: goose/ (YAML, session flag, and deeplink; not a Goose installer)
• Live resource manifest: https://agents.samedaydesk.com/.well-known/x402
• OpenAPI: https://agents.samedaydesk.com/openapi.json
• Official MPP OpenAPI: https://agents.samedaydesk.com/mpp-openapi.json
• Skill contract: https://agents.samedaydesk.com/skill.md
• Action catalog: https://agents.samedaydesk.com/api/actions
• A2A agent card: https://agents.samedaydesk.com/.well-known/agent-card.json
• Global A2A Registry: https://www.a2a-registry.org/agent/9cb0b8e6-cb1f-422b-a604-861d0a79e24b
• Settlement Radar: https://agents.samedaydesk.com/platforms
• Platform health JSON: https://agents.samedaydesk.com/v0/cards.json
• Aggregate machine-demand telemetry: https://agents.samedaydesk.com/v0/commerce-demand.json
• Morpho position risk: GET /defi/morpho-position?address=0x...&shocks=-10,-20,-30
• Morpho protection quote: GET /defi/morpho-protection?address=0x...&targetHealthFactor=1.25&protectAgainstShockPct=-10
• Morpho market underwriting: GET /defi/morpho-market-underwrite?marketId=0x...
• Morpho PreLiquidation replay: GET /defi/morpho-preliquidation-replay?transactionHash=0x...
• Opportunity preflight: GET /work/opportunity-preflight?rewardUsd=10&hours=0.25&hourlyCostUsd=4&selectionProbabilityPct=20
• Agent discoverability audit: GET /distribution/agent-discoverability-audit?origin=https://example.com&intent=extract+a+public+website+into+structured+JSON&route=/extract&method=GET&runtimeUrl=https%3A%2F%2Fexample.com%2Fextract%3Furl%3Dhttps%253A%252F%252Fexample.org&surfaceAudit=true&materializationAudit=true
• Payment offer preflight: GET /commerce/payment-offer-preflight?url=https://example.com/paid-route
• Seller integrity audit: GET /commerce/seller-integrity-audit?origin=https://seller.example&route=/paid-route&method=GET&requiredPaths=data.attributes
  • A buyer may add referral=r1_<sha256> derived from its complete seller-signed x402 settlement receipt. This creates a declared acquisition label, not verified proof. POST /commerce/referral-recheck accepts that receipt plus one downstream seller-signed settlement receipt from a distinct payer and transaction, then atomically grants at most one free changed-state recheck. The receipts prove neither an application HTTP 200 response nor output delivery or validity, and public posting or broadcasting is optional. A file matching Agent402 PR 1070's observable capture contract (bare pretty JSON receipt, no bundled Agent402 source) is already a drop-in input after ordinary JSON.parse; see docs/agent-outcome-referral-experiment.md and agent402-receipt-interop.test.mjs.
• Contract-qualified search: GET /commerce/contract-qualified-search?query=service+domain+ownership+code+provenance&requiredPaths=data.sourceRepository returns a bounded advisory OpenAPI repair plan for missing buyer-required paths without mutating seller files or inferring undeclared property types.
• Base USDC settlement proof: GET /commerce/settlement-proof?transactionHash=0x...&recipient=0x...&amountAtomic=5000
• Base or Ethereum transaction receipt: GET /chain/transaction-receipt?transactionHash=0x...&network=base
• Wallet policy conformance: POST /security/wallet-policy-conformance
• Wallet policy conformance contract: GET /schemas/wallet-policy-conformance-v1.json
• Stateful wallet policy conformance: POST /security/stateful-wallet-policy-conformance
• Stateful wallet policy contract: GET /schemas/stateful-wallet-policy-conformance-v1.json
• Material-change alert probe: https://agents.samedaydesk.com/alerts
• Agoragentic seller callback: POST /integrations/agoragentic/ai-readiness-audit
• the402 signed fulfillment webhook: POST /integrations/the402/webhook

No API key or subscription is required. Every paid HTTP route advertises x402 and native MPP Payment authentication in the same 402 response. Both protocols settle the same exact USDC amount to the same Base mainnet merchant wallet. MCP tool calls remain x402-gated.

The Morpho route is read-only. It calculates LTV, LLTV, health factor, liquidation headroom, and collateral-price shock scenarios from integer protocol values, then cross-checks indexed collateral, borrow shares, and oracle price against direct Base RPC state. Scenarios are calculations rather than probabilities or transaction recommendations. The separate protection route uses a fresh direct-RPC oracle read and direct confirmation of collateral and borrow shares to calculate exact partial-repay and add-collateral amounts. It returns unsigned token-approval and Morpho-call templates, explicit execution buffers, revalidation requirements, and economic postconditions. It never accesses a wallet, signs, broadcasts, or takes custody.

The service also keeps a privacy-safe demand telescope on a persistent Railway volume. It records route families, query key names, challenge/success classes, and pseudonymous repeat-use signals. External fetches are acquisition signals, not verified buyers, because unidentified automated indexers can remain. Recognized crawler and agent-indexer user agents are reduced at ingestion to a controlled source label and reported in a separate machine-discovery lens with source and route coverage. Those observations measure fetches, not authenticated catalog referrals, intent, or demand. Unmatched requests are reported separately from a conservative semantic-candidate subset; neither becomes demand until an independent caller repeats or converts. It does not record raw IP addresses, user agents, URLs, query values, bodies, payment headers, marketplace payloads, or credentials. Public output is aggregate only; owner traffic is excluded and crawler traffic remains excluded from demand even when its controlled discovery counts are reported separately. Common exploit probes such as .env, .git, and WordPress discovery paths are classified as scanner traffic and excluded as well.

Version 1.9.4 adds explicit paid-traffic classes without exposing buyer addresses. COMMERCE_PAYER_CLASSES accepts a JSON array of { "address", "class" } records. Controlled classes are internal, validation, incentivized, affiliated, and independent. Addresses are converted to the same secret-keyed payer pseudonyms already used by telemetry and classified at read time, which also permits retroactive correction without storing a raw address. Unknown payers remain unclassified; unfamiliar wallets never become independent demand by inference. The public snapshot reports paid success by class plus independent and repeat-independent actor counts.