Prototyp · Vorschau: alle Server aus der offiziellen Registry, alle 30 Minuten synchronisiert. Bewertungen und Benutzerkonten folgen in einem späteren Schritt.
PopNx MCPMCP-Server für alle, die KI nutzen · in einfachen Worten erklärt
Einsteigermodus Aus
FarbenSystemHellDunkel
SpracheไทยEnglish中文日本語한국어EspañolDeutsch
☰ MenüEinstellungen
Einsteigermodus Aus
FarbenSystemHellDunkel
SpracheไทยEnglish中文日本語한국어EspañolDeutsch

X402 Data Gateway

von epistemedeusVersion 1.23.55i★ –iLäuft in der Cloud
Name in der Registryio.github.epistemedeus/x402-data-gateway

Installieren

Überblick

Beschreibung vom Entwickler (englisches Original)

Agent tools for discovery, payment safety, data extraction, and DeFi.

Die drei Säulen von PopNx MCP

Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.

Was du damit machen kannst

Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.

  • Verbindung: Läuft in der Cloud
  • Transport: Streamable HTTP
  • Kategorie: Onlineshops & Zahlungen

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Bevor du installierst

Du brauchst

Welche App nutzt du?

Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.

Funktioniert in Claude im Web, auf dem Desktop und auf dem Handy:

  1. Öffne Settings → Connectors
  2. Tippe auf Add custom connector
  3. Füge die Adresse unten ein und tippe auf Add
  4. Wenn eine Anmeldung verlangt wird, melde dich beim Dienst des Entwicklers an
SettingsConnectors1+ Add2https://…3
https://agents.samedaydesk.com/mcp

Führe das in deinem Terminal aus

claude mcp add --transport http x402-data-gateway https://agents.samedaydesk.com/mcp

In Cursor öffnen

Oder kopier die Einstellungen selbst

In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen

{
  "mcpServers": {
    "x402-data-gateway": {
      "url": "https://agents.samedaydesk.com/mcp"
    }
  }
}

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

In VS Code öffnen

Oder kopier die Einstellungen selbst

In .vscode/mcp.json in deinem Projekt einfügen

{
  "servers": {
    "x402-data-gateway": {
      "type": "http",
      "url": "https://agents.samedaydesk.com/mcp"
    }
  }
}

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

ChatGPT verbindet sich nur mit Servern im Internet:

  1. Öffne ChatGPT im Web → Settings → Connectors (Apps)
  2. Tippe auf Create oder Add (bei manchen Tarifen musst du zuerst Developer mode unter Advanced einschalten)
  3. Füge die Adresse unten ein, gib ihr einen Namen und speichere
  4. Wenn eine Anmeldung verlangt wird, melde dich beim Dienst des Entwicklers an
SettingsConnectors1+ Create2https://…3
https://agents.samedaydesk.com/mcp

Menünamen können sich je nach Tarif und mit der Zeit leicht unterscheiden.

Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Was er kann

