openplacesapi
Registry code: c6d1bba60c586738
Place search near a coordinate, backed by the Open Places API. Use list_categories to find category slugs, then search_places with q, category, or both. Authenticate by sending your API key as an Authorization: Bearer header on every request. Create a free key (2,500 searches once) at https://app.openplacesapi.com/signup.
- endpoint
- https://app.openplacesapi.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is openplacesapi live?
- Yes — it answered the hub's last check (checked 26h ago). It answered 100% of checks over the last 30 days.
- Is openplacesapi free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does openplacesapi have?
- 2 tools: search_places, list_categories.
- Is openplacesapi safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 2 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_categories open 26h ago
Look up valid category slugs for search_places. Answered locally from the Overture category taxonomy; does not use the API key or count against quota. With q (e.g. 'pharmacy', 'coffee', 'ev charging'), returns the best-matching categories (default 20, max 100) with label, parent, and full hierarchy. Without q, returns a compact overview: the top-level groups and their direct subcategories. Prefer passing q; the full taxonomy has over 2,000 categories.
{ "type": "object", "properties": { "q": { "type": "string", "maxLength": 64, "minLength": 1, "description": "Words describing the kind of place, or a guessed slug, e.g. 'pharmacy', 'hardware store', 'firestation'." }, "limit": { "type": "integer", "maximum": 100, "minimum": 1, "description": "Maximum matches when q is supplied, 1-100. Default 20. Ignored without q." } }, "additionalProperties": false }arguments 18 linessearch_places unknown 26h ago
Search real-world places (businesses, landmarks, venues) near a latitude/longitude. Returns names, structured addresses, categories, coordinates, and distances in miles, ranked by relevance then distance. Backed by open Overture Places data. Global coverage wherever the current Overture release has indexable Places data; quality varies by location. Pass q (free text), category (an exact Overture category slug such as 'pharmacy'), or both; at least one is required. A q that names a kind of place ('pharmacy', 'coffee near me', 'boots pharmacy') also searches that category: meta.interpreted_as says how q was read, and each result's match field says whether it matched by name, address, category, or name_and_category. Use mode=name to match q literally against names only. Use list_categories to find valid category slugs instead of guessing. This is proximity search only: it cannot geocode street addresses or autocomplete partial input. Each call counts as one search from the prepaid balance. Read meta.warnings: category_alias reports a reviewed legacy category resolved to resolved_category (legacy parent aliases can narrow the old filter), unknown_category lists suggested categories, no_results_within_radius includes nearest_match identifying the closest place found within the bounded 100-mile lookup, outside results, and says which radius_mi to retry with or to search from a closer point beyond the 50-mile maximum, query_relaxed means no exact matches so a loosened q was used, category_inferred means nothing matched by name so the results are nearby places in the closest category (not the named place), pagination_limit_reached means more places match beyond the 1,000-place category-browse window so narrow the search instead of paging. If a call fails with quota_exhausted, stop and tell the user instead of retrying.
{ "type": "object", "required": [ "lat", "lon" ], "properties": { "q": { "type": "string", "maxLength": 128, "minLength": 2, "description": "Free-text search, e.g. 'ramen', 'Blue Bottle', 'pharmacy', '서울'. Category words in q also search that category unless mode=name or category is set. Use at least 3 searchable characters, or 2 contiguous CJK characters. Required unless category is supplied." }, "lat": { "type": "number", "maximum": 90, "minimum": -90, "description": "Latitude of the search center." }, "lon": { "type": "number", "maximum": 180, "minimum": -180, "description": "Longitude of the search center." }, "mode": { "enum": [ "all", "name", "address" ], "type": "string", "description": "Match q against names, addresses, or both. Default 'all' (also reads category words in q). 'name' matches names literally, without category interpretation. mode=address needs at least 4 searchable characters in q." }, "sort": { "enum": [ "relevance", "distance" ], "type": "string", "description": "Result order. 'relevance' (default) ranks by match quality, then distance. 'distance' returns the same matches nearest first; category pages then page by distance." }, "limit": { "type": "integer", "maximum": 50, "minimum": 1, "description": "Maximum results. 1-20 without category, 1-50 when category is supplied. Default 10." }, "offset": { "type": "integer", "maximum": 999, "minimum": 0, "description": "Pagination offset for category browsing; only valid with category. offset + limit must be at most 1000 (the first 1000 ranked places). Use meta.next_offset from the previous page; it is null on the last page. Each page is one search." }, "category": { "type": "string", "pattern": "^[a-z0-9][a-z0-9_:-]{0,127}$", "maxLength": 128, "description": "Exact Overture category slug, e.g. 'pharmacy', 'coffee_shop', or a parent such as 'food_and_drink' (matches its subcategories). Find slugs with list_categories. Without q, lists places in this category by distance; with q, filters text matches to it." }, "radius_mi": { "type": "number", "maximum": 50, "description": "Search radius in miles, max 50. Default 25.", "exclusiveMinimum": 0 }, "min_confidence": { "type": "number", "maximum": 1, "minimum": 0, "description": "Only return places whose Overture confidence score is at least this value, 0-1." } }, "description": "Provide q, category, or both. lat and lon are always required.", "additionalProperties": false }arguments 76 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idc6d1bba60c586738.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/c6d1bba60c586738/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/c6d1bba60c586738?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.