Google Maps full place search via x402 — pay $0.04 per query, no API key needed
What it does
This endpoint wraps the Google Maps Places API through auor.io (Oreo), an x402-enabled AI agent research toolkit. It performs a text-based place search and returns all available details for each result, including address components, ratings, review counts, and place metadata. Payment is handled per-call via the x402 protocol on Base (EIP-155:8453) using USDC, at a fixed price of $0.04 per request.
The endpoint accepts a required `query` string parameter (e.g. "Restaurants in Ottawa"), an optional `pageSize` (1–20) to control result count, an optional `pageToken` for pagination, and an optional `Accept-Language` header for localized results. It is a GET request that returns JSON. The "full" variant returns all available place fields, as opposed to the sibling `/search/basic` endpoint which returns a reduced field set at a lower price ($0.032).
auor.io hosts multiple x402-gated API proxies (Google Maps, Google Translate, Google Weather, Amadeus flights, CrustData enrichment, Tavily web search, and more) under a single origin with no API keys or subscriptions required. The x402 challenge was confirmed live during probing. No dedicated documentation page was found (/docs, /pricing, /api all return 404), but the OpenAPI 3.1 spec is available at the origin and fully describes parameters and payment info.
Capabilities
Use cases
- —Finding businesses or points of interest by text query with full detail (ratings, addresses, types)
- —Retail site selection by searching for commercial areas in a city
- —Building location-aware AI agents that need rich place metadata
- —Aggregating place data for market research without managing Google API keys
Fit
Best for
- —AI agents needing pay-per-call Google Maps search without API key management
- —Developers who want full place details (address components, ratings, reviews count) in a single call
- —Prototyping location-based features with minimal setup
Not for
- —High-volume batch geocoding (dedicated geocode endpoint is cheaper at $0.005/call)
- —Use cases requiring only basic place info (the /search/basic endpoint is cheaper at $0.032)
- —Applications needing directions, routing, or Street View imagery
Quick start
curl -X GET "https://api.auor.io/google-maps/v1/search/full?query=Restaurants+in+Ottawa&pageSize=5" \
-H "Accept: application/json" \
-H "X-Payment: <x402-payment-header>"Endpoint
Quality
Full OpenAPI 3.1 spec with parameter definitions and x-payment-info is available, and the x402 challenge was confirmed live. However, response schemas are external $ref links not resolved in the probe, no example response body is provided, and the /docs page returns 404, leaving output structure undocumented.
Warnings
- —No dedicated documentation page found — /docs, /pricing, /api all return 404
- —Response schema is an unresolved $ref (./schemas/google-maps/v1/search/full/output.json); actual response fields are not documented in the probe
- —Example response structure inferred only from the landing page demo snippet, not from a formal schema
Citations
- —Endpoint uses x402 protocol with fixed price of $0.04 per callhttps://api.auor.io
- —Payment settles on Base (eip155:8453) using USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)https://api.auor.io
- —Parameters include query (required), pageSize (1-20), pageToken, and Accept-Language headerhttps://api.auor.io
- —auor.io describes itself as an x402 AI agent research toolkit with no API keys or monthly feeshttps://api.auor.io
- —The x402 challenge was confirmed live during probing (HTTP 402 returned)https://api.auor.io/google-maps/v1/search/full