Tool-Namen und -Beschreibungen genau so, wie der Server sie am 6. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.

  • careers_board

    Read one configured public careers board and return title, location or null, posting URL, source, fetchedAt, and explicit coverage. Use `careers_board_cold` for the acquired free recipe. Partial, missing, duplicate, listed, empty, and changed stay explicit. A source failure is un

  • extract

    Fetch a public HTTP(S) page and return compact extraction signals for programmatic inspection: title, meta description, Open Graph/Twitter metadata, JSON-LD, headings, links, text excerpt, and AI-readiness flags. Use `read` instead when you need the page body as LLM-ready Markdow

  • extract_batch

    Fetch one to five public HTTPS URLs and return bounded structured fields for each source in one paid attempt. Supply `urls` as a JSON array and optional unique `fields`. Use `extract` for a single URL when you do not need batch accounting. Charge is one flat introductory 0.01 USD

  • lockfile_pin_delta

    Inspect two caller-supplied npm package-lock.json objects and return added, removed, and changed name+version+integrity+resolved pins. Supply JSON `before` and `after` lockfile objects, not filesystem paths, URLs, or commands. An identical pin set is informational, not a failure.

  • read

    Fetch a public HTTP(S) page and return its readable body as cleaned Markdown for LLM context, preserving headings, links, and lists while dropping navigation, ads, scripts, headers, footers, asides, and forms. Use `extract` instead when you need metadata, JSON-LD, Open Graph/Twit

  • scan

    Static supply-chain security scan of a public GitHub repo before an agent installs/runs it. Flags exfil sinks, obfuscation, credential reads, install-time curl|bash. risk=clean|suspicious|dangerous. Payment challenge and credentials are bound to GET https://agents.samedaydesk.com

  • schemaforge

    Analyze a public business site and return a deterministic, paste-ready JSON-LD template plus the live structured-data gap diff and ranked fixes. Use `deep_audit` instead when the same call must also return company, technology, contact, and DNS/email evidence. Generated markup con

  • enrich

    Inspect a public company domain and return structured identity, technology, social, contact, DNS, email-infrastructure, and AI-readiness evidence. Use `schemaforge` instead for a paste-ready JSON-LD template and remediation diff, or `deep_audit` when both outputs are required tog

  • wallet_enrich

    Inspect a public Base or EVM address and return an agent-ready on-chain profile: EOA or contract type, native and curated token holdings, token/NFT metadata, proxy evidence, activity, and a derived profile label. Use `enrich` for a company domain; the two tools accept different i

  • deep_audit

    Run one read-only AI-search-readiness audit for a public business domain: company, technology, contact, and DNS/email evidence from `enrich`, plus the live structured-data gap analysis and paste-ready JSON-LD template from `schemaforge`. Use `enrich` for company facts only or `sc

  • morpho_position

    Inspect one Base borrower across Morpho markets and return position balances, LTV, health factor, liquidation headroom, direct-RPC verification, and caller-selected collateral-price stress scenarios. Use `morpho_protection` when you need exact repay or add-collateral amounts and

  • morpho_protection

    Calculate two alternative protection plans for one Base Morpho borrower under a selected collateral-price shock and target health factor: partial repayment or added collateral. Each plan includes the bounded asset amount, expected stressed health factor, evidence basis, and unsig

  • morpho_market_underwrite

    Underwrite one Base Morpho market with independent GraphQL, REST, and direct-RPC evidence for configuration integrity, liquidity, utilization, concentration, borrower health bands, recent history, bad debt, and PreLiquidation availability. Use `morpho_position` or `morpho_protect

  • morpho_preliquidation_replay

    Reconstruct one successful Base Morpho PreLiquidation transaction from its receipt and the exact block state, returning repaid and seized assets, protocol-oracle valuation, gross incentive, configured health window, and transaction gas before off-chain costs. Use `morpho_market_u

  • opportunity_preflight

    Agent work opportunity -> deterministic attempt, verify-first, or abandon preflight using caller-supplied cost and selection assumptions plus dated platform evidence. Returns break-even probability, expected surplus, hard gates, and source-linked evidence. No claim, bid, payment,

  • agent_discoverability_audit

    Measure one service's brand-blind rank, source-family coverage, expected-route presence, canonical-vs-alias listing identity, duplicate records, competitors, and exact-price drift across ten public machine-service discovery views. Supply `runtimeUrl` with an exact GET route to de

  • payment_offer_preflight

    Compare x402 and MPP payment challenges, terms, and seller-declared JSON success-response readiness for one exact public HTTPS GET route before buyer authorization, including URL and realm binding, expiry, cross-protocol economic parity, and exact-route OpenAPI evidence. Use `age

  • seller_integrity_audit

    Use this after a buyer integration fails, a seller changes a paid route, or before the next paid retry or release. Audit one exact paid GET or POST seller route against buyer-required JSON success paths. GET verifies constructible non-secret input, exact request binding, live x40

  • contract_qualified_search

    Search Agent402 and the official MPP catalog for paid machine services that both match a capability intent and guarantee buyer-required JSON response paths. Use `agent_discoverability_audit` when you are measuring one known seller's catalog reach or rank, `seller_integrity_audit`

  • agent_surface_budget_audit

    Measure one public service's credential-free MCP tools/list, OpenAPI, or both declared discovery surfaces before any tool call or target payment. Use `agent_discoverability_audit` for catalog reach and rank, `seller_integrity_audit` for one exact operation's response contract, or

  • settlement_proof

    Verify one claimed canonical Base USDC settlement after execution by matching a successful transaction receipt to the exact recipient, atomic amount, and optional payer. Use `payment_offer_preflight` before authorization when you need to inspect an unpaid x402 or MPP offer instea

  • transaction_receipt

    Inspect one Base or Ethereum transaction hash and return normalized success or revert status, block time, gas and fee fields, decoded ERC-20 Transfer events, and canonical USDC transfers. Use `settlement_proof` instead when you must verify an exact canonical Base USDC recipient,

  • solana_transaction_receipt

    Inspect one finalized Solana mainnet transaction signature and return normalized success or failure status, slot, block time, fee, SPL-token owner deltas, and canonical USDC deltas. Supply recipient, amount, and optional payer when an exact settlement claim must be verified; use

  • wallet_policy_conformance

    Evaluate safe standardized allow, deny, and error observations from an agent wallet or delegated signer. Use this after running a bounded provider policy test matrix to distinguish explicit provider-policy enforcement from validation or generic provider failures and to test exact

  • stateful_wallet_policy_conformance

    Evaluate safe standardized observations from wallet policies that track prior or concurrent requests. Use `wallet_policy_conformance` instead for one-request action shape, method, chain, token, recipient, amount, and function controls. This tool separately tests sequential cumula

  • page_change

    Compare two already-held extract-batch JSON artifacts. charged is false. Not a paid SKU. Does not fetch, pay, or schedule a second observation. Compare only the explicitly selected data keys present on both matched rows. Missing keys are coverage unknown, not deletions; explicit

  • careers_board_cold

    Return the acquired cold careers-board recipe and its public tests. This tool is free: charged is false, it does not fetch a live board, and it does not accept payment. Use `careers_board` when you need one named-board observation. Direct free execution remains available.

  • report_caller_result

    Optionally state whether the current paid morpho_position result was useful or not_useful. This tool is free: charged is false, it does not repay, and it does not change the delivered purchase. Read the capability only from the paid result meta samedaydesk/mcp-caller-result. Sche

  • trial_read

    Read one public HTTP(S) page as bounded Markdown through the existing walletless trial. Read and extract share the same original authority, remaining hops, expiry and one concurrent operation. No separate reader allowance. Optional markdownLimitChars is an integer from 1 through

  • recover_paid_result

    Read the stored outcome of an earlier native paid call using its original input and credential. This call cannot execute or pay.

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 7. Nov. 2026

  • ✓ Bestanden

    Entwickler passt zum Repo

    Der Registry-Name wurde mit dem GitHub-Konto epistemedeus bestätigt, dem das Repo gehört

  • … Noch nicht geprüft

    Wird noch gepflegt

    Dieses Repo haben wir noch nicht von GitHub gelesen

  • … Noch nicht geprüft

    Hat eine Lizenz

    Dieses Repo haben wir noch nicht von GitHub gelesen

  • ✓ Bestanden

    Endpunkt antwortet

    Antwort in 181 ms (HTTP 200)

  • – Nicht zutreffend

    Anmeldung mit OAuth

    Keine Anmeldung nötig

  • ✓ Bestanden

    Keine versteckten Anweisungen in Tool-Beschreibungen

    Wir haben 30 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden

