# Place Dossier Intent

Give a place query, get the matching business record plus its reviews.

- endpoint: `GET https://marketplaceforaiagents.com/api/public/v1/place-dossier`
- category: intents
- price: $0.005 USDC per call (5000 atomic, 6 decimals)
- free tier: 3 calls per agent identity, shared across all endpoints (unknown/generic clients draw from a site-wide 100 successful free calls per UTC day; crawlers get none)
- settlement: USDC on Base mainnet `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`, payee `0x05e82e03753c7bc99fb24d10a876cce53f24b7b7`, scheme `exact`
- sandbox: append `?network=base-sepolia` for testnet USDC + mock data
- results key: `results`
- html: https://marketplaceforaiagents.com/listings/place-dossier

## What it returns

Resolve a business or place from a query, then pull its Google Maps reviews — the place lookup and review fetch chained server-side.

## Use cases

- Vendor vetting for a local-services agent
- Sentiment summary for one location
- Contact + reputation dossier

## Parameters

| param | type | required | default | description |
| --- | --- | --- | --- | --- |
| `q` | string | yes | — | Place or business query, e.g. coffee in Austin |
| `place_id` | string | no | — | Skip discovery by supplying a known Google place ID |
| `sort_by` | string | no | — | relevance | newest | highest_rating | lowest_rating |
| `hl` | string | no | en | Interface language code |

## Example call

```bash
curl -s "https://marketplaceforaiagents.com/api/public/v1/place-dossier?q=example"
```

## Response shape

```json
{
  "intent": "place-dossier",
  "chain": [
    "google-maps",
    "google-maps-reviews"
  ],
  "steps_run": 2,
  "results": {
    "google-maps": {
      "note": "Normalized response of /api/public/v1/google-maps"
    },
    "google-maps-reviews": {
      "note": "Normalized response of /api/public/v1/google-maps-reviews"
    }
  }
}
```

## Payment

1. Call without `X-PAYMENT`. The first 3 calls per identity (across all endpoints) return 200 with an `X-Free-Calls-Remaining` header.
2. After that the response is `402` with an `accepts[]` requirement.
3. Sign the EIP-3009 USDC authorization, base64 the x402 payload, resend as `X-PAYMENT`.
4. Settlement receipt returns in the `X-PAYMENT-RESPONSE` header.