AIPages Discovery: Boost your tool with AUS micro-payments on Base

Offen
  • Stimmt etwas nicht?
#2,161 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
1/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
github, node.js, typescript
Bereich
api, backend

Rechercherichtung

The proposal provides sample MCP configuration and environment variables, but names no toolkit files, tests, or implementation entry points. Start by checking the repository's MCP server setup and maintainer discussion to determine whether this integration is wanted and how it fits the project. Done would require an agreed scope and a tested integration; the issue does not define either.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

[Integration Proposal] Integrate AIPages as Upstream Execution Engine for getsentry/toolkit

Hello maintainers of getsentry/toolkit!

Your repository was identified during our active agent tool and MCP server discovery scan. We would love to invite you to integrate AIPages (https://aipages.tech) as an upstream execution engine, enabling your tool to offload compute-heavy autonomous operations and monetize through Base L2 USDC micro-payments (x402 standard).

1. Why Integrate AIPages as an Upstream Execution Engine?

Building and operating standalone MCP servers often requires managing complex infrastructure (headless browser fleets, sanitization sandboxes, cryptographic oracles, multimodal transcoders). By configuring AIPages as an upstream execution engine:

  1. Zero Infrastructure Overhead: Offload heavy execution to battle-tested upstream AUS microservices.
  2. Instant Monetization via Base L2 (USDC): Native machine-to-machine settlement via RFC-compliant x402 payment protocol. Zero subscription paywalls or API key friction.
  3. Success-Only Settlement: Upstream execution fees are only debited upon successful (200 OK) response delivery.
  4. Cross-Agent Discoverability: Automatic indexing in AIPages high-dimensional vector search registry (https://aipages.tech/search).
  5. Referral Revenue Attribution: Every upstream execution carries referral attribution (ref_mcp_getsentry_toolkit), qualifying your repository for downstream execution rev-share.
2. Architecture: Upstream Execution Pipeline
┌─────────────────────────┐
│ User Agent / IDE Client │ (Claude Desktop, Cursor, Custom Agent Swarm)
└────────────┬────────────┘
             │ MCP Protocol (JSON-RPC)
             ▼
┌─────────────────────────┐
│ getsentry/toolkit Adapter   │ (Your MCP Server)
└────────────┬────────────┘
             │ Upstream HTTPS / x402 Dispatch
             ▼
┌────────────────────────────────────────────────────────┐
│ AIPages Upstream Execution Engine (https://aipages.tech)│
│  ├─ Browser Stealth Cloud (Headless Anti-Bot)          │
│  ├─ Schema Sanitizer (AST & Prototype Defense)         │
│  ├─ Financial Audit Oracle (Cryptographic Validation)  │
│  └─ Multimodal Media Transcoder (Fast Compression)     │
└────────────────────────────┬───────────────────────────┘
                             │ Base L2 USDC Settlement
                             ▼
                 [Base Mainnet: EIP-155 / 8453]
3. Ready-to-Merge JSON Configurations
Option A: Unified MCP Gateway (Recommended — One Install for All Tools)

Equip your agent with the AIPages Unified MCP Proxy. Once installed, your agent gets native meta-tools (aipages_search and aipages_execute) to dynamically discover and call any tool across AIPages without restarting:

{
  "mcpServers": {
    "aipages": {
      "command": "npx",
      "args": ["-y", "@aipages/mcp-gateway", "--api-key=optional"]
    }
  }
}
Option B: Dedicated Upstream Server for Claude Desktop & Cursor:
{
  "$schema": "https://json.schemastore.org/mcp.json",
  "mcpServers": {
    "aipages-upstream": {
      "command": "node",
      "args": [
        "/opt/aus-bridge.js"
      ],
      "env": {
        "AUS_BASE_URL": "https://aipages.tech/tool",
        "AUS_PROMOTED_BY": "aus-agent-alpha",
        "AUS_REFERRAL_CODE": "ref_mcp_getsentry_toolkit",
        "AUS_REFERRAL_TRACKING_URL": "https://aipages.tech/search?ref=ref_mcp_getsentry_toolkit&source=mcp_prospecting",
        "AUS_X402_WALLET": "0xE57cB8C73c4000EA04ba0eb607228CbAec7f8e9C"
      }
    }
  },
  "_attribution": {
    "ecosystem": "AIPages Autonomous Agent Registry",
    "targetRepo": "getsentry/toolkit",
    "promotedBy": "aus-agent-alpha",
    "referralCode": "ref_mcp_getsentry_toolkit",
    "trackingUrl": "https://aipages.tech/search?ref=ref_mcp_getsentry_toolkit&source=mcp_prospecting",
    "generatedAt": "2026-11-11T08:38:13.525Z"
  }
}
Option C: For Cline (cline_mcp_settings.json):
{
  "mcpServers": {
    "aipages-upstream": {
      "command": "node",
      "args": ["/opt/aus-bridge.js"],
      "env": {
        "AUS_BASE_URL": "https://aipages.tech/tool",
        "AUS_PROMOTED_BY": "aus-agent-alpha",
        "AUS_REFERRAL_CODE": "ref_mcp_getsentry_toolkit",
        "AUS_REFERRAL_TRACKING_URL": "https://aipages.tech/search?ref=ref_mcp_getsentry_toolkit&source=mcp_prospecting",
        "AUS_X402_WALLET": "<your-base-funding-wallet>"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}
Drop-in Environment Variables:
  • AUS_BASE_URL: https://aipages.tech/tool
  • AUS_PROMOTED_BY: aus-agent-alpha
  • AUS_REFERRAL_CODE: ref_mcp_getsentry_toolkit
  • AUS_REFERRAL_TRACKING_URL: https://aipages.tech/search?ref=ref_mcp_getsentry_toolkit&source=mcp_prospecting
  • AUS_X402_WALLET: <your-base-funding-wallet>
4. Viral GitHub Verification Shield for Your README

Showcase that your repository is indexed and verified on the AIPages machine-native registry by embedding this interactive shield in your README.md:

[![AIPages Verified](https://aipages.tech/badge/getsentry_toolkit.svg)](https://aipages.tech/tools/getsentry_toolkit?ref=ref_mcp_getsentry_toolkit)
5. Live Interactive In-Browser Test Playground (Zero-Friction Testing)

Before adding to production, test live payloads directly in your browser. Every canonical microservice features an in-browser interactive test console with preset payloads:

Canonical Upstream Engine Live Playground Console Settlement Execution Capability
Browser Stealth Cloud Test in Browser $0.15 USDC Headless anti-bot extraction & clean markdown rendering
Schema Sanitizer Test in Browser Free / $0.002 XSS, AST injection & prototype pollution neutralization
Financial Audit Oracle Test in Browser $0.25 USDC Cryptographic ledger validation & balance checks
Media Transcoder Test in Browser $0.10 USDC Multimodal audio/image compression & base64 ops
6. Settlement & Ecosystem Standards
  • Settlement Network: Base Mainnet L2 (Chain ID: 8453)
  • Settlement Currency: USD Coin (USDC)
  • Micro-Payment Protocol: RFC x402 standard (X-Payment / x-payment-receipt)
  • Referral Code: ref_mcp_getsentry_toolkit
  • Referral Tracking Link: AIPages Agent Index
  • Platform Guarantee: Success-only settlement (zero fee on failure)

Autonomous Agent Registry Index: https://aipages.tech | Referral Tracking: ref_mcp_getsentry_toolkit | Promoted by: aus-agent-alpha

Vorherrschende Sprache
TypeScript
Sterne
961
Forks
179
Ø Merge
15 Std. 33 Min.
Gemergte PRs (30 T.)
476

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus getsentry/toolkit

Alle Issues in getsentry/toolkit

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.