MPPtempoquality 0.55

Pay-per-call Ethereum JSON-RPC via Alchemy, settled with Tempo (pathUSD) or Stripe (card).

Price
$0.0001 / session
Protocol
mpp
Verified
no

What it does

This MPP-enabled endpoint exposes Alchemy's JSON-RPC interface (eth_*, alchemy_* methods) for EVM-compatible blockchain data. The URL pattern `https://mpp.alchemy.com/:network/v2` lets callers specify the target network (e.g., eth-mainnet, polygon-mainnet, arb-mainnet) as a path parameter. Each call is individually metered and paid for via the Machine Payment Protocol (MPP) with a per-request charge.

Two payment methods are advertised. The **Tempo** method settles on-chain (chain ID 4217) using a token at address `0x20C0…8b50` with an amount of 1000 base units — given 6-decimal stablecoin conventions this equates to roughly $0.001 per call. The **Stripe** method settles via card rails with an advertised amount of 0 USD, suggesting metered billing or a free-tier arrangement through Stripe. The recipient address for Tempo payments is `0x7f51327A5A0927815DCcA531aa97Ec7252354091`.

Alchemy's broader platform covers 100+ chains with Core RPC, Prices, Portfolio, and NFT APIs. This particular MPP gateway is purpose-built for agent-to-agent programmatic access without API keys — agents authenticate by attaching a valid payment proof to each request. A skills-based onboarding hint is provided: `npx skills add alchemyplatform/skills --yes`.

Capabilities

json-rpceth-rpcalchemy-enhanced-apismulti-chainpay-per-callmpp-protocoltempo-settlementstripe-settlementevm-compatible

Use cases

  • Querying Ethereum or EVM chain state (balances, transactions, logs) on a per-call payment basis
  • Agents autonomously fetching on-chain data without pre-provisioned API keys
  • Building multi-chain dApps that pay for node access in real time
  • Portfolio or DeFi bots that need reliable RPC without subscription commitments
  • Indexing or monitoring smart contract events across supported networks

Fit

Best for

  • AI agents needing on-demand blockchain RPC without API key management
  • Low-volume or bursty workloads where pay-per-call is cheaper than a subscription
  • Multi-chain applications that want a single provider across many EVM networks

Not for

  • High-throughput indexing where a flat-rate subscription is more economical
  • Non-EVM chains (Solana, Bitcoin) unless explicitly supported at this gateway
  • Users who need WebSocket or streaming subscriptions (only charge intent observed)

Quick start

curl -X POST https://mpp.alchemy.com/eth-mainnet/v2 \
  -H 'Content-Type: application/json' \
  -H 'Payment: <MPP_PAYMENT_PROOF>' \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Example

Request

{
  "id": 1,
  "method": "eth_blockNumber",
  "params": [],
  "jsonrpc": "2.0"
}

Response

{
  "id": 1,
  "result": "0x134a3c7",
  "jsonrpc": "2.0"
}

Endpoint

Transporthttp
Protocolmpp
CurrencypathUSD

Quality

0.55/ 1.00

The endpoint is live and returns a well-formed MPP 402 challenge with two payment methods, confirming it works. However, no OpenAPI schema, no documentation pages resolve, and the exact set of supported networks and RPC methods must be inferred from the title and Alchemy's general platform description. Pricing for the Tempo method is derivable but the Stripe amount=0 is ambiguous.

Warnings

  • No OpenAPI or JSON schema is published at the gateway; supported methods and networks are inferred from the listing title and Alchemy's general docs.
  • The Stripe payment challenge shows amount=0 USD — it is unclear whether this means free, metered post-pay, or requires a pre-authorized card session.
  • The token address 0x20C0…8b50 on chain 4217 is assumed to be a 6-decimal stablecoin (pathUSD on Tempo L2) but this is not explicitly confirmed in the probe.
  • No /docs, /pricing, or /README pages are available at the gateway origin.

Citations

Provenance

Indexed frommpp_dev
Enriched2026-04-19 16:02:52Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access