354K+ restaurants across 12 markets — reviews, photos, neighborhood context and AI insights. Query it like any API, pay by the call in USDC. No account, no sales call.
● Free tier, no key required · Open x402 standard · MCP + REST
Quietest at 14:30 on weekdays — the relaxed window for lunch. Reviewers single out the cacio e pepe and the corner terrace tables.
Each restaurant comes back as a structured record — the same shape whether you ask for one place or stream a whole city.
Name, address, coordinates, hours, amenities, price level and verified phone. 354K+ restaurants, kept fresh.
7.5M+ real reviews with photos, star distribution and owner replies — paginated and filterable.
Landmarks, museums and parks around each place via Wikidata, so an agent can explain why this block.
Time-based discounts — “your hour, your price.” Read live slots and let an agent book the table directly.
Generated summaries, best-time-to-go and dish call-outs distilled from the reviews. Available from Premium.
Full record history and bulk export for indexing or training — on Premium and Enterprise.
Three moves on one route — from a cold request to a tier with room to run.
Search, fetch a place, or resolve a landmark over plain REST/JSON — or point an MCP client at pos.do. Free tier needs no key.
Hit a paid field and the route answers 402 Payment Required. Your agent settles a few cents of USDC via x402 and retries — per request, on-chain.
Hold $POSDO to move Free → Pro → Premium: higher rate limits, reviews, AI insights and bulk — no contract to sign.
No sign-up funnel, no key-management console, no human in the loop. An agent discovers the API, pays for what it uses, and keeps going.
Consumption is always pay-as-you-go in USDC. Holding $POSDO lifts your tier — more requests, richer data, higher priority.
| Tier | Hold (USD in $POSDO) | Consumption (USDC) | Rate limit | Data | Priority | Support |
|---|---|---|---|---|---|---|
| Free | — | Standard | ~10 req/min | Core fields | Standard | Docs & community |
| Pro | ≥ $100 in $POSDO | Discounted | ~120 req/min | + Reviews & photos | Elevated | |
| Premium Most data | ≥ $1,000 or stake | Best rate | ~600 req/min | + AI insights, full history, bulk | Priority queue | Priority |
| Enterprise | Custom / stake | Committed | Dedicated | Everything + bulk export, SLA | Dedicated | Dedicated |
$POSDO is how access and priority are coordinated across the API. You don’t spend it to call the data — consumption is always USDC. You hold it to unlock a tier, and the builders and agents using POS.DO share that same layer.
Utility access token for the POS.DO data network. It coordinates access and priority — it is not an investment product.
The free fields answer immediately. Paid fields return an x402 challenge your agent settles and retries — automatically.
# No key needed — start with one call
curl https://pos.do/v1/restaurants/anima-e-cuore?fields=core
# → 200 OK
# { "name": "Anima e Cuore",
# "neighborhood": "Eixample",
# "rating": 4.6, "price_level": 2 }# Paid fields answer with a payment challenge
curl -i https://pos.do/v1/restaurants/anima-e-cuore?fields=reviews,ai_insight
HTTP/1.1 402 Payment Required
x402: { asset:"USDC", amount:"0.002",
pay_to:"0x…", network:"Base" }
# Agent pays, then retries with the receipt
curl https://pos.do/v1/restaurants/anima-e-cuore?fields=reviews,ai_insight \
-H 'X-Payment: <usdc-settlement-proof>'
# → 200 OK · full record + ai_insightIllustrative — see the docs for exact schemas, fields and the full x402 handshake. The MCP endpoint exposes the same data conversationally.
No. The free tier is anonymous — make your first call with nothing but a URL. You only need the token when you want a higher tier’s rate limits and data.
Paid routes answer with HTTP 402 Payment Required and an x402 challenge. Your agent settles a few cents of USDC and retries with proof of payment — no invoices, no prepaid credits, no dashboard.
Access, not consumption. Holding it unlocks higher tiers — more requests, reviews, AI insights and bulk. You always pay for the calls themselves in USDC. It’s a utility access layer, not an investment.
354K+ restaurants across 12 markets, continuously enriched with 7.5M+ reviews, photos and neighborhood context — the same inventory that powers POS.DO discovery.
Yes. Point any Model Context Protocol client at pos.do and your agent discovers the tools and uses the same data conversationally — no glue code.
Premium and Enterprise include full record history and bulk export for indexing or training, with dedicated capacity available on Enterprise.