MPPtempoquality 0.30

S3/R2-compatible object listing endpoint with per-call micropayment via Tempo L2.

Price
$0.0001 / call
Protocol
mpp
Verified
no

What it does

This endpoint provides an object listing operation for an S3/R2-compatible object storage service hosted at storage.mpp.tempo.xyz. It is part of a broader Object Storage system that offers dynamic per-size pricing for storage operations. The endpoint is accessed via HTTP GET and is gated by the MPP (Micropayment Protocol) using the Tempo settlement method on chain ID 4217.

When called without payment, the endpoint returns a 402 Payment Required challenge. The challenge specifies a one-shot charge of 100 base units in the token at address 0x20c000000000000000000000b9537d11c60e8b50 on chain 4217. Assuming this is a 6-decimal stablecoin (such as pathUSD on Tempo L2), the cost per list-objects call is $0.000100 (one hundredth of a cent). The fee payer flag is set to true, meaning the service covers gas fees for the payment transaction.

Documentation is extremely sparse — all sub-paths (including /docs, /api, /pricing, /README) are themselves behind payment gates (returning 402 for "Download object"), so no schema, parameter documentation, or response format details are publicly available without paying. The service appears to treat every path as either a list or download operation depending on context.

Capabilities

object-listings3-compatibler2-compatiblemicropayment-gatedtempo-settlementper-call-pricing

Use cases

  • Listing stored objects in a pay-per-use storage bucket
  • Agent-driven file discovery without subscription commitments
  • Programmatic enumeration of stored assets with micropayment access

Fit

Best for

  • AI agents needing on-demand object enumeration without API keys
  • Micropayment-based storage access without monthly subscriptions
  • Developers building pay-as-you-go storage workflows on Tempo L2

Not for

  • High-frequency listing operations where per-call cost accumulates
  • Users needing detailed API documentation before integration
  • Applications requiring traditional auth (API key / OAuth) rather than crypto payments

Quick start

# List objects (requires MPP payment header)
curl -X GET https://storage.mpp.tempo.xyz/ \
  -H "Authorization: Payment <signed-tempo-payment-token>"

Endpoint

Transporthttp
Protocolmpp
CurrencypathUSD

Quality

0.30/ 1.00

The endpoint is confirmed live (402 challenge captured), but there is zero documentation available — all doc paths are themselves paywalled. No response schema, no parameter details, and the token currency address is not independently verifiable. This is effectively a stub listing.

Warnings

  • No public documentation available; all sub-paths (/docs, /api, /pricing, /README) are behind payment gates
  • Response schema for the list-objects call is unknown
  • Currency token address (0x20c000000000000000000000b9537d11c60e8b50) could not be independently verified; price assumes 6-decimal stablecoin
  • Chain ID 4217 (Tempo L2) is not a widely-known chain; wallet compatibility may be limited

Citations

Provenance

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

Agent access