MPPtempoquality 0.55

Scrape web pages with optional JavaScript rendering, paid per call via MPP/Tempo.

Price
$0.006 / call
Protocol
mpp
Verified
no

What it does

This endpoint wraps the Abstract API Web Scraping service and is exposed through the Locus MPP (Micropayment Protocol). It accepts a target URL and returns the scraped page content. Optional parameters include JavaScript rendering (useful for SPAs and dynamically loaded content) and proxy country selection for geo-targeted scraping.

The endpoint is a POST-only route at `/abstract-web-scraping/scrape`. Each call costs $0.006 (6,000 base units of pathUSD with 6 decimals), settled on the Tempo L2 network. Payment is handled inline via the MPP charge intent — callers attach a Tempo payment header to each request.

Documentation is available at Abstract API's own reference pages and a Locus-hosted skill file. The probe returned 404 on HEAD and GET, which is expected since the endpoint only accepts POST requests. The OpenAPI spec is well-defined with a clear request schema, though the response schema is not documented beyond a generic 200 success indicator.

Capabilities

web-scrapingjavascript-renderinggeo-proxyhtml-extractionpost-only

Use cases

  • Scraping product pages or pricing data from e-commerce sites with JS-heavy frontends
  • Extracting article content from news sites for summarization pipelines
  • Geo-targeted page retrieval to verify region-specific content or ads
  • Feeding raw HTML into downstream LLM or NLP processing workflows
  • Monitoring web page changes by periodically scraping and diffing content

Fit

Best for

  • AI agents that need on-demand web page content without managing their own scraping infrastructure
  • Workflows requiring JavaScript-rendered pages (SPAs, lazy-loaded content)
  • Geo-specific scraping via proxy country selection

Not for

  • High-volume bulk crawling where per-call pricing would be expensive
  • Scraping sites that require authentication or cookie sessions (no auth parameter exposed)

Quick start

curl -X POST https://abstract-web-scraping.mpp.paywithlocus.com/abstract-web-scraping/scrape \
  -H "Content-Type: application/json" \
  -H "X-Payment: <tempo-payment-header>" \
  -d '{"url": "https://example.com", "render_js": true}'

Example

Request

{
  "url": "https://example.com",
  "render_js": true,
  "proxy_country": "US"
}

Endpoint

Quality

0.55/ 1.00

The OpenAPI spec provides a clear request schema, pricing, and payment method. However, the response schema is undocumented, no example responses are available, and the probe could not confirm a live 402 challenge because only HEAD/GET were attempted on a POST-only endpoint. External docs are referenced but were not crawled.

Warnings

  • Probe returned 404 on HEAD and GET — endpoint is POST-only; liveness via 402 challenge was not confirmed
  • Response schema is not documented; callers must infer the output format
  • No example responses available from probe or crawl data

Citations

Provenance

Indexed frommpp_dev
Enriched2026-04-19 17:49:42Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-21

Agent access