Im Vergleich mit anderen in Onlineshops & Zahlungeni

  • Mehr Sterne als 0 % der anderen 1754 Server in dieser Kategorie
  • Neuer in der Registry veröffentlicht als 79 % der anderen 1754 Server in dieser Kategorie
  • Basischecks gleich gut wie oder besser als bei 100 % der anderen 1754 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Häufige Fragen

Ist X402 Data Gateway sicher?

Er hat 3 von 3 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.

Welche Schlüssel oder Codes braucht er?

Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.

Läuft er auf meinem Computer oder in der Cloud?

Er läuft in der Cloud des Entwicklers. Du verbindest dich übers Internet, ohne etwas zu installieren, aber was du sendest, läuft über die Server des Entwicklers.

Wird er noch gepflegt?

Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (1.23.55) kam vor 7 Tagen in die Registry.

Welche Apps können ihn nutzen?

Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.

Was kann ich stattdessen nutzen?

In derselben Kategorie: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce

Alternativen

Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.

So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

Stripe MCP

von stripe

MCP server integrating with Stripe - tools for customers, products, payments, and more.

Läuft in der Cloud★ 2.043MITAktualisiert vor 12 Monaten
Installieren

MCP Cn Commerce

von TonyWang-hub

8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending

Läuft auf deinem Computer★ 96MITAktualisiert vor 28 Tagen
Installieren

