MPPtempoquality 0.92

Exa-powered neural web search at $0.01/request via micropayment — no API keys needed.

Price
$0.01 / call
Protocol
mpp
Verified
no

What it does

This endpoint provides semantic (neural) web search powered by Exa, proxied through StableEnrich's pay-per-request gateway. Send a natural-language query and receive ranked web results with titles, URLs, published dates, relevance scores, and optional inline content (text, highlights, summaries). An optional `category` parameter filters results by content type — including company pages, research papers, news, GitHub repos, tweets, LinkedIn profiles, PDFs, and financial reports.

The endpoint accepts POST requests with a JSON body. The only required field is `query` (string). Optional parameters include `numResults` (1–100, default 5), `type` (neural, fast, auto, deep), `category`, domain include/exclude lists, date range filters, `includeText`/`excludeText` arrays, and a `contents` object for requesting inline text extraction, highlights, summaries, livecrawl, and subpage expansion. Pagination is handled via `numResults`.

Pricing is $0.01 USD per request, settled via x402 or MPP (Tempo method, pathUSD currency) on each call. No API key or subscription is required — payment is authentication. The endpoint is part of StableEnrich, a unified research API suite by Merit Systems that bundles Exa, Apollo, Firecrawl, Google Maps, Serper, Whitepages, Clado, Minerva, Reddit, Hunter, Influencer, and Cloudflare crawl endpoints behind a single micropayment interface. Payments settle on Base mainnet (EIP-155:8453), Solana, or Tempo.

Capabilities

neural-web-searchsemantic-searchcategory-filteringdate-range-filteringdomain-filteringcontent-extractiontext-highlightsai-summarylivecrawlsubpage-expansionlinkedin-profile-searchmicropayment-authx402mpp-tempo

Use cases

  • AI agent performing open-ended web research on any topic
  • Finding LinkedIn profiles matching a job title and location
  • Discovering companies, research papers, or news articles by semantic query
  • Building candidate pools by searching for people profiles before enrichment
  • Retrieving web pages filtered by category (GitHub, PDF, tweet, financial report)

Fit

Best for

  • AI agents needing autonomous, subscription-free web search
  • Semantic queries where keyword search falls short
  • People discovery via LinkedIn profile category filter before enrichment
  • Research pipelines that fan out across many queries at low per-call cost

Not for

  • High-volume batch search requiring negotiated enterprise pricing
  • Use cases needing Google-specific SERP features (ads, knowledge panels) — use Serper endpoints instead
  • Scraping full page content from a known URL — use Exa Contents ($0.002) or Firecrawl Scrape ($0.0126) instead

Quick start

POST https://stableenrich.dev/api/exa/search
Content-Type: application/json

{
  "query": "best practices for building AI agents",
  "numResults": 5
}

Example

Request

{
  "type": "auto",
  "query": "hedge fund portfolio manager New York",
  "category": "linkedin profile",
  "numResults": 10
}

Response

{
  "results": [
    {
      "id": "result_001",
      "url": "https://www.linkedin.com/in/janedoe",
      "score": 0.92,
      "title": "Jane Doe - Portfolio Manager - Citadel | LinkedIn",
      "author": null,
      "publishedDate": "2024-01-15"
    },
    {
      "id": "result_002",
      "url": "https://www.linkedin.com/in/johnsmith",
      "score": 0.88,
      "title": "John Smith - Senior PM - Bridgewater | LinkedIn",
      "author": null,
      "publishedDate": "2023-11-20"
    }
  ],
  "requestId": "abc123",
  "searchType": "auto",
  "costDollars": {
    "total": 0.01
  },
  "resolvedSearchType": "neural"
}

Endpoint

Transporthttp
Protocolmpp
CurrencypathUSD

Quality

0.92/ 1.00

Full OpenAPI 3.1 schema with detailed request/response definitions, clear pricing ($0.01/request in USD), comprehensive guidance documentation, and multiple documented examples. The endpoint returned 405 on HEAD/GET probes because it only accepts POST, which is expected behavior — the OpenAPI spec confirms POST as the method. The 402 challenge was not directly captured but the x-payment-info block and full MPP protocol details are present in the schema.

Warnings

  • Probe returned 405 because HEAD/GET were tried on a POST-only endpoint; the endpoint is live per the OpenAPI spec and root page (200 status).
  • No direct 402 challenge was captured in the probe bundle, but payment info is fully specified in the OpenAPI x-payment-info block.

Citations

Provenance

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

Agent access