Pay-per-call PPC keyword research via SpyFu's SERP API on Tempo L2
What it does
This MPP (Micropayment Protocol) endpoint exposes SpyFu's PPC (pay-per-click) keyword research data through a per-call payment model settled on Tempo L2 (chain ID 4217). The endpoint lives at a wildcard path (`/apis/serp_api/v2/ppc/*`), suggesting it proxies multiple sub-routes of SpyFu's SERP API v2 for PPC-related queries — likely covering competitor ad copy, keyword bid estimates, ad spend history, and related PPC intelligence drawn from SpyFu's 18+ years of historical search marketing data.
Each call costs 20,000 base units of the settlement token (likely pathUSD with 6 decimals, i.e., $0.02 per request). Payment uses the Tempo method with intent "charge", meaning each request is a one-shot micropayment — no session or subscription required. The provider covers gas fees (feePayer: true), so callers only need a funded wallet on chain 4217.
No OpenAPI schema, documentation pages, or usage examples were found on the MPP gateway itself (all doc paths return 404). The endpoint structure and naming strongly suggest it mirrors SpyFu's existing SERP API v2 PPC endpoints, but without official docs on this gateway, the exact request parameters and response shapes must be inferred from SpyFu's public API documentation.
Capabilities
Use cases
- —Querying competitor PPC keywords and ad spend estimates on a per-call basis
- —Building automated SEM dashboards that pull fresh PPC data without a SpyFu subscription
- —Agent-driven ad copy analysis and keyword opportunity discovery
- —Integrating historical PPC intelligence into marketing automation pipelines
Fit
Best for
- —AI agents needing on-demand PPC keyword data without monthly subscriptions
- —Developers building SEM tools who want pay-per-query pricing
- —Automated competitor ad monitoring workflows
Not for
- —Organic SEO-only research (this endpoint is PPC-specific)
- —High-volume bulk data pulls where a flat-rate SpyFu subscription would be cheaper
- —Users without a Tempo L2 wallet or unfamiliar with crypto micropayments
Quick start
curl -X GET "https://spyfu.mpp.tempo.xyz/apis/serp_api/v2/ppc/keyword?query=insurance" \
-H "Authorization: Payment <tempo-payment-token>"Endpoint
Quality
The endpoint is live (402 challenge captured and valid), pricing is parseable, and the SpyFu brand context provides some grounding. However, there is zero documentation, no OpenAPI schema, no examples, and no crawlable content on the gateway — making this effectively a stub listing with inferred capabilities.
Warnings
- —No documentation or OpenAPI schema found on the MPP gateway (all doc paths return 404)
- —Exact request parameters and response format are unknown — must be inferred from SpyFu's public API docs
- —Currency token address 0x20c0…8b50 assumed to be pathUSD (6 decimals) on chain 4217; if decimals differ, the $0.02 price estimate is wrong
- —Wildcard path pattern means the exact sub-routes available are unconfirmed
Citations
- —SpyFu offers competitor keyword research with 18+ years of historical datahttps://spyfu.mpp.tempo.xyz
- —Endpoint returns 402 with Tempo payment challenge, amount 20000 base units, chain 4217https://spyfu.mpp.tempo.xyz/apis/serp_api/v2/ppc/*