README vom Entwickler

README öffnen

Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.

SameDayDesk x402 and MPP Data Gateway

Optional bounded batch extraction

Paid GET /extract and GET /read (and MCP extract / read) return a typed record after settlement. Merchant HTTP 200 is delivery of that record, not proof that the source succeeded or that the page is complete. The JSON keeps requestedUrl, observed finalUrl (also copied to url for compatibility), source HTTP status, sourceOk, a nullable error, and a capture object that labels the no-JavaScript GET, body/excerpt limits, charset, and truncation. A 403/404 with block text is not an empty 200. Observational HTTP delivery evidence may classify schema conformance, source refusal, and truncation; that is not buyer usefulness or a sold guarantee. The extract text field is a bounded excerpt. Omitted requests keep 1,200 characters. Optional textExcerptLimitChars from 1 through 40,000 is rejected before payment when it is not an integer in that range; the price stays the same and /read is not fetched. 40,000 matches the /read Markdown ceiling because the body was already capped at 3 MB. Batch requests use the same parser and a tighter ceiling so five excerpts cannot pass admission and then exceed the 128 KiB response cap. Use /read for longer Markdown. Neither route executes JavaScript, so missing discussion text is not proof of absence. Script data islands and comments are stripped; this is not a full-discussion reader. Production source connections validate and pin public IPv4 DNS answers, revalidate up to three redirects, and reject URL credentials, private addresses, IPv6 and compressed responses that ignore the requested identity encoding. Header/meta charset labels select a decoder; capture.charset names the decoder actually used. Unknown labels fall back to UTF-8 with an explicit fallback marker.

Batch rows retain requested source slots, including duplicates and failures. Each captured row's provenance.capture records the no-JavaScript method, actual byte allowance and 1,200-character text limit when text is requested. A known body or text cutoff is partial, not complete. This does not detect undisclosed missing content. Source refusal remains a failed row even when its error page has text. The in-process fetch/timeout test hooks have no HTTP, MCP or environment input binding and do not change settlement or authorization middleware.

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.

LOCKFILE_PIN_DELTA_ENABLED=1 adds POST /lockfile-pin-delta and MCP lockfile_pin_delta for two caller-supplied npm package-lock.json objects. The default is off. Production already has EXTRACT_BATCH_ENABLED=1 (26 paid HTTP / 23 MCP tools). Enabling lockfile beside that envelope is 27 / 24. Default-off catalogs remain 25 / 22. Default price is $0.005 (LOCKFILE_PIN_DELTA_PRICE), matching live GET /extract. Margin is not proven. Initial live release accepts x402 only; existing MPP routes including extract_batch are unchanged. HTTP JSON only: no filesystem paths, arbitrary commands, or network fetch. Identical pins are informational, not engine failure. The signed deployment statement is not rewritten here. The lockfile MCP tool's challenge resource is https://agents.samedaydesk.com/lockfile-pin-delta, not mcp:// and not /extract/batch.

The extract_batch 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)
  • Hermes Agent skills: hermes/ plus portable plugins/samedaydesk-x402/skills (AgentSkills SKILL.md drop-in; not a Hermes plugin or 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_ 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.
  • Discovery↔live payment drift (library/CLI only; not a hosted or paid route): node discovery-drift.mjs observe --url 'https://agent-economy-signal-x402-mainnet.bronzetti-andrea.workers.dev/premium/agent-brief' --bazaar-pay-to '0xbda48b29607b9dc66ef7e38b68ad53f2b17efb23'
  • 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 whose runtime values pass the shared GET presence test, 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 l

Nur der Anfang wird gezeigt; den Rest findest du im Repo

PopNx fragen