Api Endpoint

serp402

Yelp: Scrape Yelp search results in JSON format automatically using custom parameters. Position, title, link, rating, reviews and more available. Structured JSON, USD 0.05 per call in USDC — no API key, no account, no subscription, no minimum. Not affiliated with, endorsed by or an official channel of any of the services the results come from. All trademarks and copyright remain the property of their respective owners.

Open interactive test console

Offering

Provider
serp402.com
Method
POST
Offering type
Api Endpoint
Transport type
http
Category
Other
Delivery
Not provided
Pricing model
Not provided
x402 version
2

Endpoint context

URL
https://serp402.com/api/v1/yelp-search
MIME type
Not provided
First seen
2026-10-26T21:57:19.024Z
Last seen
Tags
local, yelp, Search, X402, Agents

Payment pricing

x402 payment terms are the authoritative price for calling this endpoint.

Payment option 1
0.05 USDC
Atomic price: 50000 · Network: eip155:8453 · Asset: USDC · Scheme: exact
Payment option 2
0.05 USDC
Atomic price: 50000 · Network: solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp · Asset: USDC · Scheme: exact
Raw x402 terms
[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "50000",
    "payTo": "0xAA1252D726567293cffE6Ca495e32c6AEcfDC56d"
  },
  {
    "scheme": "exact",
    "network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
    "asset": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
    "amount": "50000",
    "payTo": "6srFz6v3mSUWBmz6Fx2XUaHQGHCNFJ59z85Cp9UDCvbK"
  }
]

Observed health

Status
Healthy
Latest latency
49 ms
Average latency
65 ms
HTTP status
204
Last checked
Reachability
100% over 2 checks

Latency is measured to the first response headers. A reachable result does not verify response accuracy or merchant identity.

Input schema

{
  "additionalProperties": false,
  "properties": {
    "body": {
      "additionalProperties": true,
      "properties": {
        "attrs": {
          "description": "Parameter is used for refining results. You can add more filters like 'price', 'features', etc. to your search. You can use our JSON endpoint to fetch values.…",
          "type": "string"
        },
        "cflt": {
          "description": "a category. It can be used alongside find_desc parameter to refine the search.",
          "type": "string"
        },
        "find_desc": {
          "description": "query you want to search. You can use anything that you would use in a regular Yelp search.",
          "type": "string"
        },
        "find_loc": {
          "description": "from where you want the search to originate. You can use any location you would use in a regular Yelp search. Following location formats are acceptable: - 706…",
          "type": "string"
        },
        "sortby": {
          "description": "Parameter is used for sorting results. Available options: recommended - Recommended (default) rating - Highest Rated review_count - Most Reviewed",
          "type": "string"
        },
        "start": {
          "description": "result offset. It skips the given number of results. It's used for pagination. (e.g., 0 (default) is the first page of results, 10 is the 2nd page of results,…",
          "type": "string"
        },
        "yelp_domain": {
          "description": "Yelp domain to use. It defaults to yelp.com . Head to the Yelp domains for a full list of supported Yelp domains.",
          "type": "string"
        }
      },
      "required": [
        "find_loc"
      ],
      "type": "object"
    },
    "bodyType": {
      "enum": [
        "json",
        "form-data",
        "text"
      ],
      "type": "string"
    },
    "method": {
      "enum": [
        "POST"
      ],
      "type": "string"
    },
    "type": {
      "const": "http",
      "type": "string"
    }
  },
  "required": [
    "type",
    "method",
    "bodyType",
    "body"
  ],
  "type": "object"
}

Output schema

{
  "properties": {
    "example": {
      "additionalProperties": true,
      "description": "Yelp results as structured JSON. The shape follows the source, so fields differ between endpoints; identifiers and routing belonging to the collection layer are stripped.",
      "properties": {
        "attribution": {
          "description": "Where the data comes from and what was done to it. Keep it with the results if you pass them on.",
          "type": "object"
        },
        "endpoint": {
          "description": "Which endpoint answered.",
          "type": "string"
        },
        "meta": {
          "description": "How long the call took.",
          "type": "object"
        },
        "paid": {
          "description": "The settled transaction and network.",
          "type": "object"
        }
      },
      "type": "object"
    },
    "type": {
      "type": "string"
    }
  },
  "required": [
    "type"
  ],
  "type": "object"
}