Skip to main content
Glama
0rkz

PayPerByte

by 0rkz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to PayPerByte

Related Servers

  • AI Data Marketplace

    jblaz6335
    A
    license
    A
    quality
    A
    maintenance
    I built this local stdio MCP adapter to discover, preview, and purchase live agent data APIs, including vendor risk, company intelligence, transaction preflight, and EVM reads. Free discovery and previews require no wallet. Optional paid calls settle in Base USDC through x402 v2; auto-pay is disabled by default.
    2
    129 npm
    MIT

  • AlphaPipeline

    parkyucheol-del
    A
    license
    A
    quality
    A
    maintenance
    Pay-per-call ($0.005–$0.03 USDC) market, on-chain, and prediction-market data API for AI agents and trading bots via the x402 protocol — no signup, no API key. Exposed as a remote MCP server with 16 tools: pre-trade token security (honeypot/liquidity checks), kimchi premium, funding rate APR, DEX slippage, Polymarket arbitrage & liquidity audits, and Hyperliquid HIP-4 prediction-market odds.
    4
    16
    MIT

  • Genesis402

    FTHTrading
    A
    license
    A
    quality
    A
    maintenance
    Pay-per-call data and tools for AI agents over x402, by UnyKorn. 360 endpoints: DeFi and market data, multi-chain wallet reads, wallet and token risk signals, SEC filings, web and domain intel, and AI text tools. Settled per call in USDC on Base ($0.001-$0.25). No API keys or subscriptions; unpaid calls return the exact quote first.
    2
    21
    MIT

  • Nexus Intelligence MCP Server

    ROGT7
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to call 93 pay-per-call machine-to-machine services spanning web scraping, crypto sentiment, market data, on-chain analytics, social and threat intelligence, vulnerability scanning, and micro-SaaS utilities. Payments are settled in USDC on Arbitrum via the x402 protocol using a wallet header, so no API keys, signups, or billing setup are required.
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 15 tools

Disambiguation4/5

Each tool targets a distinct resource+action (publisher, subscription, feed, payload, balance), with clear separation between discover/subscribe/buy/publish/verify flows. The closest overlaps are byte_search_publishers vs byte_list_feeds and byte_check_subscription vs byte_list_my_subscriptions, but the descriptions clarify catalog-level discovery vs wallet-specific checks well enough to prevent misselection.

Naming Consistency4/5

The dominant pattern is byte_verb_noun (get_publisher, list_feeds, buy_data, verify_payload), and the byte_ prefix gives every tool a strong family identity. Deviations like byte_subscription_health (no verb) and byte_subscribe/byte_unsubscribe (verb-only) are conventional and readable but break the strict pattern.

Tool Count5/5

15 tools sits at the top of the well-scoped range, and each tool earns its place across two user roles (subscriber and publisher) plus payment, balance, and verification concerns. The breadth is justified by the data-marketplace domain, which naturally requires discovery, subscription lifecycle, publishing, pay-per-call purchasing, and attestation verification.

Completeness4/5

The subscriber lifecycle is fully covered (discover, subscribe, monitor health, unsubscribe), and the publisher side supports register and publish, complemented by pay-per-call purchase, fact-oracle queries, and payload verification. Notable gaps are publisher self-service (no schema/price update, no unregister) and no historical message retrieval beyond counts, but the core v1 workflows have no dead ends.

Maintenance

ActivityMaintained
ResponsivenessWithin a week

Resources