Local Descriptions

by brave62793e0c49edNo license183 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 2 weeks ago

USE FOR getting AI-generated POI text descriptions. Requires POI IDs from local-place-search, or from web-search with result_filter=locations. Returns markdown descriptions grounded in web search context. Max 20 IDs per request.

Instructions onlyResearch & Analysis
AI-generated overview

Fetches AI-generated markdown descriptions for points of interest using POI IDs from a prior Brave search.

What it does
Documents the Brave Search API local descriptions endpoint, which returns AI-generated markdown descriptions for points of interest. It explains the required POI IDs, the request parameters, and the JSON response fields, including cases where a description is null. It also shows how to obtain POI IDs from a prior local place search or web search with a locations result filter.
When to use it
Use it when you already have POI IDs from a Brave local place search or a web search with the locations filter and need narrative descriptions for those places. It suits travel or destination content, local business overviews, and enriching search results with descriptive text.
Requirements
Requires a Brave Search API key with the Search plan, sent as an X-Subscription-Token header, plus network access to api.search.brave.com. POI IDs must come from a prior search and are valid for roughly eight hours. No scripts are included; it is instructions only.

Local Descriptions (Search API)

Requires API Key: Get one at https://api.search.brave.com

Plan: Included in the Search plan. See https://api-dashboard.search.brave.com/app/subscriptions/subscribe

Two-step flow: This endpoint requires POI IDs from a prior search.

  1. Get POI IDs from local-place-search, or from web-search with result_filter=locations (locations.results[].id)
  2. Pass those IDs to this endpoint to get AI-generated descriptions

Quick Start (cURL)

Get POI Description

bash
curl -s "https://api.search.brave.com/res/v1/local/descriptions?ids=loc4CQWMJWLD4VBEBZ62XQLJTGK6YCJEEJDNAAAAAAA%3D" \  -H "Accept: application/json" \  -H "Accept-Encoding: gzip" \  -H "X-Subscription-Token: ${BRAVE_SEARCH_API_KEY}"

Multiple POIs

bash
curl -s "https://api.search.brave.com/res/v1/local/descriptions" \  -H "Accept: application/json" \  -H "Accept-Encoding: gzip" \  -H "X-Subscription-Token: ${BRAVE_SEARCH_API_KEY}" \  -G \  --data-urlencode "ids=loc4CQWMJWLD4VBEBZ62XQLJTGK6YCJEEJDNAAAAAAA=" \  --data-urlencode "ids=loc4HTAVTJKP4RBEBZCEMBI3NG26YD4II4PATIHPDYI="

Note: POI IDs are opaque strings returned in web search locations.results[].id. They are valid for approximately 8 hours. The example IDs above are for illustration — fetch fresh IDs via web-search with result_filter=locations.

Endpoint

http
GET https://api.search.brave.com/res/v1/local/descriptions

Authentication: X-Subscription-Token: <API_KEY> header

Parameters

ParameterTypeRequiredDefaultDescription
idsstring[]Yes—POI IDs from web search locations.results[].id (1-20, repeated: ?ids=a&ids=b)

Response Format

Response Fields

FieldTypeDescription
typestringAlways "local_descriptions"
resultsarrayList of description objects (entries may be null)
results[].typestringAlways "local_description"
results[].idstringPOI identifier matching the request
results[].descriptionstring?AI-generated markdown description, or null if unavailable

Example Response

json
{  "type": "local_descriptions",  "results": [    {      "type": "local_description",      "id": "loc4CQWMJWLD4VBEBZ62XQLJTGK6YCJEEJDNAAAAAAA=",      "description": "### Overview\nA cozy neighborhood cafe known for its **artisanal coffee**..."    }  ]}

Getting POI IDs

local-place-search returns POI IDs directly. They also come from the Web Search API (web-search) with result_filter=locations:

bash
# 1. Search for local businessescurl -s "https://api.search.brave.com/res/v1/web/search?q=restaurants+san+francisco&result_filter=locations" \  -H "Accept: application/json" \  -H "X-Subscription-Token: ${BRAVE_SEARCH_API_KEY}"
# 2. Extract POI IDs from locations.results[].id# 3. Use those IDs with local/pois and local/descriptions

Use Cases

  • Local business overview: Pair with local-pois to get both structured data (hours, ratings) and narrative descriptions
  • Travel/tourism enrichment: Add descriptive context to POIs for travel planning or destination guides
  • Search results augmentation: Supplement web search results with AI-generated summaries of local businesses

Notes

  • Always markdown: Descriptions use ### headings, bullet lists, bold/italics — always formatted as markdown
  • Travel-guide tone: Typically 200-400 words covering what makes the POI notable
  • AI-generated: Descriptions are AI-generated based on web search context, not sourced from business profiles
  • Availability: Not all POIs have descriptions — description may be null
  • Max IDs: Up to 20 IDs per request

Source and attribution

Source:brave/brave-search-skillsinskills/local-descriptionsat commit62793e0

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal